735
edits
MP Fallback models: Difference between revisions
no edit summary
(+ See also: Howto:Animate models, forum topic and developer mailing list threads) |
No edit summary |
||
| Line 34: | Line 34: | ||
</PropertyList> | </PropertyList> | ||
</syntaxhighlight> | |||
== Testing fallback models == | |||
The easiest way to test if a fallback model is working is by using two instances of flightgear connecting locally with each other for MP. To do this you first need to ensure that you have no FG_AIRCRAFT paths set (this ensures that flightgear will use the FGDATA AI/Aircraft). | |||
Then start two separate instances, e.g. | |||
<syntaxhighlight> | |||
# Instance loading the aircraft (in this case the spitfire) | |||
fgfs --multiplay=out,10,127.0.0.1,5000 --multiplay=in,10,127.0.0.1,5001 --callsign=Test1 --disable-fullscreen --aircraft=spitfireVb --airport=EG32 --geometry=800x600 --fg-aircraft=/home/stuart/FlightGear/fgaddon/Aircraft | |||
# Instance loading the ufo to view the above aircraft | |||
fgfs --multiplay=out,10,127.0.0.1,5001 --multiplay=in,10,127.0.0.1,5000 --callsign=Test2 --disable-fullscreen --aircraft=ufo --airport=EG32 --geometry=1280x1000 --altitude=100 --offset-distance=0.1 | |||
</syntaxhighlight> | </syntaxhighlight> | ||