Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
/hello Guys: This is a very old message please ignore this. I have no clue why it is here now. It may have been moderated Take care Garrett On Aug 16, 2007, at 1:48 PM, Garrett Potts wrote: > Hello All: > > I am having text/font issues under the 64-bit SUSE. If ever a > setText is called on an osgText object there is a core dump that > occurs. Note the code works fine on MAC's ad Windows. I think it > might be related to 64-bit build on SUSE. I don't have much more > details than this. Commenting out any of the setText code allows my > application to run fine. I have also tried the latest dev 2.1.5 with > the same issues. I am still poking around but do not know if I can > resolve this quickly. > > > Take care > > Garrett > > ___ > 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] Has anyone tried 64-bit SUSE enterprise
On 8/17/07, Robert Osfield <[EMAIL PROTECTED]> wrote: > > Hi Garret, > > On 8/16/07, Garrett Potts <[EMAIL PROTECTED]> wrote: > > I think you are right that it's a ATI problem more than likely the > > drivers for SUSE. The MAC drivers work great. > > Mac ATI drivers seem to be the only place that ATI's actually have > good drivers... > > One thing you could try is to disable the incremental subloading of glyphs > >export OSG_TEXT_INCREMENTAL_SUBLOADING=OFF Ah, thanks. This solved my issue of viewer being blocked for a long time when I enable stats on my laptop. It seems that this should be disabled by default if an ATI driver is being used. Regards, Jan ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hi Brede, The slow down in performance could be down to either the OSG or OpenGL. When stats is enabled the OSG, on hardware that supports it, will put timing tokens into the OpenGL fifo to collect GPU stats - this is used in the orange GPU text and bars. The OSG' collection of stats itself isn't multi-threaded, except when you have multiple graphics windows active, and the granulatity of the threading is simply the same as normal rendering. The enabling of multi-core might be leading to the OSG using DrawThreadPerContext rather than SingleThreaded on you machine, so this could be a potention change. Try forcing SingleThreaded then try the stats. I don't think this will make any difference but it would at least tick on possibility off the list. My best guess right now is that this bug is an NVidia driver bug in collecting GPU stats + running with running dual core. Robert. On 8/20/07, Brede Johansen <[EMAIL PROTECTED]> wrote: > Robert, > > Yes the continuous drop in framerate only happens when the bar graph stats > are active. The help screen doesn't have this problem. One interesting > thing is that when I remove the stats the framerate is back to normal and > when the stats are enabled again the drop continues from where it was last > time stats where active! > > I found out that disabling one of the two cores in the BIOS settings I was > no longer able to reproduce the drop in framerate. > > I do have some problems with BSOD when running OSG applications with both > cores enabled so it might be an indication of a driver issue. > > Regards, > Brede > > > > > On 8/19/07, Robert Osfield <[EMAIL PROTECTED]> wrote: > > Hi Brede, > > > > Does the onscreen help cause the same performance slow down, or is it > > just stats. The difference being that help is static text, and stats > > is being dynamically update. The cost should be pretty negligible > > though - the stats scene graph is trivial in size. > > > > With the stats I have found that text is relatively slow to update, > > suggesting a need for a rewrite of osgText further down the line, > > but.. the currently implementation should not go leaking like you have > > found, this suggest another problem all togther. > > > > Robert. > > > > On 8/18/07, Brede Johansen <[EMAIL PROTECTED] > wrote: > > > Jan and Robert, > > > > > > This happens with the latest ForceWare release 162.18. > > > osgviewer from SVN. > > > I have two screens attached to a 8800GTX and one screen attached to a > > > 8600GS. I know the GS isn't the best but I had a spare slot and a > spare > > > screen so I had to try. The CPU is a Core 2 Duo. > > > > > > Brede > > > > > > > > > > > > On 8/18/07, Jan Ciger <[EMAIL PROTECTED]> wrote: > > > > -BEGIN PGP SIGNED MESSAGE- > > > > Hash: SHA1 > > > > > > > > Brede Johansen wrote: > > > > > Hi Jan, > > > > > > > > > > The framerate continues to drop so if it starts at 60Hz it slowly > drops > > > and > > > > > reaches 30Hz after aproximatly 20 seconds. It is not a one time > drop > > > due to > > > > > the HUD. This happens in SingleThreaded mode with a very simple > model. > > > > > > > > > > Brede > > > > > > > > > > > > > If this is happening with a standalone viewer, then this indeed looks > > > > like a driver bug. I do not see this behaviour on a GeForce nor ATI > > > > hardware. > > > > > > > > Jan > > > > -BEGIN PGP SIGNATURE- > > > > Version: GnuPG v1.4.7 (GNU/Linux) > > > > Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org > > > > > > > > > > > > iD8DBQFGxylsn11XseNj94gRAu7vAJ9yASBA0Nfy1YV30Cdou9w2RmcbogCg6wq/ > > > > Y4cDyO3QqkydYX/uLkqXQm0= > > > > =p5qa > > > > -END PGP SIGNATURE- > > > > ___ > > > > 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 > > > > > ___ > 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] Has anyone tried 64-bit SUSE enterprise
Robert, Yes the continuous drop in framerate only happens when the bar graph stats are active. The help screen doesn't have this problem. One interesting thing is that when I remove the stats the framerate is back to normal and when the stats are enabled again the drop continues from where it was last time stats where active! I found out that disabling one of the two cores in the BIOS settings I was no longer able to reproduce the drop in framerate. I do have some problems with BSOD when running OSG applications with both cores enabled so it might be an indication of a driver issue. Regards, Brede On 8/19/07, Robert Osfield <[EMAIL PROTECTED]> wrote: > > Hi Brede, > > Does the onscreen help cause the same performance slow down, or is it > just stats. The difference being that help is static text, and stats > is being dynamically update. The cost should be pretty negligible > though - the stats scene graph is trivial in size. > > With the stats I have found that text is relatively slow to update, > suggesting a need for a rewrite of osgText further down the line, > but.. the currently implementation should not go leaking like you have > found, this suggest another problem all togther. > > Robert. > > On 8/18/07, Brede Johansen <[EMAIL PROTECTED]> wrote: > > Jan and Robert, > > > > This happens with the latest ForceWare release 162.18. > > osgviewer from SVN. > > I have two screens attached to a 8800GTX and one screen attached to a > > 8600GS. I know the GS isn't the best but I had a spare slot and > a spare > > screen so I had to try. The CPU is a Core 2 Duo. > > > > Brede > > > > > > > > On 8/18/07, Jan Ciger <[EMAIL PROTECTED]> wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > > > > Brede Johansen wrote: > > > > Hi Jan, > > > > > > > > The framerate continues to drop so if it starts at 60Hz it slowly > drops > > and > > > > reaches 30Hz after aproximatly 20 seconds. It is not a one time > drop > > due to > > > > the HUD. This happens in SingleThreaded mode with a very simple > model. > > > > > > > > Brede > > > > > > > > > > If this is happening with a standalone viewer, then this indeed looks > > > like a driver bug. I do not see this behaviour on a GeForce nor ATI > > > hardware. > > > > > > Jan > > > -BEGIN PGP SIGNATURE- > > > Version: GnuPG v1.4.7 (GNU/Linux) > > > Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org > > > > > > > > iD8DBQFGxylsn11XseNj94gRAu7vAJ9yASBA0Nfy1YV30Cdou9w2RmcbogCg6wq/ > > > Y4cDyO3QqkydYX/uLkqXQm0= > > > =p5qa > > > -END PGP SIGNATURE- > > > ___ > > > 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 > ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Robert, I'm pretty sure it's only the stats with the bar graphs. I will check the help screen tomorrow when I'm back at work. Brede On 8/19/07, Robert Osfield <[EMAIL PROTECTED]> wrote: > > Hi Brede, > > Does the onscreen help cause the same performance slow down, or is it > just stats. The difference being that help is static text, and stats > is being dynamically update. The cost should be pretty negligible > though - the stats scene graph is trivial in size. > > With the stats I have found that text is relatively slow to update, > suggesting a need for a rewrite of osgText further down the line, > but.. the currently implementation should not go leaking like you have > found, this suggest another problem all togther. > > Robert. > > On 8/18/07, Brede Johansen <[EMAIL PROTECTED]> wrote: > > Jan and Robert, > > > > This happens with the latest ForceWare release 162.18. > > osgviewer from SVN. > > I have two screens attached to a 8800GTX and one screen attached to a > > 8600GS. I know the GS isn't the best but I had a spare slot and > a spare > > screen so I had to try. The CPU is a Core 2 Duo. > > > > Brede > > > > > > > > On 8/18/07, Jan Ciger <[EMAIL PROTECTED]> wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA1 > > > > > > Brede Johansen wrote: > > > > Hi Jan, > > > > > > > > The framerate continues to drop so if it starts at 60Hz it slowly > drops > > and > > > > reaches 30Hz after aproximatly 20 seconds. It is not a one time > drop > > due to > > > > the HUD. This happens in SingleThreaded mode with a very simple > model. > > > > > > > > Brede > > > > > > > > > > If this is happening with a standalone viewer, then this indeed looks > > > like a driver bug. I do not see this behaviour on a GeForce nor ATI > > > hardware. > > > > > > Jan > > > -BEGIN PGP SIGNATURE- > > > Version: GnuPG v1.4.7 (GNU/Linux) > > > Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org > > > > > > > > iD8DBQFGxylsn11XseNj94gRAu7vAJ9yASBA0Nfy1YV30Cdou9w2RmcbogCg6wq/ > > > Y4cDyO3QqkydYX/uLkqXQm0= > > > =p5qa > > > -END PGP SIGNATURE- > > > ___ > > > 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 > ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hi Brede, Does the onscreen help cause the same performance slow down, or is it just stats. The difference being that help is static text, and stats is being dynamically update. The cost should be pretty negligible though - the stats scene graph is trivial in size. With the stats I have found that text is relatively slow to update, suggesting a need for a rewrite of osgText further down the line, but.. the currently implementation should not go leaking like you have found, this suggest another problem all togther. Robert. On 8/18/07, Brede Johansen <[EMAIL PROTECTED]> wrote: > Jan and Robert, > > This happens with the latest ForceWare release 162.18. > osgviewer from SVN. > I have two screens attached to a 8800GTX and one screen attached to a > 8600GS. I know the GS isn't the best but I had a spare slot and a spare > screen so I had to try. The CPU is a Core 2 Duo. > > Brede > > > > On 8/18/07, Jan Ciger <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Brede Johansen wrote: > > > Hi Jan, > > > > > > The framerate continues to drop so if it starts at 60Hz it slowly drops > and > > > reaches 30Hz after aproximatly 20 seconds. It is not a one time drop > due to > > > the HUD. This happens in SingleThreaded mode with a very simple model. > > > > > > Brede > > > > > > > If this is happening with a standalone viewer, then this indeed looks > > like a driver bug. I do not see this behaviour on a GeForce nor ATI > > hardware. > > > > Jan > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1.4.7 (GNU/Linux) > > Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org > > > > > iD8DBQFGxylsn11XseNj94gRAu7vAJ9yASBA0Nfy1YV30Cdou9w2RmcbogCg6wq/ > > Y4cDyO3QqkydYX/uLkqXQm0= > > =p5qa > > -END PGP SIGNATURE- > > ___ > > 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
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brede Johansen wrote: > Jan and Robert, > > This happens with the latest ForceWare release 162.18. > osgviewer from SVN. > I have two screens attached to a 8800GTX and one screen attached to a > 8600GS. I know the GS isn't the best but I had a spare slot and a spare > screen so I had to try. The CPU is a Core 2 Duo. This isn't an exactly common config, perhaps the driver doesn't know how to cope with it? Did you try to run the code on a single card only? Jan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFGxz3in11XseNj94gRAq6DAJ9V72dLTVXHzpxzMv/6jQRJN/2I4wCgpjIp vWl3QgZPYj66LIDF/pPFaew= =Oa7y -END PGP SIGNATURE- ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Jan and Robert, This happens with the latest ForceWare release 162.18. osgviewer from SVN. I have two screens attached to a 8800GTX and one screen attached to a 8600GS. I know the GS isn't the best but I had a spare slot and a spare screen so I had to try. The CPU is a Core 2 Duo. Brede On 8/18/07, Jan Ciger <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Brede Johansen wrote: > > Hi Jan, > > > > The framerate continues to drop so if it starts at 60Hz it slowly drops > and > > reaches 30Hz after aproximatly 20 seconds. It is not a one time drop > due to > > the HUD. This happens in SingleThreaded mode with a very simple model. > > > > Brede > > > > If this is happening with a standalone viewer, then this indeed looks > like a driver bug. I do not see this behaviour on a GeForce nor ATI > hardware. > > Jan > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.7 (GNU/Linux) > Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org > > iD8DBQFGxylsn11XseNj94gRAu7vAJ9yASBA0Nfy1YV30Cdou9w2RmcbogCg6wq/ > Y4cDyO3QqkydYX/uLkqXQm0= > =p5qa > -END PGP SIGNATURE- > ___ > 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] Has anyone tried 64-bit SUSE enterprise
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brede Johansen wrote: > Hi Jan, > > The framerate continues to drop so if it starts at 60Hz it slowly drops and > reaches 30Hz after aproximatly 20 seconds. It is not a one time drop due to > the HUD. This happens in SingleThreaded mode with a very simple model. > > Brede > If this is happening with a standalone viewer, then this indeed looks like a driver bug. I do not see this behaviour on a GeForce nor ATI hardware. Jan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFGxylsn11XseNj94gRAu7vAJ9yASBA0Nfy1YV30Cdou9w2RmcbogCg6wq/ Y4cDyO3QqkydYX/uLkqXQm0= =p5qa -END PGP SIGNATURE- ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hi Brede, On 8/18/07, Brede Johansen <[EMAIL PROTECTED]> wrote: > The framerate continues to drop so if it starts at 60Hz it slowly drops and > reaches 30Hz after aproximatly 20 seconds. It is not a one time drop due to > the HUD. This happens in SingleThreaded mode with a very simple model. This sounds like memory leak or similar problem, it also sounds like it may well be a driver bug that for some reason the HUD text is triggering. You could try updating drivers, and try the same app on a diffrent machine/hardware. Robert. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hi Jan, The framerate continues to drop so if it starts at 60Hz it slowly drops and reaches 30Hz after aproximatly 20 seconds. It is not a one time drop due to the HUD. This happens in SingleThreaded mode with a very simple model. Brede On 8/17/07, Jan Ciger <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Brede Johansen wrote: > > Hi, > > > > On 8/16/07, Jan Ciger <[EMAIL PROTECTED]> wrote: > >> Do you have problems displaying the stats in the osgviewer as well? > >> > > > > > > I also have a problem with the stats in osgviewer and I'm running on > Windows > > XP (32-bit) with GeForce hardware. > > The framerate starts to drop as soon as the bar graphs are enabled. The > > framerate is restored when the bar graphs are removed > > That's true, but that is likely unrelated. The framerate drop is normal, > because there are at least two rendering passes being done - one for the > main camera and one for the stats/help/whatever which are attached to a > secondary camera. > > Regards, > > Jan > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.7 (GNU/Linux) > Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org > > iD8DBQFGxhPCn11XseNj94gRAv5LAKDYbaBU1YM9JdK1Nbqb8RbjkshH1wCgqIUR > KuB/fvf1OlMwbxydjI/1rVU= > =QFdw > -END PGP SIGNATURE- > ___ > 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] Has anyone tried 64-bit SUSE enterprise
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brede Johansen wrote: > Hi, > > On 8/16/07, Jan Ciger <[EMAIL PROTECTED]> wrote: >> Do you have problems displaying the stats in the osgviewer as well? >> > > > I also have a problem with the stats in osgviewer and I'm running on Windows > XP (32-bit) with GeForce hardware. > The framerate starts to drop as soon as the bar graphs are enabled. The > framerate is restored when the bar graphs are removed That's true, but that is likely unrelated. The framerate drop is normal, because there are at least two rendering passes being done - one for the main camera and one for the stats/help/whatever which are attached to a secondary camera. Regards, Jan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFGxhPCn11XseNj94gRAv5LAKDYbaBU1YM9JdK1Nbqb8RbjkshH1wCgqIUR KuB/fvf1OlMwbxydjI/1rVU= =QFdw -END PGP SIGNATURE- ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hello Robert: Thank you for the tip. I am doing a fly through test without text to see if I get crashes. Will let that rn for several hours. I'll then try the SUBLOADING and turn the hud back on and see what happens. Thank you again Take care Garrett On Aug 17, 2007, at 5:07 AM, Robert Osfield wrote: > Hi Garret, > > On 8/16/07, Garrett Potts <[EMAIL PROTECTED]> wrote: >> I think you are right that it's a ATI problem more than likely the >> drivers for SUSE. The MAC drivers work great. > > Mac ATI drivers seem to be the only place that ATI's actually have > good drivers... > > One thing you could try is to disable the incremental subloading of > glyphs > >export OSG_TEXT_INCREMENTAL_SUBLOADING=OFF > > Robert. > ___ > 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] Has anyone tried 64-bit SUSE enterprise
Hi Garret, On 8/16/07, Garrett Potts <[EMAIL PROTECTED]> wrote: > I think you are right that it's a ATI problem more than likely the > drivers for SUSE. The MAC drivers work great. Mac ATI drivers seem to be the only place that ATI's actually have good drivers... One thing you could try is to disable the incremental subloading of glyphs export OSG_TEXT_INCREMENTAL_SUBLOADING=OFF Robert. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hi, On 8/16/07, Jan Ciger <[EMAIL PROTECTED]> wrote: > > Do you have problems displaying the stats in the osgviewer as well? > I also have a problem with the stats in osgviewer and I'm running on Windows XP (32-bit) with GeForce hardware. The framerate starts to drop as soon as the bar graphs are enabled. The framerate is restored when the bar graphs are removed. Regards, Brede ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hello Jan: Thank you for the help. I assume you are using : http:// cairographics.org/ Is there any way to release your Text Node source code? I am just curious if this will help me with the text problem. My direct email is pottscflrrcom. Thank you again for the help! Take care Garrett On Aug 16, 2007, at 4:15 PM, Jan Ciger wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > Garrett Potts wrote: >> hello Jan: >> >> Hmmm, funny you mention it. The SUSE enterprise is running on Mac >> Hardware and so yes it is an ATI board. I also have tried te osgtext >> example. It runs but is very slow. I do get the same crash issues >> with osgviewer stats hud where the text is changing on every frame >> which simulates what I am doing. It could be a driver issue. The >> MAC OSX handles it very well and I don't remember having any problems >> on the windows on the MAC running the bootcamp ATI drivers. > > It is a long standing bad driver/OSG interaction. I have the same > issue > on my laptop with a FireGL T2 card and i586 since at least two years, > likely longer. If there is any osgText in the scene, the viewer > locks up > in a busy loop, pegging the CPU at 100% load. Usually it wakes up > after > several minutes, though, without a reboot. I believe that it has to do > with the way osgText is implemented - by rendering glyphs into many > small textures which need to be generated and uploaded to the GPU when > the node is first time rendered. The subsequent triggering of stats or > help is immediate for me, only the first one is always a problem. > > I have "solved" this issue by implementing my own text widget using > Cairo and Freetype. That way I have only a single quad with a single > texture, regardless of how many characters and with what font I > render. > > Regards, > > Jan > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.7 (GNU/Linux) > Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org > > iD8DBQFGxK0In11XseNj94gRAm6PAKDoMS/09jFYGSVRD0VlJqKjhCPbxQCfTTtD > ciK3JQjZVltmuCBVbjPc3Eg= > =Hy/D > -END PGP SIGNATURE- > ___ > 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] Has anyone tried 64-bit SUSE enterprise
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Garrett Potts wrote: > hello Jan: > > Hmmm, funny you mention it. The SUSE enterprise is running on Mac > Hardware and so yes it is an ATI board. I also have tried te osgtext > example. It runs but is very slow. I do get the same crash issues > with osgviewer stats hud where the text is changing on every frame > which simulates what I am doing. It could be a driver issue. The > MAC OSX handles it very well and I don't remember having any problems > on the windows on the MAC running the bootcamp ATI drivers. It is a long standing bad driver/OSG interaction. I have the same issue on my laptop with a FireGL T2 card and i586 since at least two years, likely longer. If there is any osgText in the scene, the viewer locks up in a busy loop, pegging the CPU at 100% load. Usually it wakes up after several minutes, though, without a reboot. I believe that it has to do with the way osgText is implemented - by rendering glyphs into many small textures which need to be generated and uploaded to the GPU when the node is first time rendered. The subsequent triggering of stats or help is immediate for me, only the first one is always a problem. I have "solved" this issue by implementing my own text widget using Cairo and Freetype. That way I have only a single quad with a single texture, regardless of how many characters and with what font I render. Regards, Jan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFGxK0In11XseNj94gRAm6PAKDoMS/09jFYGSVRD0VlJqKjhCPbxQCfTTtD ciK3JQjZVltmuCBVbjPc3Eg= =Hy/D -END PGP SIGNATURE- ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Garrett Potts wrote: > hello Jan: > > Hmmm, funny you mention it. The SUSE enterprise is running on Mac > Hardware and so yes it is an ATI board. I also have tried te osgtext > example. It runs but is very slow. I do get the same crash issues > with osgviewer stats hud where the text is changing on every frame > which simulates what I am doing. It could be a driver issue. The > MAC OSX handles it very well and I don't remember having any problems > on the windows on the MAC running the bootcamp ATI drivers. It is a long standing bad driver/OSG interaction. I have the same issue on my laptop with a FireGL T2 card and i586 since at least two years, likely longer. If there is any osgText in the scene, the viewer locks up in a busy loop, pegging the CPU at 100% load. Usually it wakes up after several minutes, though, without a reboot. I believe that it has to do with the way osgText is implemented - by rendering glyphs into many small textures which need to be generated and uploaded to the GPU when the node is first time rendered. The subsequent triggering of stats or help is immediate for me, only the first one is always a problem. I have "solved" this issue by implementing my own text widget using Cairo and Freetype. That way I have only a single quad with a single texture, regardless of how many characters and with what font I render. Regards, Jan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFGxK0In11XseNj94gRAm6PAKDoMS/09jFYGSVRD0VlJqKjhCPbxQCfTTtD ciK3JQjZVltmuCBVbjPc3Eg= =Hy/D -END PGP SIGNATURE- ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hello Jan: Thank you for the insight on your experiences. Yes the stats in osgviewer produces the same problem and causes core dumps. If the osg example apps are static text where theyare set at load time and never change like in osgtext example then no crash, but is really slow to render. I think you are right that it's a ATI problem more than likely the drivers for SUSE. The MAC drivers work great. Take care Garrett On Aug 16, 2007, at 3:04 PM, Jan Ciger wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Garrett Potts wrote: >> Hello: >> >>> You might want to try and get a stack trace with gdb. If it turns >>> out >>> that you have vector iterators or OpenThreads in the stack trace, >>> then >>> it's probably a question of calling setText() while another >>> thread is >>> running the draw traversal. >>> >> >> :). Wish I could. The setText is completly hosing everything. I >> have tried the gdb on the executable. I usually have to reboot. > > Reboot?? Whoa, now that is really a bad issue. > > Do you have problems displaying the stats in the osgviewer as well? > > Jan > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.7 (GNU/Linux) > Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org > > iD8DBQFGxJ/Hn11XseNj94gRAu8/AKDBDh1F64W405vLXCb407RBOYRuRACfc66n > tqRF+r5T4CjEiOm7xr6BGPc= > =l/OI > -END PGP SIGNATURE- > ___ > 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] Has anyone tried 64-bit SUSE enterprise
hello Jan: Hmmm, funny you mention it. The SUSE enterprise is running on Mac Hardware and so yes it is an ATI board. I also have tried te osgtext example. It runs but is very slow. I do get the same crash issues with osgviewer stats hud where the text is changing on every frame which simulates what I am doing. It could be a driver issue. The MAC OSX handles it very well and I don't remember having any problems on the windows on the MAC running the bootcamp ATI drivers. Take care Garrett On Aug 16, 2007, at 3:02 PM, Jan Ciger wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Garrett Potts wrote: >> Hello All: >> >> I am having text/font issues under the 64-bit SUSE. If ever a >> setText is called on an osgText object there is a core dump that >> occurs. Note the code works fine on MAC's ad Windows. I think it >> might be related to 64-bit build on SUSE. I don't have much more >> details than this. Commenting out any of the setText code allows my >> application to run fine. I have also tried the latest dev 2.1.5 with >> the same issues. I am still poking around but do not know if I can >> resolve this quickly. >> >> > > Strange - I was running a 64bit Mandriva and it was working for me > just > fine. Do you happen to have an ATI card? They seem to "not like" > osgText > too much. > > Jan > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.7 (GNU/Linux) > Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org > > iD8DBQFGxJ9On11XseNj94gRAp4vAJ9BouXHCU8BS/lpiOkAwOMW2AGdsQCcCmtS > TjWYTwL0dD3etZnxC2l1gMA= > =3rGE > -END PGP SIGNATURE- > ___ > 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] Has anyone tried 64-bit SUSE enterprise
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Garrett Potts wrote: > Hello: > >> You might want to try and get a stack trace with gdb. If it turns out >> that you have vector iterators or OpenThreads in the stack trace, then >> it's probably a question of calling setText() while another thread is >> running the draw traversal. >> > > :). Wish I could. The setText is completly hosing everything. I > have tried the gdb on the executable. I usually have to reboot. Reboot?? Whoa, now that is really a bad issue. Do you have problems displaying the stats in the osgviewer as well? Jan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFGxJ/Hn11XseNj94gRAu8/AKDBDh1F64W405vLXCb407RBOYRuRACfc66n tqRF+r5T4CjEiOm7xr6BGPc= =l/OI -END PGP SIGNATURE- ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Garrett Potts wrote: > Hello All: > > I am having text/font issues under the 64-bit SUSE. If ever a > setText is called on an osgText object there is a core dump that > occurs. Note the code works fine on MAC's ad Windows. I think it > might be related to 64-bit build on SUSE. I don't have much more > details than this. Commenting out any of the setText code allows my > application to run fine. I have also tried the latest dev 2.1.5 with > the same issues. I am still poking around but do not know if I can > resolve this quickly. > > Strange - I was running a 64bit Mandriva and it was working for me just fine. Do you happen to have an ATI card? They seem to "not like" osgText too much. Jan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFGxJ9On11XseNj94gRAp4vAJ9BouXHCU8BS/lpiOkAwOMW2AGdsQCcCmtS TjWYTwL0dD3etZnxC2l1gMA= =3rGE -END PGP SIGNATURE- ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hello: > > You might want to try and get a stack trace with gdb. If it turns out > that you have vector iterators or OpenThreads in the stack trace, then > it's probably a question of calling setText() while another thread is > running the draw traversal. > :). Wish I could. The setText is completly hosing everything. I have tried the gdb on the executable. I usually have to reboot. > To be safe with all threading models that OSG supports, setText on an > osgText object must be called in the update traversal. I've run into > this lately myself, and the tricky part is that it won't necessarily > crash each time you call setText(), it depends on timing issues. > > Using an update callback fixed it for me. I just have a setText() I only update a text object within the update traversal of the scene graph. Thank you for the suggestion though. I am also suspect about the version of freetype being compiled in. I am downloading the latest and greatest release form freetype.org and will try that instead of the system freetype. Take care Garrett ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
HI Garret, To build the examples you need to configure the cmake to do it, via: cd OpenSceneGraph; ccmake . Then you'll see in the console a list of options, one with be OSG_BUILD_EXAMPLES set by default to OFF, just toggle this to ON, then press 'c' to configure, the 'g' to generate the Makefiles. You'll see onscreen help provide too. The just type make in the console as usual. Robert. On 8/16/07, Garrett Potts <[EMAIL PROTECTED]> wrote: > Hello Robert: > > Thank you for the fast response. > > Trying to figure out now how to enable builds of examples on the > SUSE. I will try to run the osgtext example to see. I have the font > set to "" so it uses the system font. The version of freetype > installed on the enterprise is 9.8.3. Will keep poking to see. > there is something it doesn't like. > > > Take care > > Garrett > > On Aug 16, 2007, at 2:01 PM, Robert Osfield wrote: > > > Hi Garret, > > > > I've used 64 bit Suse for several years without problems with osgText. > > Recently I've moved to 64bit Kubunto and don't see any problems > > either. I have had nothing come by that might suggest some latent 64 > > bit/linux issue. > > > > Do you have problems with osgtext running? Which version of freetype > > do you have? > > > > Robert. > > > > On 8/16/07, Garrett Potts <[EMAIL PROTECTED]> wrote: > >> Hello All: > >> > >> I am having text/font issues under the 64-bit SUSE. If ever a > >> setText is called on an osgText object there is a core dump that > >> occurs. Note the code works fine on MAC's ad Windows. I think it > >> might be related to 64-bit build on SUSE. I don't have much more > >> details than this. Commenting out any of the setText code allows my > >> application to run fine. I have also tried the latest dev 2.1.5 with > >> the same issues. I am still poking around but do not know if I can > >> resolve this quickly. > >> > >> > >> Take care > >> > >> Garrett > >> > >> ___ > >> 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 > ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hello Robert: You know that version number makes no since. I did a freetype-config --version and that is what was returned. Let me look in the usr lib directory to see if the version is tacked on there. Have to wait for a reboot. Take care Garrett On Aug 16, 2007, at 2:11 PM, Garrett Potts wrote: > Hello Robert: > > Thank you for the fast response. > > Trying to figure out now how to enable builds of examples on the > SUSE. I will try to run the osgtext example to see. I have the font > set to "" so it uses the system font. The version of freetype > installed on the enterprise is 9.8.3. Will keep poking to see. > there is something it doesn't like. > > > Take care > > Garrett > > On Aug 16, 2007, at 2:01 PM, Robert Osfield wrote: > >> Hi Garret, >> >> I've used 64 bit Suse for several years without problems with >> osgText. >> Recently I've moved to 64bit Kubunto and don't see any problems >> either. I have had nothing come by that might suggest some latent 64 >> bit/linux issue. >> >> Do you have problems with osgtext running? Which version of freetype >> do you have? >> >> Robert. >> >> On 8/16/07, Garrett Potts <[EMAIL PROTECTED]> wrote: >>> Hello All: >>> >>> I am having text/font issues under the 64-bit SUSE. If ever a >>> setText is called on an osgText object there is a core dump that >>> occurs. Note the code works fine on MAC's ad Windows. I think it >>> might be related to 64-bit build on SUSE. I don't have much more >>> details than this. Commenting out any of the setText code allows my >>> application to run fine. I have also tried the latest dev 2.1.5 >>> with >>> the same issues. I am still poking around but do not know if I can >>> resolve this quickly. >>> >>> >>> Take care >>> >>> Garrett >>> >>> ___ >>> 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 ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hello Garret, >> I am having text/font issues under the 64-bit SUSE. If ever a >> setText is called on an osgText object there is a core dump that >> occurs. Note the code works fine on MAC's ad Windows. I think it >> might be related to 64-bit build on SUSE. I don't have much more >> details than this. Commenting out any of the setText code allows my >> application to run fine. You might want to try and get a stack trace with gdb. If it turns out that you have vector iterators or OpenThreads in the stack trace, then it's probably a question of calling setText() while another thread is running the draw traversal. To be safe with all threading models that OSG supports, setText on an osgText object must be called in the update traversal. I've run into this lately myself, and the tricky part is that it won't necessarily crash each time you call setText(), it depends on timing issues. Using an update callback fixed it for me. I just have a setText() method in my callback class which saves the new text but does not set it just yet. I then attach an instance of the callback class to the osgText object, and in the callback's operator() method I call setText on the osgText object (gotten from casting the drawable given to operator()). This guarantees that the actual osgText::setText() call will be done in the update traversal, and seems to work great for me on Windows and Linux. If you need a more concrete code example just ask, but it's pretty simple. Then again I may be completely off track here. In any case, getting a stack trace is the first thing to do in order to diagnose the problem correctly. Good luck, J-S -- __ Jean-Sebastien Guay [EMAIL PROTECTED] http://whitestar02.webhop.org/ This message was sent using IMP, the Internet Messaging Program. ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hello Robert: Thank you for the fast response. Trying to figure out now how to enable builds of examples on the SUSE. I will try to run the osgtext example to see. I have the font set to "" so it uses the system font. The version of freetype installed on the enterprise is 9.8.3. Will keep poking to see. there is something it doesn't like. Take care Garrett On Aug 16, 2007, at 2:01 PM, Robert Osfield wrote: > Hi Garret, > > I've used 64 bit Suse for several years without problems with osgText. > Recently I've moved to 64bit Kubunto and don't see any problems > either. I have had nothing come by that might suggest some latent 64 > bit/linux issue. > > Do you have problems with osgtext running? Which version of freetype > do you have? > > Robert. > > On 8/16/07, Garrett Potts <[EMAIL PROTECTED]> wrote: >> Hello All: >> >> I am having text/font issues under the 64-bit SUSE. If ever a >> setText is called on an osgText object there is a core dump that >> occurs. Note the code works fine on MAC's ad Windows. I think it >> might be related to 64-bit build on SUSE. I don't have much more >> details than this. Commenting out any of the setText code allows my >> application to run fine. I have also tried the latest dev 2.1.5 with >> the same issues. I am still poking around but do not know if I can >> resolve this quickly. >> >> >> Take care >> >> Garrett >> >> ___ >> 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
Re: [osg-users] Has anyone tried 64-bit SUSE enterprise
Hi Garret, I've used 64 bit Suse for several years without problems with osgText. Recently I've moved to 64bit Kubunto and don't see any problems either. I have had nothing come by that might suggest some latent 64 bit/linux issue. Do you have problems with osgtext running? Which version of freetype do you have? Robert. On 8/16/07, Garrett Potts <[EMAIL PROTECTED]> wrote: > Hello All: > > I am having text/font issues under the 64-bit SUSE. If ever a > setText is called on an osgText object there is a core dump that > occurs. Note the code works fine on MAC's ad Windows. I think it > might be related to 64-bit build on SUSE. I don't have much more > details than this. Commenting out any of the setText code allows my > application to run fine. I have also tried the latest dev 2.1.5 with > the same issues. I am still poking around but do not know if I can > resolve this quickly. > > > Take care > > Garrett > > ___ > 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] Has anyone tried 64-bit SUSE enterprise
Hello All: I am having text/font issues under the 64-bit SUSE. If ever a setText is called on an osgText object there is a core dump that occurs. Note the code works fine on MAC's ad Windows. I think it might be related to 64-bit build on SUSE. I don't have much more details than this. Commenting out any of the setText code allows my application to run fine. I have also tried the latest dev 2.1.5 with the same issues. I am still poking around but do not know if I can resolve this quickly. Take care Garrett ___ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
