We have several sections through which synchronization can occur. So, where to put each dataref we need? The planes we tried to work on had a very varied approach on the implementation of the systems. One thing is for sure – the transmission of positioning data from the Master to the Slave machine works. It is important to understand that the Slave will fly like the Master, even if its own systems will not work. All we have to do is to make the instruments work the same as on Master (or in worst case make a visual representation of working instruments). The ideal case is described in a section below, but before is a list of recommended steps in creating a config file for existing addons.
Please look at what Ben Supnik says which datarefs to use:
- Try to use
sim/flightmodel2 when possible;
- More recent datarefs are usually better;
- Use the most useful dataref you can find.
In the same article it is also mentioned that the commands are more preferable than datarefs. So I would recommend starting with the commands. But, unfortunately, there are many cases where the commands won’t work. Often cockpit manipulators are not assigned to the commands which mean that when you press the hot key, the action will be transmitted, and when you click the mouse on the corresponding manipulator in the virtual cockpit, nothing happens. However, for example, in the default Baron B58 3D manipulators of the starter switches will call Ignition command and respectively transmission through the command will work here.
If command synchronization does not work for some functions go to the section TRIGGERS. But in this section try to avoid any dataref which changes value very frequently. Initially, this section is assumed only for the transmission of buttons and switches, instrument manipulators and so on. For example, all light switches, the course and heading knobs are the best candidates in this section. If dataref changes own value very often, think about moving this dataref to CONTINUED section. Or better yet, it may be possible to do synchronisation without this dataref or to implement this feature in any other manner.
SEND_BACK section should not cause much difficulty.