20,741
edits
| Line 48: | Line 48: | ||
== Slaving Dynamics (FDM) == | == Slaving Dynamics (FDM) == | ||
== Examples == | |||
For setting up slaved visual channels, here are some of the options I have used: | |||
<pre> | |||
--enable-game-mode (--enable-fullscreen depending on glut vs. sdl) | |||
--prop:/sim/menubar/visibility=false | |||
--prop:/sim/ai/enabled=false (prevents the ai ATC text at the top of the screen.) --prop:/sim/ai-traffic/enabled=false (prevents strange planes from flying across a single view) | |||
--prop:/sim/rendering/bump-mapping=false | |||
--fov=35 | |||
--prop:/sim/view/config/heading-offset-deg=-35 | |||
--prop:/sim/view/config/pitch-offset-deg=3 | |||
--native-fdm=socket,in,60,,5505,udp | |||
--native-ctrls=socket,in,60,,5506,udp | |||
--fdm=null | |||
</pre> | |||
== Troubleshooting == | == Troubleshooting == | ||
Check the hardwired version number in the packet. That will get incremented when the structure changes. It's also there if you want to get crazy and build a system that can read the packet version and decode it differently for different versions. I suspect there probably was a change | Check the hardwired version number in the packet. That will get incremented when the structure changes. It's also there if you want to get crazy and build a system that can read the packet version and decode it differently for different versions. I suspect there probably was a change | ||