View Full Version : Volume Clipping issue on ATI Radeon 2400
JeffI
11-24-2008, 07:18 PM
Hi,
My client is using an ATI Radeon 2400. We installed OIV 7.2 and VolumeViz 7.2.
Volume clipping in Volume Viz is doing some bizarre things. We've repro'ed the issue using the just the VolRend demo.
See Link for:
- Card information
- A picture of the VolRend Demo
http://www.freeimagehosting.net/image.php?372b718f0e.png
I checked the following:
1) SoVolumeClippingGroup::isSupported() returns true.
JeffI
11-24-2008, 07:33 PM
When I built a quick demo with Volume Clipping, I'm seeing the following error messages pop up in an Open Inventor window:
Inventor: in SoGLSLangObject::compile(): info log after compilation of
VERTEX_SHADER:
Vertex shader was successfully compiled to run on hardware.
Inventor: in SoGLSLangObject::compile(): info log after compilation of
FRAGMENT_SHADER:
Fragment shader was successfully compiled to run on hardware.
I see a ton of these.
JeffI
11-25-2008, 08:11 PM
Hi,
The engineer here upgraded the latest driver for the 2400 card. Clipping now works on this card.
HOWEVER, their target card (4650) with the latest driver has issues with clipping. In fact, I can get the app to lock up if I zoom in to the clipped area.
Can you suggest something to try?
Thanks.
Jeff
JeffI
11-26-2008, 04:42 PM
The ATI Radeon card is loaded with the latest driver:
8.542.0.0 (Dated 10/3/2008)
Our simple scene has a volume (located at 0,0,0) with the following key values:
extent -188 -188 -744 188 188 744
data 376 376 248 "UBYTE"
We are clipping using the following geometry:
VolumeClippingGroup {
clipOutside FALSE
Coordinate3 {
point [ -491.268 -203.49 -750.024 ,
0 0 -750.024 ,
0 0 744 ,
-491.268 -203.49 744 ,
-376 376 -750.024 ,
203.49 491.268 -750.024 ,
203.49 491.268 744 ,
-376 376 744 ]
}
IndexedFaceSet {
coordIndex [ 0 , 1 , 2 , 3 , -1 , 3 , 2 , 6 ,
7 , -1 , 7 , 6 , 5 , 4 , -1 , 4 ,
5 , 1 , 0 , -1 , 0 , 3 , 7 , 4 ,
-1 , 1 , 5 , 6 , 2 , -1 ]
} }
Our Camera is:
OrthographicCamera {
position -564 564 -435.74
orientation -0.159267 -0.932447 -0.32431 2.28275
nearDistance -0
farDistance 3218.83
focalDistance 1609.42
height 1407.39
mikeheck
12-01-2008, 05:38 AM
Hi Jeff,
For what it's worth, volume clipping uses standard OpenGL features and GLSL code, and checks that all the required features are (claimed to be) supported on the current board. I don't mean to say it can't be (somehow) our problem, but historically when something like this only fails on one particular board, it's almost always a driver problem. Even more so when it's a fairly new board like the 4650.
I don't have access to a 4650, but I will check if any of our offices have one. I agree, 8.542 is the latest Catalyst 8.10 driver. However there is a slightly newer Catalyst 8.11 driver, 8.552. The release notes include this: "Running certain OpenGL applications may intermittently cause the system to
stop responding". It might be worth a try.
-Mike
mikeheck
12-01-2008, 07:01 PM
Customer reports that the problem is resolved using a newer ATI driver, specifically version 8.551:
http://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&questionID=38664
-Mike
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.