Re: [osg-users] osgWidget 0.1.6 /osgText
Hi Jeremy, Is it osgWidget causing the BSOD, or just other things with that driver version? If I could track down a workaround for newer versions, I most certainly would--but every debugging app I've run watches the crash happen in proprietary libGL and stops there... No, not osgWidget. OSG itself. Have gone back to latest drivers and we're replacing all 'space' with '_'. Not ideal but need a solution now. Gert -- Gert van Maren Head of Research Development K2Vi Virtual Reality Software Data Interface Technologies Ltd Phone: +64 21 2855581 Email: [EMAIL PROTECTED] Web: http://www.k2vi.com ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] osgWidget 0.1.6 /osgText
On Fri, 2008-03-14 at 20:12 +1300, Gert van Maren wrote: Hi Robert, Looks like it. I have to go back to 97.XX driver to get rid of the crash but now I get other issues - BSOD occasionally. Is it osgWidget causing the BSOD, or just other things with that driver version? If I could track down a workaround for newer versions, I most certainly would--but every debugging app I've run watches the crash happen in proprietary libGL and stops there... G Hi Gert, This is almost certainly a driver bug... If getting rid of spaces fixes the problem perhaps its the spaces rendering in with coincident vertices or something, legal but triggering the bug no less. Robert. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] osgWidget 0.1.6 /osgText
Version 96.43.05 On Thu, 2008-03-13 at 19:21 +1300, Gert van Maren wrote: Hi Jeremy, I am getting similar crashes in osgText - nvogl.dll - division by zero. If I get rid of all spaces in my text - no crashes. I am running a GeForce 8800 GTS. 169.21 forceware drivers. Which legacy driver did you go to? Regards Gert On Thu, 13 Mar 2008 13:31:14 +1300, [EMAIL PROTECTED] wrote: I downgraded to the latest Linux NVidia legacy driver and the problem went away. ...go figure... Full speed ahead! ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] osgWidget 0.1.6
I downgraded to the latest Linux NVidia legacy driver and the problem
went away.
...go figure...
Full speed ahead!
On Tue, 2008-03-11 at 13:19 -0700, Mark Sciabica wrote:
Check that new text code I posted. I initially had problems handling
the space character because it's implemented as having zero height and
width.
First make sure I sent you the right version: fHorizQuadMargin and
fVertQuadMargin initialization should be checking for vDiff nonzero
before dividing. My driver didn't like when I forgot to do that. Also,
the code assumes that the texture width/height are nonzero. If this
assumption is incorrect, the division by zero at that point might be
causing a problem.
Other than that, the only thing I can see a driver tripping up on is
creation of a zero area quad (which a space will end up being) with
different texture coordinates at each vertex. This will give an
infinite rate of change of texture coordinates across the primitive
which might be confusing the driver.
To see if this is the problem, try the following code to avoid adding
unnecessary margins to zero width glyphs.
float fHorizTCMargin = 1.0f / glyph-getTexture()-
getTextureWidth();
float fVertTCMargin = 1.0f / glyph-getTexture()-
getTextureHeight();
float fHorizQuadMargin;
if (vDiff.x() == 0.0f)
{
fHorizQuadMargin = 0;
}
else
{
fHorizQuadMargin = width * fHorizTCMargin /
vDiff.x();
mintc.x() -= fHorizTCMargin;
maxtc.x() += fHorizTCMargin;
}
if (vDiff.y() == 0.0f)
{
fVertQuadMargin = 0;
}
else
{
fVertQuadMargin = height * fVertTCMargin /
vDiff.y();
mintc.y() -= fVertTCMargin;
maxtc.y() += fVertTCMargin;
}
On Mar 11, 10:46 am, Jeremy Moles [EMAIL PROTECTED] wrote:
I tagged a 0.1.6 of osgWidget:
http://osgwidget.googlecode.com
I really wouldn't even bother posting about it to be honest but I need a
bit of help if anyone is willing to try it. :)
Upon building osgWidget (you'll want to get the monospace font and the
osgText.cpp patch for maximum font clarity, but they aren't necessary),
run the osgwidgetinput example and press the following keys:
n
SPACE
Where that's the actual key 'n' and the spacebar. Something really
bizarre is happening on my machine and I'm beginning to think it's a
driver bug... what happens though is that I get an Floating Point
Exception inside of NVidia's libGL, and it seems to have something to do
with the space character in some context. If you immediately insert a
space character, you can then follow that with any series of key presses
you like, including spaces or otherwise.
Anyways, this isn't a big deal (I'm sure I'll get it figured out), but I
just wanted to let folks know I'm still alive and things are chugging
along slowly. :)
(I've been extremely busy these last few weeks writing some
system-auditing software in Python for a client, and haven't had much
time for hobby code...)
___
osg-users mailing list
[EMAIL
PROTECTED]://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph...
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] osgWidget 0.1.6
Hi Jeremy, Good to see another release of osgWidget make it out into the daylight. W.r.t the crash, try forcing the app to be single threaded. Beyond that I can't suggest much. Alas I'm too busy myself for experimenting with osgWidget yet, but I really really want to get started with it. Robert. On Tue, Mar 11, 2008 at 5:46 PM, Jeremy Moles [EMAIL PROTECTED] wrote: I tagged a 0.1.6 of osgWidget: http://osgwidget.googlecode.com I really wouldn't even bother posting about it to be honest but I need a bit of help if anyone is willing to try it. :) Upon building osgWidget (you'll want to get the monospace font and the osgText.cpp patch for maximum font clarity, but they aren't necessary), run the osgwidgetinput example and press the following keys: n SPACE Where that's the actual key 'n' and the spacebar. Something really bizarre is happening on my machine and I'm beginning to think it's a driver bug... what happens though is that I get an Floating Point Exception inside of NVidia's libGL, and it seems to have something to do with the space character in some context. If you immediately insert a space character, you can then follow that with any series of key presses you like, including spaces or otherwise. Anyways, this isn't a big deal (I'm sure I'll get it figured out), but I just wanted to let folks know I'm still alive and things are chugging along slowly. :) (I've been extremely busy these last few weeks writing some system-auditing software in Python for a client, and haven't had much time for hobby code...) ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] osgWidget 0.1.6
Hi Jeremy, As you know, I was waiting for this release to dive in. So there I go. I will try to helpful. Thanks a lot, Nicolas. 2008/3/11, Robert Osfield [EMAIL PROTECTED]: Hi Jeremy, Good to see another release of osgWidget make it out into the daylight. W.r.t the crash, try forcing the app to be single threaded. Beyond that I can't suggest much. Alas I'm too busy myself for experimenting with osgWidget yet, but I really really want to get started with it. Robert. On Tue, Mar 11, 2008 at 5:46 PM, Jeremy Moles [EMAIL PROTECTED] wrote: I tagged a 0.1.6 of osgWidget: http://osgwidget.googlecode.com I really wouldn't even bother posting about it to be honest but I need a bit of help if anyone is willing to try it. :) Upon building osgWidget (you'll want to get the monospace font and the osgText.cpp patch for maximum font clarity, but they aren't necessary), run the osgwidgetinput example and press the following keys: n SPACE Where that's the actual key 'n' and the spacebar. Something really bizarre is happening on my machine and I'm beginning to think it's a driver bug... what happens though is that I get an Floating Point Exception inside of NVidia's libGL, and it seems to have something to do with the space character in some context. If you immediately insert a space character, you can then follow that with any series of key presses you like, including spaces or otherwise. Anyways, this isn't a big deal (I'm sure I'll get it figured out), but I just wanted to let folks know I'm still alive and things are chugging along slowly. :) (I've been extremely busy these last few weeks writing some system-auditing software in Python for a client, and haven't had much time for hobby code...) ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
