fly/fgdata
1
0
Fork 0
Code Activity

Mathias Fröhlich:

Browse source 
Limit the maximum time we spent in the simulation loops.
That means, if the /sim/max-simtime-per-frame value is strictly positive
you can limit the maximum amount of time you will do simulations for
one frame to display. The cpu time spent in simulations code is roughtly
at least O(real_delta_time_sec). If this is (due to running debug
builds or valgrind or something different blowing up execution times)
larger than the real time you will no more get any response
from flightgear. This limits that effect. Just set to property from
your .fgfsrc or commandline ...
This commit is contained in:
ehofman 2006-01-30 10:36:20 +00:00
parent 24139b8600
commit a94b00c976
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
preferences.xml
View file

@ -18,6 +18,9 @@ Started September 2000 by David Megginson, david@megginson.com
<!-- don't reset the simulator when the aircraft hits the ground -->
<reset-on-crash type="bool">false</reset-on-crash>
<!-- Limit the time we need to spend in simulation loops to 1 second -->
<max-simtime-per-frame>1.0</max-simtime-per-frame>
<intl include="Translations/locale.xml"/>
<aircraft>c172p</aircraft>
<virtual-cockpit type="bool">false</virtual-cockpit>