Do your Xith apps work with the newst Jogl version?
On my Ati Radeon 9600pro it doesn’t: the newst Jogl version doesn’t render anything (but the app doesn’t hang).
However when I set the switch -DATI_WORKAROUND , the Xith apps works.
This switch I’ve found in the Jogl thread named Rendering stops after first frame
Does anybody use Jogl v1.1. beta04 with Xith?
If you do so: does it work for your Xith apps and the official Xith demos?
For me it doesn’t.
I’ve filed an Jogl issue #98 on the Jogl dev net java, like Ken asked for in the above mentioned JOGL thread.
Unfortunately the Ctrl-Break dum when the render loops hangs doesn’t help so far.
Ken asks on the issue tracker: [quote]There isn’t an obvious deadlock in the stack trace below, although it isn’t clear how long or why the main thread is sleeping. Can you add some printing code to see whether the main loop is running properly? Can you also add some printing code to the underlying GLEventListener.display() routine in Xith3D (or some similar routine called during every render pass) to see whether the code is being executed?
[/quote]
However I’ve got no idea how to do this within Xith because I don’t know the the Xith internas.
Help much appreciated.
PS: I’m using not the latest Xith CVS version, mine is ~ 2 months old. Has there been some changes regarding this Jogl Ati workaround stuff in the latest Xith version, which I’ll download now?
the official xith version of jogl is two months old ( https://xith3d.dev.java.net/source/browse/xith3d/third-party/jogl/ ). No work has been done on compliance with the latest version to my knowledge. Once it does work with Xith3D, I am happy to update the JWS, CVS and xith.org downloads however 
Cheers,
Will.
With the newest Xith version (CVS), the few official Xith demos I’ve tested work with the Jogl 1.1 beta 04. Yesterday with my older Xith version they didn’t.
Of course it could all be coincidence.
However my own Xith application doesn’t work with Jogl 1.1 beta 04: no frame is being rendered.
Until I start my Xith app with the “-DATI_WORKAROUND=false” switch: then it works.
So actually I’ve no idea what’s going on. But it confuses me.
Maybe if some Xith-Jogl users who use ATI cards, would like to test if the Xith demos and their own Xith apps work fine with the newest Jogl version? (With and without that -D… switch)
Thanks!
Hi,
I am using latest JOGL from CVS with minor modifications, one of which is targeted to ATI_WORKAROUND.
I had this problem few weeks ago, and after deeper investigation discovered that the code hangs (dead-locks) at the ATI detection point. I just modified JOGL code and did not perform deeper investigation (just because of that time I found nothing relevant in JOGL and Xith3D foums, so decided not to make a noise).
I think I will try to dig deeper into this issue to get it fixed, but it looks like chicken-&-egg problem - ATI workaround tries to perform all the rendering in AWT event handling thread, and detection of the card happens in main thread, so we anyway access GL context from different threads, which causes headache for ATI driver…
Yuri
[quote]I had this problem few weeks ago, and after deeper investigation discovered that the code hangs (dead-locks) at the ATI detection point. I just modified JOGL code and did not perform deeper investigation (just because of that time I found nothing relevant in JOGL and Xith3D foums, so decided not to make a noise).
I think I will try to dig deeper into this issue to get it fixed, but it looks like chicken-&-egg problem - ATI workaround tries to perform all the rendering in AWT event handling thread, and detection of the card happens in main thread, so we anyway access GL context from different threads, which causes headache for ATI driver…
[/quote]
Thanks for that info, Yuri.
In the above mentioned Jogl thread (“Rendering 1st frame only”) there’s some more info by another Ati Jogl user. Basically there are quite some problems currently for (some?) Ati users to even run the offical Jogl demos (Gears for example).
Of course if such users use Xith the problems can become even more complex.
As a quick fix I currently can run my Xith app by setting the -DATI_WORKAROUND=false. However this can be just a very temporary solution. For the Xith demos I don’t have to do this. However for some Jogl demos they don’t work (=just 1st frame) no matter of that switch…
It looks to be very unstable currently. For Ati users I mean. Maybe the Ati OpenGL drivers will get better, now that OpenGL Doom3 is going to be shipped?