ATI 9800pro

Since upgrading to an ATI 9800 Pro my JOGL applications are throwing surface already locked exceptions whenever the window is resized quickly (under Windows XP).

This happens with my apps as well as the JOGL demos. Everything ran fine on my old NVIDIA. Has anybody experienced something similar?

Regards,

Craig

Yes.
I also experience troubles with my Xith3d application (based on JOGL), since I replaced an Nvidia GF4 with an ATI Radeon 9600 pro.
With my Xith app I experience the following:

  • the app now takes much longer to do the first render call (for a few polygon scenery),
  • strange effects appears when I swap between full screen and window mode (all the Swing components laying next to my GLcanvas are corrupted),

With my JOGL app(s) I experience this:

  • corrupted textures sometimes - in particular when I resize the window containing the GLcanvas.

None of these effects has been there with the very same Xith and Jogl apps on the same PC with a GF4 gfx card.

I think ATI’s OpenGL implementation isn’t good. A few friends of mine with ATI cards experienced trouble with OpenGL applications, too.

FYI: Using the latest ATI Catlyst drivers and resizing the JOGL canvas will completely hang the machine.
I have had more luck with the Omega drivers (www.omegacorner.com) which allow the application to keep running if I catch and ignore the errors thrown in the Animator thread. However this results in display corruption including textures, cursors and framebuffer. I may log a report with ATI if enough people have the same problem…

[quote]FYI: Using the latest ATI Catlyst drivers and resizing the JOGL canvas will completely hang the machine.
[/quote]
Well, I had to kick the latest Catalyst (4.1), too, because it caused several Bluescreens to my Win2000 box. :frowning:
Now I’m using a very old one (3.6) and it works fine - aside the mentioned Jogl “features”.

[quote]I have had more luck with the Omega drivers (www.omegacorner.com)
[/quote]
Kev’s using this, too AFAIK.

[quote]I may log a report with ATI if enough people have the same problem…
[/quote]
Well, maybe some more people report their problems here in the forum?

ATI’s drivers in combination with Java are evil… ;D Everything prior to 3.6 couldn’t do Swing in combination with a native OpenGL binding on some machine (including mine of course). Wurm Online doesn’t work anymore with the 3.10 (NOT 3.1…what a stupid naming btw) on my machine and the 4.1 crashes everything when running JBuilder9 in combination with LWJGL or Jogl. As much as i like the cards (have a 9700pro and a 9600xt), the drivers stink…
There’s a “catalyst feedback program” on ATI’s site. I’ve already reported my issues and i think it would be a good idea if everyone who has similar problems does. Maybe that forces them to a have a closer look.

Radeon 9700 Pro
Athlon XP 2.1 Ghz
512 MB of DDR 2700
NForce 2 Mobo

Zero glitches and everything running smooth as a baby’s butt ;D

I don’t see why using Java would be causing problems with ATI’s drivers as opposed to using straight c or c++. My guess is the drivers are not thread safe and don’t like calls from the drawing thread and window events coming in on different threads…

[quote]I don’t see why using Java would be causing problems with ATI’s drivers as opposed to using straight c or c++. My guess is the drivers are not thread safe and don’t like calls from the drawing thread and window events coming in on different threads…
[/quote]
It’s not just Jogl causing problems with ATI drivers, it’s ATI’s sloppily OpenGL drivers in general. With some of their cards things are worse, with others (Javacooldude’s?) it’s not so critically. My 9600 Pro is definitley no good OpenGL card, at least what’s concerning drivers.

[quote]My guess is the drivers are not thread safe and don’t like calls from the drawing thread and window events coming in on different threads…
[/quote]
Uh, OpenGL is never thread safe, calls are only valid from the thread you create the context in, unless you manually change which thread is current (which I don’t think is exposed in Jogl). If its failing due to you calling GL functions in (say) the event thread then its your code at fault, not ATi’s.

Yes of course. I don’t know why I wrote that… :-[

Have had no serious problems with my ATI 9500 Pro. Although with the previous drivers I used, opengl did not have 32 bit rendering or texturing. Went away when I upgraded the drivers.

A friend of mine has a 9600 and it crashes to a black screen when starting a simple lwjgl app. He has also had the same problem with other native opengl apps.

[quote]Well, maybe some more people report their problems here in the forum?
[/quote]
Well, my program crashes (error outside VM - [atioglxx.dll]) when setting some TIN geometry to wireframe. I tried the radeon 7500 and 9200 running on 4.1 catalyst drivers. I haven’t checked older drivers, but the same code worked for a GF4600ti and FX5600… :frowning: