Hi all, I have a request: Can we reduce the default value for the property max-simtime-per-frame in preferences.xml to something a lot smaller than 1 second, like e.g. 0.1 (which I use myself).
The reason for this request is that the external forces my airships use for mooring are computed based on properties (namely the aircraft position in /position/*) that are updated for each frame but act at the JSBSim FDM rate (120 time steps per simulated second). When the frame rate is very low, e.g. during startup this results in the mooring forces staying constant for up to 1 simulated second during which the aircraft might have accelerated considerably, with usually disastrous results. Restricting that time to 0.1 seems to be enough to avoid most problems. The best solution to this problem is, of course, to compute the needed position at FDM rate (in JSBSim) and I'm (slowly) looking into how to implement that. However, I cannot think of any common case where it is useful to allow the FDM to run in the blind for 1 second. Restricting the simulation time per frame to 0.1 means simulation time slows down compared to real time when the frame rate drops below 10 frames per second. I suppose this might limit the amount time acceleration available on slow systems, but other than that I don't see any problems. Cheers, Anders -- --------------------------------------------------------------------------- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
