789
edits
m (→Known problems) |
|||
Line 86: | Line 86: | ||
==Multiplayer dual control== | ==Multiplayer dual control== | ||
This aircraft equipped for dual control over the FlightGear multiplayer network. | This aircraft is equipped for dual control over the FlightGear multiplayer network. | ||
To use this feature the pilot sets the property /sim/remote/pilot-callsign to the callsign of the prospective copilot. This property can be set in the property browser, on the command line or in fgrun. Command line example: | To use this feature the pilot sets the property /sim/remote/pilot-callsign to the callsign of the prospective copilot. This property can be set in the property browser, on the command line or in fgrun. Command line example: | ||
Line 96: | Line 96: | ||
<b>Note:</b> | <b>Note:</b> | ||
1. If the pilot sets /sim/remote/pilot-callsign at runtime the copilot | 1. If the pilot sets /sim/remote/pilot-callsign at runtime the copilot should join MP <i>after</i> the pilot set /sim/remote/pilot-callsign or things won't work correctly. This will be improved in a future version. | ||
2. Using the ZLT-NT-copilot it is possible to hitch a ride with any ZLT-NT on MP. However, unless you are the pilot "approved" copilot you will only be an observer (and will not, if there is no approved copilot, receive the full aircraft state from the pilot). | 2. Using the ZLT-NT-copilot it is possible to hitch a ride with any ZLT-NT on MP. However, unless you are the pilot "approved" copilot you will only be an observer (and will not, if there is no approved copilot, receive the full aircraft state from the pilot). |
edits