Hi John
On 2/13/07, PCJohn <[EMAIL PROTECTED]> wrote:
> The is known bug in NVidia drivers [...]
What is OSG strategy concerning HW bugs, drivers bugs, extension bugs...
Generally pull your hair in frustration :-)
There are actually a few things see below.
Is it expected that:
- each user of OSG has to handle the hw bugs by its own
-> OSG code is simple and clear
-> OSG users has to do much debugging on different hw again
and again
- OSG is expected to disable buggy extension,... if it detects the
problem
-> saving the time of other developers
-> some workarounds may "pollute" the clean OSG code
The OSG has OpenGL extension disable support built into as a means of
creating work arounds for a number of bugs. See
include/osg/GLExtensions for the methods and comments on controlling
the extension disable mechanism.
There are few places in the OSG where driver problems are specifically
accounted for, but in general its my policy not to do driver specific
hacks, hence the above general purpose mechanism.
The reason to avoid introducing lots of workarounds into the OSG is
that driver quality comes and goes throughout the life of the OSG and
associated applications. One day something will work, the next driver
update it won't and visa versa.
- something other - ?
I was pretty happy with Coin (Inventor clone) since they handled nearly
all different kinds of driver bugs and disfunctionalities in their
library. It can probably save quite much time of bug huntings at
customer side.
I don't know how up to date Coin is w.r.t latest OpenGL version and
extensions, but the OSG does map almost all latest extensions (save
for the latest NVidia ones) and this puts us a bit on the front line
w.r.t driver quality.
There are real liimits how much you can insulate app developer and end
users from driver bugs. The best fix is to work with/pressure the
like of ATI and NVidia to fix their bugs. We have an
OpenGLConformance page on the OSG wiki for just this purpose.
In the case of Producer's use of glXWaitVideoSync its not
configurable, so unfortunately one can't workaround it without
commenting out the affected code in Producer.
Robert.
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
