VRi MCP Combo II (Boeing) COM/NAV digits inc/dec

[tzagman]

VRi MCP Combo II (Boeing)

MSFS with PMDG737

FSUIPC7 v7.4.12

LINDA_4_1_5_289 with PMDG_737_v0_6

===============

COM and NAV decimal digits not inc/dec by one.

Any solution?

Thanks in advance

[John Dowson]

1 hour ago, tzagman said:

COM and NAV decimal digits not inc/dec by one.

Any solution?

What have you tried? Have you tried these custom events for the COM1:

Quote

#define EVT_COM1_INNER_SELECTOR                            (THIRD_PARTY_EVENT_ID_MIN + 727)

There are also presets available that use those custom controls:
    PMDG_B737-7_COM1_RADIO_FRACT_INC
    PMDG_B737-7_COM1_RADIO_FRACT_DEC

There are similar custom events and presets for COM2 and COM3.

And for NAV1 - custom control:

Quote

  #define EVT_NAV1_INNER_SELECTOR                            (THIRD_PARTY_EVENT_ID_MIN + 732)

and preset:
    PMDG_B737-7_NAV1_RADIO_FRACT_DEC 
    PMDG_B737-7_NAV1_RADIO_FRACT_INC

If not familiar with PMDG custom controls, see 

   For presets, check Select for Preset and then Find Preset... and click-through the MobiFlight presets to find the preset. You can also use https://hubhop.mobiflight.com/presets/ to search for presets. This is the MobiFlight HubHop site that is the community effort to share aircraft presets, all of which are included with FSUIPC7 (or at least the latest presets at time of release).

John

[tzagman]

Thank you for the response!

I am familiar with PMDG custom controls.
There is not a problem to use them with FSUIPC assignments.
But this is not the case.

As I mentioned, I use 'VRi MCP Combo II' (Boeing) which is supported by FSUIPC with LINDA lua scripting.
It is well supported for MSFS PMDG737 except the COM and NAV decimal digits inc/dec.
If I assign the rotary knob manually in FSUIPC (as you mentioned) it interferes with the lua control.

I have two choices:

1)  Modify LINDA's script (not easy for me) I’ve searched LINDA support forum in Avsim about this with no luck.
Can you help me to this? (I attach ‘RADIOS COMMON’ module from ‘common.lua’ file)

2)  Deactivate LINDA's MCP and configure it manually using FSUIPC assignments (or even use Spadnext but I prefer to keep LINDA for the VRi MCP)
How can I use FSUIPC assignments for the SAME rotary knob (there’s a single one at the right part of Vri MCP combo) so that I’ll be able to change both NAV and COM separately?

 

I could also use AXISandOHS with existing MCP Combo Templates and Scripts, but I have built a handmade cockpit using Opencockpits SIOC.
If I change now FSUIPC with AXISandOHS, I should assign everything from the scratch. 
FSUIPC is my favorite. I have bought all versions from the early years until now.
Thank you for your support!

-- ## RADIOS COMMON ###############.lua

Edited June 5 by tzagman

[John Dowson]

14 minutes ago, tzagman said:

I have two choices:

1)  Modify LINDA's script (not easy for me) I’ve searched LINDA support forum in Avsim about this with no luck.
Can you help me to this? (I attach ‘RADIOS COMMON’ module from ‘common.lua’ file)

No. LINDA is no longer supported by the developer. I have never used LINDA and just haven't got the time to look into it and support it, sorry. Especially for VRI devices, which I also know very little about.

15 minutes ago, tzagman said:

2)  Deactivate LINDA's MCP and configure it manually using FSUIPC assignments (or even use Spadnext but I prefer to keep LINDA for the VRi MCP)
How can I use FSUIPC assignments for the SAME rotary knob (there’s a single one at the right part of Vri MCP combo) so that I’ll be able to change both NAV and COM separately?

How do you know when it controls COM and when it controls NAV? 
If you want a button/switch (including rotary buttons) to send different controls, then you need something else that this depends on, e.g. another button or maybe an offset.
Lets assume you are using another button or switch, so when this switch is down/off, the rotary controls NAV, and when up/on, it controls COM.
So, on the rotary, you would assign the left/righ buttons to decr/incr both NAV and COM. Then you would add a compound button condition to those assignments, so that the assignment triggered would depend on the state of your other button/switch. See the section on Compound Button Conditions in the Advanced User guide, page 22.

 

[tzagman]

Thank you! 👌