Dual control: Difference between revisions

Jump to navigation Jump to search
Fixed links etc.
(New page: This is an add-on for FlightGear that adds basic support for shared control of an aircraft over the FlightGear multiplayer network. The main part is a set of ...)
 
(Fixed links etc.)
Line 1: Line 1:
This is an add-on for [[FlightGear]] that adds basic support for shared control of an [[aircraft]] over the FlightGear [[Multiplayer Howto|multiplayer network]]. The main part is a set of generic [[Nasal]] modules and modified instrument files that form the core of the networked shared control functionality.  
This is an add-on for [[FlightGear]] that adds basic support for shared control of an [[aircraft]] over the FlightGear [[Multiplayer Howto|multiplayer network]]. The main part is a set of generic [[Nasal scripting language|Nasal]] modules and modified instrument files that form the core of the networked shared control functionality.  


'''Note:''' The Open Scene Graph based FlightGear/CVS (developer's version) is needed to use this add-on. The aircraft will load in FlightGear 1.0.0 too but the copilot cannot see or touch anything in the cockpit.  
'''Note:''' The Open Scene Graph based FlightGear/CVS (developer's version) is needed to use this add-on. The aircraft will load in FlightGear 1.0.0 too but the copilot cannot see or touch anything in the cockpit.  


Feel free to drop me an e-mail (see bottom of page for the address) if you find some of this software useful or have other comments, suggestions or questions.
[http://www.gidenstam.org/FlightGear/DualControl The main page for this add-on.] A summary of the information follows below.


==Aircraft==
==Aircraft==
The tar.gz archive for each aircraft should be extracted in $FG_ROOT/Aircraft/. You can find archives for all aircraft below in [http://www.gidenstam.org/FlightGear/DualControl/Aircraft the hangar].  
The tar.gz archive for each aircraft should be extracted in $FG_ROOT/Aircraft/. You can find archives for all aircraft below in [http://www.gidenstam.org/FlightGear/DualControl/Aircraft the dual-control aircraft hangar].  


Currently there is only one aircraft with dual control support.
Currently there is only one aircraft with dual control support: A c172p Skyhawk with dual control (c172p-pilot and c172p-copilot) which is based on David Megginson's [[Cessna C172|c172p]] single control aircraft.  
 
[http://www.gidenstam.org/FlightGear/DualControl/Aircraft/c172p-dual_fgfsCVS.tar.gz c172p Skyhawk with dual control (c172p-pilot and c172p-copilot)]
 
This aircraft is based on David Megginson's [[Cessna C172|c172p]] single control c172p.  


The aircraft enables a pilot and copilot to jointly fly the aircraft over the FlightGear multiplayer network. Pilot and copilot currently have shared control over primary flight controls, throttle, mixture, elevator trim, flaps, brakes, cockpit switches, part of the radio stack and some  instrument settings. The copilot has a subset of the full instrumentation, including airspeed, altimeter, VSI, HSI, turn coordinator, engine RPM and the radio stack. NavComm 1 and the first VOR indicator is best controlled by the pilot, while NavComm 2 and the corresponding VOR indicator is faster for the copilot.
The aircraft enables a pilot and copilot to jointly fly the aircraft over the FlightGear multiplayer network. Pilot and copilot currently have shared control over primary flight controls, throttle, mixture, elevator trim, flaps, brakes, cockpit switches, part of the radio stack and some  instrument settings. The copilot has a subset of the full instrumentation, including airspeed, altimeter, VSI, HSI, turn coordinator, engine RPM and the radio stack. NavComm 1 and the first VOR indicator is best controlled by the pilot, while NavComm 2 and the corresponding VOR indicator is faster for the copilot.
Line 28: Line 24:
'''Copilot usage example:'''
'''Copilot usage example:'''
  fgfs --aircraft=c172p-copilot --prop:/sim/remote/pilot-callsign="anybody"
  fgfs --aircraft=c172p-copilot --prop:/sim/remote/pilot-callsign="anybody"
Note: The copilot will want to reset the view (ctrl-v) to avoid jitter as external views are jitter prone (this will be fixed later).
Note: The copilot will want to reset the view (ctrl-v) to avoid jitter as external views are jitter prone.
 
'''Status:''' Beta, perfectly flyable but some functions are not yet shared between the pilot and co-pilot.
789

edits

Navigation menu