Richard wrote in Sat Sep 10, 2016 8:49 pm:This is indeed a giant leap.
For all sim-kind
In that while I'm in a different aircraft, flightgear could run "SpaceShuttle-launch" all on its own soon as this demo is loaded.
I removed flightgear temporary folder from user's files and now neither CRT or HUD are working
Ok, long since last time I flew the shuttle, so I updated FG to 2016.3.1 and Space Shuttle up to last version in the repository and now it takes dlike 15 minutes to open the scenario...
Thorsten wrote in Fri Oct 21, 2016 7:19 am:Ok, long since last time I flew the shuttle, so I updated FG to 2016.3.1 and Space Shuttle up to last version in the repository and now it takes dlike 15 minutes to open the scenario...
Loading subsystems is the detailed cockpit mesh most likely.
Try to open preferences.xml in FGData and uncomment
<multithreading-mode>AutomaticSelection</multithreading-mode>
this will thread out model loading. Helps a lot here with startup times.
<model>
<path>cockpit-detailed.xml</path>
<offsets>
<x-m> 0 </x-m>
<y-m> 0 </y-m>
<z-m> 0 </z-m>
</offsets>
<condition>
<equals>
<property>/sim/config/shuttle/detailed-flightdeck</property>
<value>1</value>
</equals>
</condition>
</model>
Thorsten wrote in Wed Nov 02, 2016 12:08 pm:Please open Models/SpaceShuttle.xml and localize
- Code: Select all
<model>
<path>cockpit-detailed.xml</path>
<offsets>
<x-m> 0 </x-m>
<y-m> 0 </y-m>
<z-m> 0 </z-m>
</offsets>
<condition>
<equals>
<property>/sim/config/shuttle/detailed-flightdeck</property>
<value>1</value>
</equals>
</condition>
</model>
close to the beginning of the file, then comment out the section and see whether this improves the situation (this will make the detailed mesh inaccessible, but at least we know the culprit if this works). Maybe eventually we can convert the mesh into an OSG native binary format to speed things up...
Also, expect an unusually long loading time (= much more than FG usually takes) because the simulation really needs to load a lot of stuff - for instance I doubt there's another plane that needs to parse more than 40 detailed avionics pages for nine screens.
For devel purposes, I usually work with 2-3 screens active only to improve loading times, so it really hits all of us.
Users browsing this forum: No registered users and 4 guests