problem with GLProfile.initSingleton()

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

problem with GLProfile.initSingleton()

NickJPGeorge
Hello, sorry for making 2 threads in one day, but I thought my question had diverged enough to warrant it.

I've got my webstart up until the point where it's actually running code (yay!), but I get this:

Caused by: javax.media.opengl.GLException: No profile available: [GL2, GL3bc, GL4bc, GL2GL3, GL3, GL4, GL2ES2, GLES2, GL2ES1, GLES1], GLAvailability[Native[GL4bc false, GL4 false, GL3bc false, GL3 false, GL2 false, GL2ES1 false, GLES1 false, GL2ES2 false, GLES2 false], Profiles[, default null]]
        at javax.media.opengl.GLProfile.<clinit>(GLProfile.java:995)
        ... 11 more

From the searching I tried, this looks like it would be an issue from moving from 1.1 to 2.0, but I have recent lib files.  Also, I've played around with a lot of ways of exporting the jar- the one above comes from including all the used classes in a com folder in the jar, AND referencing the newt-all-awt jnlp.  If I don't have the com folder in the jar, I get

java.lang.NullPointerException
        at javax.media.opengl.GLProfile.getProfileMap(GLProfile.java:1584)
        at javax.media.opengl.GLProfile.isGL4bcAvailable(GLProfile.java:151)
        at javax.media.opengl.GLProfile.glAvailabilityToString(GLProfile.java:242)
        at javax.media.opengl.GLProfile.glAvailabilityToString(GLProfile.java:310)
        at javax.media.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1283)
        at javax.media.opengl.GLProfile.access$000(GLProfile.java:71)
        at javax.media.opengl.GLProfile$1.run(GLProfile.java:117)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.media.opengl.GLProfile.initSingleton(GLProfile.java:115)
        at javax.media.opengl.GLProfile.validateInitialization(GLProfile.java:1428)
        at javax.media.opengl.GLProfile.getProfileMap(GLProfile.java:1580)
        at javax.media.opengl.GLProfile.get(GLProfile.java:623)
        at javax.media.opengl.GLProfile.getDefault(GLProfile.java:480)
        at javax.media.opengl.GLProfile.getDefault(GLProfile.java:486)
        at isogame.IsoFrame.<init>(IsoFrame.java:199)
        at isogame.IsoLauncher.main(IsoLauncher.java:14)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at com.sun.javaws.Launcher.executeApplication(Unknown Source)
        at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
        at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
        at com.sun.javaws.Launcher.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Thanks,
Nick
Reply | Threaded
Open this post in threaded view
|

Re: problem with GLProfile.initSingleton()

François Coupal
I have already filed a bug report for this.

Esssentially, the system generates a NPE when trying to do a simple "toString()" explaining that it could not find a profile.

The cause for that lack of profile is a different problem, probably more worthwhile to look into. The dependencies of the various packages is not well defined at the moment I'm afraid (from personnal experiences quite like your own).
Reply | Threaded
Open this post in threaded view
|

Re: problem with GLProfile.initSingleton()

NickJPGeorge
Huh.  Have you found a solution?

I think I've gotten a little closer to tracking this down.  I noticed in some sample code I saw they had a boolean in their initSingleton, so I updated all my libraries to the latest version.  Now I need the boolean, but I still get the same error.  I also get a massive framerate drop in fullscreen mode now.

...I may need to make another thread about that.

2011/3/16 François Coupal [via jogamp] <[hidden email]>
I have already filed a bug report for this.

Esssentially, the system generates a NPE when trying to do a simple "toString()" explaining that it could not find a profile.

The cause for that lack of profile is a different problem, probably more worthwhile to look into. The dependencies of the various packages is not well defined at the moment I'm afraid (from personnal experiences quite like your own).


If you reply to this email, your message will be added to the discussion below:
http://forum.jogamp.org/problem-with-GLProfile-initSingleton-tp2673904p2689053.html
To unsubscribe from problem with GLProfile.initSingleton(), click here.

Reply | Threaded
Open this post in threaded view
|

Re: problem with GLProfile.initSingleton()

Xfel
Are you shure you have OpenGL installed on your computer? "No GL Profile avaiable" would I translate in "You don't hav OpenGL"
Reply | Threaded
Open this post in threaded view
|

Re: problem with GLProfile.initSingleton()

Sven Gothel
Administrator
In reply to this post by NickJPGeorge
On Thursday, March 17, 2011 14:28:34 NickJPGeorge [via jogamp] wrote:
>
> Huh.  Have you found a solution?
>
> I think I've gotten a little closer to tracking this down.  I noticed in
> some sample code I saw they had a boolean in their initSingleton, so I
> updated all my libraries to the latest version.  Now I need the boolean, but
> I still get the same error.  
http://jogamp.org/wiki/index.php/Jogl_FAQ#Bugreports_.26_Testing

