On 10/2/06, Marc Bernatchez <[EMAIL PROTECTED]> wrote:
I think it was either osgGLUTsimple or osgGLUTkeyboardmouse, they are pretty close to each other w.r.t OSG/OpenGL usage so I doubt it'd make a difference.
Um... NVidia's driver probably has dozens of bugs in it, like any large bit of software, the OSG too, similiar symptoms can be caused by different bugs, and different symptoms can be stem from the same bug.
My hunch is the oddities in these cause stems from the same route problem.
I don't believe there any such difference worth investigating on the OSG side, the 3DS plugin just uses very simple OSG/OpenGL, all OpenGL 1.1 stuff. All these paths haven't changed in years with the OSG let alone between 1.0 and 1.2. If it were a problem on the OSG perhaps the most likely would be a dodge vertex index which is out of range.
I could try that on my side. You are referring to "osgGLUTsimple" here?
Do I have anything specific to setpup or would this sample trigger the
bug without any modifications?
I think it was either osgGLUTsimple or osgGLUTkeyboardmouse, they are pretty close to each other w.r.t OSG/OpenGL usage so I doubt it'd make a difference.
Since we already saw mention of texture crashes in the past that looked
related, I would tend to say it was still hitting the same bug. Were the
textures JPGs? I don't know if it is relevant.
Um... NVidia's driver probably has dozens of bugs in it, like any large bit of software, the OSG too, similiar symptoms can be caused by different bugs, and different symptoms can be stem from the same bug.
My hunch is the oddities in these cause stems from the same route problem.
I agree. Anything that allows us to narrow it down to the few lines of
code inside OSG that enable / disable the bug would be great.
I don't believe there any such difference worth investigating on the OSG side, the 3DS plugin just uses very simple OSG/OpenGL, all OpenGL 1.1 stuff. All these paths haven't changed in years with the OSG let alone between 1.0 and 1.2. If it were a problem on the OSG perhaps the most likely would be a dodge vertex index which is out of range.
>If the error is on the OSG side then its likely to be an uninitialized
variable somewhere. The nature of this problem doesn't
> point to this as the most likely candidate, it has many of the
hallmarks of a OpenGL driver bug. Robert.
You could be surprised ;-) One thing is certain thought, it sure sounds
like a nasty one.
I have seen many many bugs reports, I have merged many many bug reports, and have tracked down and fixed many bugs myself, few things suprise me ;-)
As a general note the core OSG is pretty sound, yes there a bugs, but most these days few are what I'd describe as nasty, and rarely do they take more than a couple of hours to track down and fix. For bugs of the nature as this one the majority of the time they prove to be OpenGL driver bugs, even ones that developer who've found the bug are convinced are OSG bugs.
If you want to make headway on this bug spend you time isolating a small app that recreates, trying to look through the OSG with a fine tooth comb will most like be wasting your and my time.
Robert.
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
