20,741
edits
Implementing VNAV support in FlightGear: Difference between revisions
Jump to navigation
Jump to search
Implementing VNAV support in FlightGear (view source)
Revision as of 08:27, 6 December 2013
, 6 December 2013→I/O
(→I/O) |
(→I/O) |
||
| Line 243: | Line 243: | ||
--fdm=null --native-fdm=socket,in,60,,5600,udp | --fdm=null --native-fdm=socket,in,60,,5600,udp | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Obviously, it would also make sense to directly start up FlightGear at a location close to your initial FDM settings. | |||
(Type of aircraft doesn't really matter, the FDM output will be applied to any model, no matter if it's a 747, the ufo or the ogeL). | (Type of aircraft doesn't really matter, the FDM output will be applied to any model, no matter if it's a 747, the ufo or the ogeL). | ||
| Line 251: | Line 252: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Typically, you'll however want to use FGScript to create a completely | Typically, you'll however want to use FGScript to create a completely scripted JSBSim run, which allows you to easily test new FDM features (and simulated systems) non-interactively. | ||
=== Adding new Functions === | === Adding new Functions === | ||