Ken -
Thanks for the reply! This is very exciting work!
The problems I’m having, at least on some of these machines, are multi-monitor related. Everything works fine on one monitor, and I can see from the debug console that the OpenGL pipeline is enabled for only one screen. I’m also seeing a nice performance increase! Is there a way to enable hardware acceleration on two (or more) monitors?
Thanks,
Paul
Hi Paul,
Unfortunately, on Windows, the OpenGL-based Java 2D pipeline is currently only configured to work properly on the primary screen (i.e., we enable it for the primary screen, but fallback on the GDI-based pipeline for other screens). This is more an artifact from a few years ago when the OGL pipeline was first developed and drivers were less robust in multi-monitor scenarios. With some more labor and testing we could probably remove this restriction, maybe in a future update release.
Thanks,
Chris
Hello,
I’ve recently started having problems, and unfortunately I cannot track down the source of the problem.
I’m using JOGL 1.1.1 (but I also tried 1.1.0) and NVidia drivers 178.24 (the latest) on a GeForce 8800 GTX card, and I’m unable to run applications which use a GLJPanel and the Java2D/OpenGL bridge. If I do not specify -Dsun.java2d.opengl=true it works ok but with a slow framerate. With the pipeline enabled, I’m seeing that either the Java2D elements are not rendered correctly (the JGears bottom bar with the JCheckBox is just black), or the OpenGL context flickers horribly (this happens with Chris Campbell’s BezierAnim3D demo). I’m using JDK 1.6.0 u 10. I’ve tried downgrading JOGL, my video driver, and the JDK to no avail. For now I have to run without the pipeline enabled, which is painfully slow.
I’ve also tried:
-Dsun.java2d.noddraw=true
-Dsun.awt.noerasebackground=true
-Dsun.java2d.opengl.fbobject=false
and I’ve tried to change gl.setSwapInterval(0) but that was a silly thing to try because that only affects GLCanvas, I think.
Anyone else experiencing flickering or Swing components not painting properly?
Thanks,
Chris
I’ve just updated to the latest NVidia drivers again with no luck. I’ve isolated the problem to the combination of:
-Dsun.java2d.noddraw=true
-Dsun.java2d.opengl=True
Without the first one, I get no rendering (as expected). Without the second the rendering is slow as the Java2D/JOGL pipeline is disabled. With both, I get horrible flickering, between my image and black.
Any suggestions?
Chris
How can I find these samples ’ s jogl source code
the interoperability demo is part of the jogl demos project (https://jogl-demos.dev.java.net/)
just download them directly or install the OpenGL Pack plugin if you are a NetBeans user
JOGL demos are failing on Open Solaris because of a missing GlueGen library:
com.sun.deploy.net.FailedDownloadException: Unable to load resource: http://download.java.net/media/gluegen/webstart-2.x/gluegen-rt-natives-solaris-i586.jar
at com.sun.deploy.net.DownloadEngine.actionDownload(DownloadEngine.java:1325)
at com.sun.deploy.net.DownloadEngine.getCacheEntry(DownloadEngine.java:1465)
at com.sun.deploy.net.DownloadEngine.getCacheEntry(DownloadEngine.java:1443)
at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(DownloadEngine.java:1546)
at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(DownloadEngine.java:1474)
at com.sun.deploy.net.DownloadEngine.getResource(DownloadEngine.java:211)
at com.sun.javaws.LaunchDownload.downloadJarFiles(LaunchDownload.java:931)
at com.sun.javaws.LaunchDownload.downloadEagerorAll(LaunchDownload.java:814)
at com.sun.javaws.Launcher.downloadResources(Launcher.java:1163)
at com.sun.javaws.Launcher.prepareLaunchFile(Launcher.java:687)
at com.sun.javaws.Launcher.prepareToLaunch(Launcher.java:212)
at com.sun.javaws.Launcher.launch(Launcher.java:106)
at com.sun.javaws.Main.launchApp(Main.java:354)
at com.sun.javaws.Main.continueInSecureThread(Main.java:216)
at com.sun.javaws.Main$1.run(Main.java:104)
at java.lang.Thread.run(Thread.java:619)
Thanks for reporting.
Sven and I have no longer access to download.java.net and to be honest I don’t know from what sources the binaries actually are built which are located there.
Rather look at them here in the future:
http://jogamp.org/deployment/jogamp-current/jar/
JOGL deployment is explained here.
WTF this is over 2.5 years old!
This thread is now non-sticky in order to focus less attention on outdated information.