Pls also send the new stack trace produce with a very recent JOGL version
while mentioning the git commit hash (or release version) - thx.
(This should be clear when following the above procedure)

haven't found your bug report in bugzilla .. hmm.


> I also get a massive framerate drop in
> fullscreen mode now.

need a test case and the usual information (see FAQ link above).

>
> ...I may need to make another thread about that.
>
> 2011/3/16 François Coupal [via jogamp] <
> [hidden email]>
>
> > I have already filed a bug report for this.
> >
> > Esssentially, the system generates a NPE when trying to do a simple
> > "toString()" explaining that it could not find a profile.
> >
> > The cause for that lack of profile is a different problem, probably more
> > worthwhile to look into. The dependencies of the various packages is not
> > well defined at the moment I'm afraid (from personnal experiences quite like
> > your own).
> >
> > ------------------------------
> >  If you reply to this email, your message will be added to the discussion
> > below:
> >
> > http://forum.jogamp.org/problem-with-GLProfile-initSingleton-tp2673904p2689053.html
> >  To unsubscribe from problem with GLProfile.initSingleton(), click here<
> >
> >
>
>
> _______________________________________________
> If you reply to this email, your message will be added to the discussion below:
>
http://forum.jogamp.org/problem-with-GLProfile-initSingleton-tp2673904p2693416.html
> To start a new topic under jogl, email [hidden email]
> To unsubscribe from jogl, visit
health & wealth
mailto:
[hidden email] ; http://jausoft.com
land : +49 (471) 4707742 ; cell: +49 (151) 28145941
Timezone CET: PST+9, EST+6, UTC+1
Reply | Threaded
Open this post in threaded view
|

Re: problem with GLProfile.initSingleton()

blainebell
In reply to this post by NickJPGeorge
I have upgraded from 2.0 to 2.0rc2, and I get this same error (it worked on 2.0), regardless of whether I call initSingleton() explicitly, or I do:

GLCapabilities gl_capabilities = new GLCapabilities(GLProfile.getDefault());

I definitely have the same setup as I did in 2.0, (I copy the libraries into the exact locations), and obviously I have OpenGL installed (I saw a message asking that)

My exact stack trace is:


Exception in thread "main" java.lang.NullPointerException
        at javax.media.opengl.GLProfile.getProfileMap(GLProfile.java:1584)
        at javax.media.opengl.GLProfile.isGL4bcAvailable(GLProfile.java:151)
        at javax.media.opengl.GLProfile.glAvailabilityToString(GLProfile.java:242)
        at javax.media.opengl.GLProfile.glAvailabilityToString(GLProfile.java:310)
        at javax.media.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1283)
        at javax.media.opengl.GLProfile.access$000(GLProfile.java:71)
        at javax.media.opengl.GLProfile$1.run(GLProfile.java:117)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.media.opengl.GLProfile.initSingleton(GLProfile.java:115)
        at javax.media.opengl.GLProfile.validateInitialization(GLProfile.java:1428)
        at javax.media.opengl.GLProfile.getProfileMap(GLProfile.java:1580)
        at javax.media.opengl.GLProfile.get(GLProfile.java:623)
        at javax.media.opengl.GLProfile.getDefault(GLProfile.java:480)
        at javax.media.opengl.GLProfile.getDefault(GLProfile.java:486)
        at com.schrodinger.jymol.JyMolJoglWrapper.initialize_canvas(JyMolJoglWrapper.java:179)
        at com.schrodinger.jymol.JyMol.init(JyMol.java:241)
        at com.schrodinger.jymol.JyMol.<init>(JyMol.java:179)
        at demos.jymol.simple.Simple.<init>(Simple.java:51)
        at demos.jymol.simple.Simple.main(Simple.java:151)
Exception in thread "Thread-2" java.lang.NoClassDefFoundError: Could not initialize class javax.media.opengl.GLDrawableFactory
        at javax.media.opengl.GLDrawableFactory$2.run(GLDrawableFactory.java:172)
        at java.lang.Thread.run(Thread.java:680)

Was there any differences in this instantiation between 2.0 and 2.0rc2?

Thanks for your help in advance.  

Blaine
Reply | Threaded
Open this post in threaded view
|

Re: problem with GLProfile.initSingleton()

Wade Walker
Administrator
Hi guys,

Could you try downloading the latest JOGL development build from http://jogamp.org/deployment/autobuilds/master/ (the latest right now is http://jogamp.org/deployment/autobuilds/master/jogl-b358-2011-03-21_19-30-41/), then running the etc/test.sh script (etc/test.bat on Windows)? The output of this test script should help us figure out the nature of your problem.

If the debug flags aren't set inside this script, please add "-Dnewt.debug=all -Dnativewindow.debug=all -Djogl.debug=all" into the list of flags that you can see in there. This will produce even more output that will help us diagnose the problem.

Take the test.log file that this test script produces, and post it here, then we should know more about what's going on.