- Joined
- Mar 31, 2012
- Messages
- 2,298
- Reaction score
- 4
- Points
- 0
There's a new game
We like to play you see
A game with added reality
We call it -- master and servant
XR-1 Master/Slave, ready for takeoff. Right Orbiter instance is master, left and center are slaves.
Florida below.
Master and slave MFDs are independent.
Flying over the East Coast. Virtual cockpit on slave, glass cockpit on master.
Edit 2014-01-08. New version (rev28) is available, announcement and list of changes here
Edit 2013-12-29. New version (rev25) is available, announcement and list of changes here
Edit 2012-09-26. The XR2 bug is now fixed.
Edit 2012-09-13. README and release below.
Orbiter Master - Slave
======================
This add-on copies the simulation state real-time from a single master instance to multiple
slave instances. Communication is performed using UDP protocol.
Slave instances run independetly of the master instance, except that the simulation state
(that is, MJD, vessel state and location) is copied from master to slave(s) every frame.
Limitations:
Generally speaking, only the data exposed through VESSEL, VESSEL2 and XRVesselCtrl interfaces
are shared between instances. In particular, it means that:
- (un)docking is not supported (okay, I plan to fix *that* one)
- UMMUs are not supported (will appear differently on master and slave)
- UCGOs are not supported (will appear differently on master and slave)
- some DG-IV-specific features are not supported
This add-on is released under the GPL-2.0 license.
Orbiter Master - Slave launch chekclist
---------------------------------------
0. If you want to run multiple Orbiter instances on the same computer, install and enable
this add-on: http://orbiter-forum.com/showthread.php?p=241888&postcount=13
1. Unpack the add-on, and edit Config\OrbMaster.cfg and Config\OrbSlave.cfg to suit your needs.
2. Start master instance: start Orbiter, enable OrbMaster.dll module, launch the simulation.
The master will periodically (every 10s) save current simulation state to the scenario named
000MasterSlave. The slave needs this file at startup. If you want to put master and slave(s)
on different computers, put your Orbiter install on a network share or use some other means
to transfer the scenario file to the slave (HTTP, FTP, ...).
NOTE: if waitForClients=1 in OrbMaster.cfg, the master will hang during startup until the
first client connects.
3. Launch orbiter, disable OrbMaster.dll, enable OrbSlave.dll. Load scenario 000MasterSlave
and launch the simulation.
NOTE: NEVER have both OrbMaster.dll and OrbSlave.dll enabled in one instance at the same time!
4. If you notice that the simulation state on the slave diverges from that on master, kill
the slave and restart it as per step 3. This causes a full scenario reload.
Attachments
Last edited:
