[vtkusers] nVidia driver problems

Fahlgren, Eric efahlgren at lifemodeler.com
Fri Aug 26 17:04:10 EDT 2011

Maybe this should go to the developer's list, if so let me know.

I have occasionally had problems with nVidia video cards showing odd renderings of polydata object (shell/stl files with explicit normals).  Up until now, changing the driver has fixed the problem (it's not necessarily the latest and greatest drivers that work, sometimes the solution is to use older ones).  Well, I just got an nVidia Quadro FX3800 in a new machine and I cannot find the magic bullet to make the problem go away, so I need the wisdom of the list gods to help out.

Here's the problem in graphical form:  http://www.lifemodeler.com/eric/snapshot.html

When the object in question is originally rendered, everything is fine.  When I create a second view in the application (VTK inside wxWidgets) containing the same geometry, swapping back and forth between the two views causes this rendering error.

Here are some clues:

1)      Not the hardware.  I swap the video card into a Windows XP Pro 32-bit machine and cannot reproduce the problem.  Problematic machine is Win7 Pro 64-bit, the problem follows the OS (we've put the card into three machines now, 2x Win7 and 1x XP).

2)      We don't see the problem in any other software, including other OGL-using CAD, CAM and CAE packages.

3)      Does not happen on the "bad" machines when a Quadro FX1700 card is installed with the same driver versions.  Does not happen with ATI FirePro V7800 on the "bad" machines.

4)      Anything that causes the view to re-render (zoom, pan, or attribute changes on any object in the view), fixes the rendering and it looks "good" again.

5)      In the past, this sort of render-mangling has happened on arbitrary objects, but in this current manifestation, it only appears to affect things with opacity != 1.0.

I dug through both the developer and user archives, found something about texture maps causing problems when they were non-power-of-2 sized, but that's not it, as I can turn off all texture maps and see the same problem (besides, all my texture maps are 256x, or 512x...).

Does anyone have ideas on how I can diagnose this?  It sort of looks to me like the normals are backwards on the polydata object, but what would that mean?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20110826/231ea1cc/attachment.htm>

More information about the vtkusers mailing list