4.10 and Devicelink for new Axis-Functions

[Artist]

Jack,

that is what I would do . See: As all get methods that deliver information on the status of the aircraft are disabled when flying online, I never used them. In YaDeLi I used only set methods and for multiple engine support I did just that: When you assign power for engine #1 to axis A and for engine #2 to axis B YaDeLi would, when you move an axis, select the attached engine first and then send the power change command...

The get methods for your information seem to behave differently, as their get method has a parameter for engine index (see DeviceLink.txt) - so you would not have to select the engine first.

Concerning DeviceLink.txt, Team Daidalos, and multiple engine support in version 4.10: The capabilities of DeviceLink haven't changed since 2004 (I guess) and Team Daidalos has not changed anything there - which is not that bad as we can workaround the limitations.

Artist

[Skip_Jack]

Artist, thanks for the information and sticking with me on the noobish questions and going a little off course.

I'm going to spend some more time reviewing the devicelink txt while also checking the device link tips and question thread over at ubi and see if I can come up with something that works. Again, thank you

[bolox]

skip jack, you may want to look here
http://www.hruks.com/forum/viewtopic.php?t=302

particularly version 1.6- multi engine parameters available