Posted by gouessej on Mar 02, 2024; 5:53pm
URL: https://forum.jogamp.org/Unable-to-determine-GraphicsConfiguration-tp4042444p4043347.html

You're not wasting my time but as I already wrote several times, the JogAmp community isn't responsible for the changes in Java itself.

I mentioned the arguments you have to use with the "java" command (since Java 9) here:
https://gouessej.wordpress.com/2012/08/01/java-3d-est-de-retour-java-3d-is-back/#commandline
https://gouessej.wordpress.com/2020/04/05/javafx-et-jogl-fonctionnent-ensemble-javafx-and-jogl-work-together/#commandlineinterface

I'm sorry to contradict you but at a certain level of complexity, any library requires a documentation and some tutorials. JogAmp will become easier to use anew when all these "--add-opens" and "--add-exports" clauses become useless. I understand your advice but keeping the backward compatibility with Java < 9 is tricky; if we decided to stop supporting those versions, we could put into JogAmp some module descriptors compatible with Java >= 9 and JogAmp would be a lot less cumbersome to use.

I'll try to run a simple example with JOGL 2.5.0 under Windows 11 Monday or Tuesday, I'll confirm which arguments are necessary.