I just emailed GKW privately about this issue but I think there is probably a race condition in the auto-detection of the ATI_WORKAROUND flag. If you specify -DATI_WORKAROUND=true or -DATI_WORKAROUND=false, it should have different behavior than leaving the system property unspecified. The issue is that the component's rendering thread is being specified before it is detected that the single-threaded workaround should take effect, so when the workaround kicks in the context is already current on another thread. I'll need to think about this some more. Hopefully GKW's fix for the other bug (needing to manually create a dummy OpenGL context) can be used to fix this as well, by finding the GL_VENDOR of the dummy context.

I just emailed GKW privately about this issue but I think there is probably a race condition in the auto-detection of the ATI_WORKAROUND flag. If you specify -DATI_WORKAROUND=true or -DATI_WORKAROUND=false, it should have different behavior than leaving the system property unspecified.

I've just upgraded to jogl1.1b04 and my ATI 9700 really prefer me to put a -DATI_WORKAROUND=true rather than leaving it unspecified! So Ken you may be right!

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org