#Aerobask X-Plane 12 Diamond DA50RG

1 messages · Page 1 of 1 (latest)

fluid jasper
#

I am trying to use an On-Off switch in Mobiflight to control the cowl flaps in Aerobask Diamond DA50RG. For some reason, the cowl lever jumps back to its initial position in the sim when the "On Press" tab is used. The "On Hold" seem to have no effect. I have watched YouTube videos on this, but only get videos explicitly for MSFS. In my previous query, @versed mirage mentioned "The difference is in the datarefs presets used by Xplane". Problem is, I cannot use the "aerobask/eng/sw_cowl_flaps_1=0" dataref to set the cowl flaps to the closed position, it causes the problem mentioned above. Any help will be greatly appreciated.
B.T.W the default X-Plane datarefs do not work in this case.

remote pilot
#

I think you need to use a command instead of a dataref. If you use datareftool, and put it on change. You can click the switch in the cockpit and see which commands are fired. A lot of datarefs don’t work when they’re written to, but require a command to be sent

fluid jasper
# remote pilot I think you need to use a command instead of a dataref. If you use datareftool, ...

I have tried the command, BUT it is only a toggle (no command for "OFF" or "ON". So, if the Cowl switch lever is in the "OPEN" position when the sim is started, mobiflight will toggle it to "CLOSED". Now the switch will be in the "OPEN" position, but the sim shows "CLOSED". I have used the "COMMAND" option with succes on other switches. THIS is mainly the reason I asked about a dedicated Mobiflight X-Plane manual. Most videos use MSFS, but you cannot simply apply information in the MSFS videos to X-Plane. It does not work!

remote pilot
#

Ahh that is a very common issue! I solved this by creating a lua script, and creating my own commands in that

fluid jasper
vital shore
#

Another solution for this:

  1. create an output that shows the actual value (0 or 1)
  2. create 2 input events for the same switch
  3. 1st - precondition: output = 0 -> action: on-press..command
  4. 2nd - precondition: output = 1 -> action: on-release..command
    (OR 1 and 0 are reversed).
    You'll see, then it always stays in sync.