Hardware problems

OpenGL Development JOGL Development
#1

Hi

I deployed my app yesterday and recognized that there occour problems using different grafic cards.

For example a radeon 9200 mobile card leads to “snow” shown inside the my 3d-panel. It also corrupts windows xp itself (for example all internal icons got lost - the explorer is not longer able to display folder icons).

Another garfic card got a really serious problem runing my app :expressionless: black screen / reboot. But there the problem occours only casually - so it must be some kind of side effekt.
(reminder - nex time try to remember the graka model - was a high end cad grafic card.)

Is there any way to debug this behaviour?
The jogl default demos run proper on the same machines.

My gemometry contains only quad-stripes and lines. And i think im using ~ 75.000 vertexes.
Im new to jogl, so i used the same aproach like the red-robot demo. I just replaced the geometry with my own calculations. It wors really well on several grafic cards (radeon x800 for example or even an odd intel low end onboard graka).

Would be nice when someone got a hint for me. I like the peformance of jogl in comparison to my previous software renderer, but without a stable system its quite usless for my purpose.

thx
cybi aka Bernhard Neuhauser

#2

Tried to find the cause. It seems like the damaged output happens always when i try to connect additional buttons next to the jogl output. Whenever i add a simple button for example to the south side of my borderlayout then the opengl output crashes.

Im able to reproduce this behaviour on a radeon 9200 mobile card.

So i just split my application into 2 frames. But when i resice the jogl frame to often, the same error occours. It seems like the error occours only when the window reaches a certain size (~2/3 of the desktop size wich is huger then my normal frame size). When i resize the frame again to the smaller size, then the rendering happens correct again

cybi

#3

Are you using the JSR-231 beta 1 recently released? Please upgrade to that if not, as the implementation should be more robust than the 1.1.1 release.

Are you specifying -Dsun.java2d.noddraw=true on the command line?

Do you have a test case you could post showing the problems?

#4

Oh ;o) Will try the beta1.
I avoided using the beta because i thought that its just an api modification without further improvements on the engine itself.

Is there a specific reason for setting this option?

Not yet - its tightly integrated into my app. Need to seperate a testcase first. Will try the beta on monday . When the problem still occours, i will try to seperate a testcase containing as less code as possible.

Bernhard

#5

It is required for correctness of all JOGL applications on Windows due to Java2D’s automatic use of DirectDraw on Windows and driver-level incompatibilities between DirectDraw and OpenGL. It’s unlikely this is the cause of your problems but possible because that’s probably at least one difference between the JOGL demos (which set it) and your app.

#6

Okay i tried the JSR231 beta.

ATI 9200 Mobile:
Works well now.

Intel Onboard Graka:
Worked well with 1.1.1, but got troubles with JSR231b1

2 Problems:
a) Some kind of Display error. A surface with small univeness contains wrong shaded triangles. They appear in some kind of raster each 10th triangle got the wrong shading. ( hard to explain :expressionless: )

b) vm dies - its a 50:50 chance to get the error:

GL_VENDOR: Intel
GL_RENDERER: Intel 865G
GL_VERSION: 1.3.0 - Build 4.14.10.3865

An unexpected error has been detected by HotSpot Virtual Machine:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0b67d594, pid=2816, tid=1332

Java VM: Java HotSpot™ Client VM (1.5.0_05-b05 mixed mode)

Problematic frame:

C [ialmgicd.dll+0x1d594]

(dont know if the hs_err_pid2816.log file contains valuable information)

Trying to get a newer driver or something like that. Will also try some other grafic cards later.
Still happy with ogl ;o) The render quality is top. Just need to find a way for reaching the necessary stability.

the noddraw option had no influence

Bernhard Neuhauser
p.s. sry for avoiding attaching a screenshot or the error.log - dont know yet, what im allowed to offer

#7

Got it. I know now how to avoid my problem.

Per Default the Intel 865G uses 24bit depth buffer.
When i change the setting to 16 bit it works propper. The faulty triangles are gone and it seems like it runs stable.

Is such behavior my applications fault? Or is this a driver issue?

thx
Bernhard Neuhauser

#8

It’s hard to say without seeing code. Can you boil down your program into a small test case showing the problem and file it with the JOGL Issue Tracker?

I would be tempted to say that it’s Intel’s drivers, but in the past I wasn’t able to see many problems with JOGL apps (at least some of the JOGL demos) running with Intel Extreme hardware.