Unable to change radio decimal after 1.1 update

[osvaldsson]

Hi,

After updating to v1.1 the radio decimal (PFD radio inner knob) does not work unless I scroll super fast with my mouse scroll button. Slow or binding to joystick buttons does not work.

Radio whole numbers and other rotating knobs seem to work fine.

I have reinstalled completely, 3 times, both into old directory as well as into a new one.

Any advice appreciated,

/Oli

Edited November 6, 2020 by osvaldsson
Correcting PFD and not MFD

[Coop]

Is this only with the popup G1000 or also with the 3D cockpit and/or hardware?

[osvaldsson]

1 hour ago, Coop said:

Is this only with the popup G1000 or also with the 3D cockpit and/or hardware?

Happens with both, and also if I bind the action to buttons on my joystick.

[osvaldsson]

Would it be possible to downgrade to 1.0 somehow and see if it is fixed going back?

[Coop]

There is no method to downgrade. 

I have tried to replicate this and I can not. I would recommend checking what other plugins you have, or perhaps a stuck button on a joystick. The radio commands are default X-Plane commands, so this issue most likely exists with something outside of the SR22 aircraft. 

[John T.]

I don't seem to be having this issue either.

I have never used the COM button on the MFD but did just give it a try when in pop-out mode.  Knobs spin fine.  The only weird thing is that it was tuning the COM 2 frequencies even though the cursor is set on COM 1.   That being said it's somewhat moot based on the way the Cirrus functions (no COM on MFD).

 COM button on PFD works fine.

[osvaldsson]

I'll try and do a fresh X-plane install today and see how it goes.

 

It's not the peripherals as I've tried removing all of them. This also only affects the SR22 (and only this specific function), all other aircraft are fine.

 

And this is the PFD, not the MFD. That was my wires crossing. Left screen with the COM rotating knobs on the right side.

Writing on my phone but will upload a larger overview screenshot when I get to my computer.

Edited November 6, 2020 by osvaldsson
Adding the screenshot

[osvaldsson]

Fresh X-Plane install works fine, now I just have to figure out what is causing the conflict. Will report back here when I find it.

[osvaldsson]

Thanks for the help, I found the culprit to be a Lua script in FlyWithLua NG that had 

require("radio")

at the top, removing the script, or even commenting out that single line made the problem go away.

[osvaldsson]

Just to close this out, FlyWithLua has a built in module called radio.lua which executes the following code, amongst other things for consistency within scripts:

dataref("COM1_STDBY", "sim/cockpit2/radios/actuators/com1_standby_frequency_hz", "writable")
dataref("COM2_STDBY", "sim/cockpit2/radios/actuators/com2_standby_frequency_hz", "writable")

Setting those to "readable" will solve the issue, but doesn't help for those that intend to write to the datarefs from their Lua scripts. Using the 8.3 khz spacing datarefs will also fix the problem.

dataref("COM1_STDBY", "sim/cockpit2/radios/actuators/com1_standby_frequency_hz_833", "writable")
dataref("COM2_STDBY", "sim/cockpit2/radios/actuators/com2_standby_frequency_hz_833", "writable")

 

[Aleksandar]

Hey guys, just as a tip to get frequencies even faster....right above the keypad on the console is the "COM" button.  You can press that, enter the frequency on the keypad, press enter, and transfer it over.  If you see that there are FMS / COM / NAV buttons....that means you can use that number pad to enter information into either of those systems.  Much quicker than rotating knobs.  Sometimes it bugs out, but I found that if I enter XXX.YYY <enter> <--> it works fine. Ex: 119.3 would be entered as 119.300.

Happy IFR-ing.!