Hi & welcome !
I think we've seen a handful of postings confirming this - if you're able to build from source and don't mind using development looks like the built-in profiler, it would be interesting to see comparison of both builds - ideally using a simple test case with everything else disabled - you could use a pre-recorded flight and/or a flight recorder type to come up with a "test flight". From our standpoint, it would help tremendously if all features that don't seem to have an effect could be completely disabled, including complex aircraft and scenery/locations. In other words, if you can reproduce the problem using "bare" minimum settings, the resulting log file will be much easier to process.
There's a built-in profiler which you can use to create these profiles:
http://wiki.flightgear.org/Built-in_ProfilerYou would then want to use two different build directories, where SG/FG build settings would be identical, but using an older version of OSG:
http://wiki.flightgear.org/Building_usi ... irectoriesFor the sake of simplicity there's a so called "minimal startup profile" that you can use:
http://wiki.flightgear.org/Howto:Debugg ... up_profileWhile unlikely, it would be great if the issue could be reproduced that way - but more likely than not, you'll have to re-add a few features and change a few settings, e.g. by using a different location.
Like I said, you could then use the replay system to create an test flight than can be easily reproduced - to get going more quickly, you can also use the built-in route manager to create a simple flight plan and fly the whole thing on autopilot:
http://wiki.flightgear.org/Instant_ReplayYou can use time warp mode to speed up simulation time and finish more quickly.
Admittedly, all this may seem a bit intimidating and tedious, but once you have such a setup working, you can reuse it over and over again for different startup profiles and provide profiling logs for each.
We do have a number of people interested in adding features to support benchmarking/profiling workflows natively:
http://wiki.flightgear.org/FlightGear_Benchmarkhttp://wiki.flightgear.org/TestingIf that's something you'd like to pursue, feel free to get in touch - it is definitely a worthwhile thing, even regardless of any OSG specific issues, as it will also help with unrelated performance issues.
Obviously, there's a bit of a steep learning curve involved, which is why it's normally only core developers that build multiple versions against different OSG versions and run the profiler.
But once you are able to build from source, you have already completed the most difficult step - everything else is fairly straightforward in comparison - as as you can probably tell, creating test flights using the route manager and/or flight recorder also isn't exactly rocket science.
However, before you do anything, I'd suggest to check first if you've possibly changed your driver, or if you can install a newer version:
Subject: OSG 3.0.1 -> 3.2.0 cuts frame rate in halftikibar wrote:Hi Everyone,
I'm wondering if anyone has any suggestions on how to improve performance with OpenSceneGraph 3.2. I built (from source) 2 instances of FG 3.0.1, one built against OSG 3.0.1 and one with OSG 3.2.0. With OSG 3.0.1, I was getting decent frame rates (~30 fps / under 50 ms). Using the FG build with OSG 3.2, the frame rate went down to around 15 fps and best spacing was ~75 ms. All the other settings (ALS, shader levels, real weather on, aircraft) were identical. The only difference was the OSG version.
For the record:
OS Ubuntu 10.04 64bit
FG 3.0.1
nVidia GTX 550
Problem tested with 747-8i/F, 757-200 (newer git version), and 777-300ER.
In both cases, console warning to upgrade my graphics driver from 290 to 300.
I get the same frame rate problem in FG-git, since OSG 3.2 is now required.
Cheers,
tikibar
Edit: I went ahead and upgraded the driver to 304. Performance with OSG 3.0.1 is even a little better now. OSG 3.2.0 frame rate/spacing is unchanged at best, and maybe a little worse.
Edit2: Fixed it. After upgrading the nVidia driver, I had to rebuild OSG 3.2.0 from source, then rebuild SimGear and FlightGear. Now getting acceptable frame rates in FG 3.0.1 and FG-git. Carry on.