You find it strange that you are put into a machine positioned on RWY28R? In your dhc2 water plane, or the bo105 helicopter? No more!
Here's a small Nasal script that allows to save the parking position and overall state (parking brake, doors, beacons) on a per-aircraft basis. This encourages you to always leave the aircraft in a sane state on a sane place. Because next time you start fgfs with it, you'll have to deal with it! HOTWO ===== (1) download http://members.aon.at/mfranz/flightgear/state.nas [2.8 kB] (2) set FG_HOME on top of the file to a writable directory (3) add key binding to your keyboard.xml (see top of script) -- first run -- (4) start fgfs with your favorite aircraft (5) you'll end up on 28R as always; nothing to see here :-/ (6) whenever you feel like it, press the `-key to save the state; ideally when you've parked the aircraft and are about to exit from fgfs -- next run -- (7) start fgfs with same aircraft and find yourself parked where you left You can set the default in the script file (whether states should be retstored or not), and can always override with --prop:state=0. The script stores position, heading, controls, and /sim/model/<aircraft>. Not all aircraft have their private settings in /sim/model/<aircraft>. The bo105 and a few others have. That means, that you'll even find the bo105 doors open when you left them open. :-) The script does not autosave a state on exit. This would be possible with a few changes, but I thought that it's probably not such a good idea. Saving should be done when leaving the aircraft and locking the door. Not when you crashed it somewhere in the woods. Note: don't park on houses! The FDMs don't recognize that and put the aircraft *into* the house on ground. m. _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
