Win and Linux works but on OSX black window

Hi there
Maybe some of you already run into a similar problem: A very simple OpenGL demo (showing a rotating cube), based on version 3.2 ("new" approach) runs fine on Windows and Linux machines.

But with OSX 10.7.5 and the newest nightly or official jogl/gluegen builds, we obtain an empty (black, depending on clear-color) window. So nothings seems to render on our GLCanvas.

I know there could be a lot of issues, but maybe some of you already encountered this problem and know something to try? Would be great.

Thanks

jonas

On 10/02/2012 12:46 AM, jonas [via jogamp] wrote: Can you pls be more specific which JogAmp build you use ?
See Wiki/FAQ and attach the information here, which will also give us
data about your OS, GPU and Java version - hence it really helps.

However, on my OSX machine w/ NVidia GeForce 320M,
  - Java 1.6.0_35-b10-428 64bit
  - OpenJDK 1.7.0-u10-b06 64bit (tested on commandline, no plugin support (?))

  - 10.7.4 (before update)
  - 10.7.5 (after update, just now - thx for the heads up)

I just ran the latest aggregated build:

<http://jogamp.org/deployment/archive/master/gluegen_594-joal_362-jogl_819-jocl_683-signed/>

Gears Test Applet (NApplet, NEWT/AWT bridge, GL2ES2 version):

<http://jogamp.org/deployment/archive/master/gluegen_594-joal_362-jogl_819-jocl_683-signed/jogl-applet-runner-newt-MovieCube-napplet.html>

Gears Test Applet (JNLP-Applet, AWT, GL2 version):

<http://jogamp.org/deployment/archive/master/gluegen_594-joal_362-jogl_819-jocl_683-signed/jogl-demos/applet-gears.html>

And I see it .. i.e. the new FBO offscreen mechanism is used
to deal w/ AWT/CALayer.

The above works well w/ latest OpenJDK7 as well.
The above should work well w/ newer OSX version.

There is one issue known w/ old Nvidia cards, see Bug 617
  <https://jogamp.org/bugzilla/show_bug.cgi?id=617>
We have triaged this bug and can provide a workaround before RC11.

I hope this info helps.

If your issue is reproducible and does not match Bug 617,
pls provide a small unit test and attach it to your new bug report.
Thank you.

~Sven

>
> Thanks
>
> jonas
>