Re: [osg-users] Frame rate hit using OSG 2

On 9/7/07, Gert van Maren [EMAIL PROTECTED] wrote: Hi Donn, We went across this week and are getting the same. About 40% drop in framerate with certain paged data sets. Curious. 2.x and 1.2 are still fundamentally the same scene graph. CullVisitor and DatabasePager changed little in the 1.2

Re: [osg-users] Error in Image.cpp

Hi Art, J-S et al. The - was meant to be a = and a case of finger wobble and the me not spotting any compiler warning for it. The has now been fixed and checked in. Curious I'm have aggressive warnings turned out right now, as I've been merging warning fixes and make fixes of my own. I guess

[osg-users] Help - trying to get a wxWidgets implementation of osgViewer::Viewer working!

I have just re-implemented my wxWindows implementation of osgViewer to use osgViewer::Viewer instead of the old SimpleViewer. The code is very heavily based on the osgviewerWX example (as was the old version!). I have come across two problems. 1. I cannot get the TrackballManipilator to work.

[osg-users] osgText precision issue

I'm having a bit of trouble with mangled text if I zoom in to close. This text is on an osgDem generated ellispoid. In the attached screenshots, the text appears correctly in text2.jpg. However, in text3.jpg you'll see the problem. This only occurs if I zoom in really close to the text. If I back

Re: [osg-users] osgText precision issue

Years ago, we wrote an earth-viewer program in which we had a requirement that we had to be able to zoom all the way from space, down to an item the size of a quarter and smaller, smoothly. Your images look like an issue we had at the time, which was a floating point precision problem. The

Re: [osg-users] osgText precision issue

Yeah, that sounds like it will do the trick. I'll have to re-work some code, but that should address the issue. On 9/8/07, Jason Beverage [EMAIL PROTECTED] wrote: Hi Sherman, The issue you're seeing is probably a precision issue since OpenGL works in floats. I've seen a similar effect with

Re: [osg-users] osgText precision issue

The other thing to do, and the most important, is to locate the local origin where your text is *before* converting to floats. This will give you the most accuracy. I know the problem well and how to solve it, but don't know OSG so can't tell you how this is done in OSG. best of luck, chris On