Mcp combo 1 vrinsight Alt sel

[Paolo De Sanctis]

hello, i am new to the forum and i thank everyone in advance for any solutions to my problem. i am using the asobo 737 max in msfs2024 with my vrinsight mcp combo 1. i managed to make it work but i cant figure out how to set the reference altitude. the encoders that regulate course, heading, speed and baro worked immediately without me setting anything but the altitude does not work. i cant figure out how to set it with fsuipc. regards

[John Dowson]

Have you configured FSUIPC to handle your VRInsight MCP?

Can FSUIPC see the (rotary) buttons of the alt select knob in the buttons assignment panel? And if so, what is this assigned to?

To control the altitude selection in the 737max in MSFS2024 you need to use the input event FCC_ALTITUDE_SEL, which takes the altitude as a parameter.
To use this, add this input event to a spare/free FSUIPC offset and assign to one of the offset increment/decrement controls.

[Paolo De Sanctis]

I configured Fsuipc and all the encoders work except the one related to the ALT selection and the Efis ones related to the Map type and Range. The strange thing is that the other encoders worked immediately without me having set anything with fsuipc.

[John Dowson]

As I said, please check what it is assigned to. For ALT select in the 737max, you need to use the input event  FCC_ALTITUDE_SEL. Have you tried assigning to this, as advised?

3 minutes ago, Paolo De Sanctis said:

The strange thing is that the other encoders worked immediately without me having set anything with fsuipc.

Well, I think the strange thing is that the other encoders actually work! The default assignments will be to the standard FS controls - these do not work for many aircraft functions in MSFS2020, and even less in MSFS2024. The encoders that are working must be because the aircraft is using the standard controls for those functions, but not for the Altitude select, where it is using that input event.

[John Dowson]

I assigned a spare rotary for this... First, add the input event to an FSUIPC offset - e.g. add to your FSUIPC7.ini file (were xxx is your profile name): 

Quote

[InputEventOffsets.xxx]
1=FCC_ALTITUDE_SEL=UW0xA030

That will add the input event FCC_ALTITUDE_SEL to offset 0xA030 as an unsigned word (2 bytes) - and for your 737Max profile only.

Then assign your rotary buttons to inc/dec that offset. I have both fast and slow buttons on my rotary, so these are my assignments:

Quote

[Buttons.xxx]
...
17=P175,10,Cx1200A030,xC3500064     -{offset uword increment, offset A030 (Incr=100, Limit=50000)}-
18=U175,10,Cx1200A030,xC3500064     -{offset uword increment, offset A030 (Incr=100, Limit=50000)}-
19=P175,11,Cx1200A030,xC35003E8     -{offset uword increment, offset A030 (Incr=1000, Limit=50000)}-
20=U175,11,Cx1200A030,xC35003E8     -{offset uword increment, offset A030 (Incr=1000, Limit=50000)}-
21=P175,9,Cx2200A030,x00000064     -{offset uword decrement, offset A030 (Decr=100, Limit=0)}-
22=U175,9,Cx2200A030,x00000064     -{offset uword decrement, offset A030 (Decr=100, Limit=0)}-
23=P175,8,Cx2200A030,x000003E8     -{offset uword decrement, offset A030 (Decr=1000, Limit=0)}-
24=U175,8,Cx2200A030,x000003E8     -{offset uword decrement, offset A030 (Decr=1000, Limit=0)}-

where 175 is my controller/device number, 10 is the slow inc button and 11 the fast, and 9 the slow dec button and 8 the fast.
If you only have one button in each direction, just assign to the slow controls (or you can use a lua script to convert to 2 virtual buttons...).
Here's how one of those assignments looks in the UI (slow increment)I:

Seems to work ok except for a minor wrapping issue when going below 0, but this shouldn't matter...

John

[Paolo De Sanctis]

Hi Giovanni, I tried as you indicated now it reads the endoder but when I try to set the Alt it seems crazy, it goes up and down quickly. I don't know if it depends on the fact that I set the order of the buttons incorrectly.

[John Dowson]

1 minute ago, Paolo De Sanctis said:

I tried as you indicated now it reads the endoder but when I try to set the Alt it seems crazy, it goes up and down quickly. I don't know if it depends on the fact that I set the order of the buttons incorrectly.

Can you show me / attach your FSUIPC7.ini file and an FSUIPC7.log file showing your issue - activate logging for Input Events, Events and Buttons & Switches, and add offset logging for offset 0xA030 (or whatever offset you are using) as U16.
What button numbers to you see when you move the rotary clcokwise and anti-clockwise, and do you have 1 or 2 buttons in each direction?

Also check that you haven't selected/checked Control to repeat while held.

I did notice this in the VRInsight appendix of the Advanced User manual:

Quote

At present the radio buttons and knobs are not programmable in FSUIPC. They seem to operate quite well enough as they are. They will be overridable in Lua plug-ins, for those among you who wish to get into more advanced manipulation of the devices, but they aren't suitable for general re-allocation.

So maybe its not possible to override the default assignment for that rotary (except via lua), but if you have assigned to this and its sending the events then it should be ok. Your log file should tell me if its working or not.

[Paolo De Sanctis]

I think I checked Ctrl, sorry I didn't notice that. I'll try again by unchecking it. Thanks

[Paolo De Sanctis]

ok now it works fine. I didn't uncheck Ctrl. I also set my VRI cdu2 only for inputs. The thing I can still figure out is why sometimes SerialFP2 finds it and sometimes not. Maybe I'm doing the wrong sequence (first I enter MSFs2024 Via FSUIPC, then I select the plane and start the flight then activate SerialFP2 for each device).

[John Dowson]

12 hours ago, Paolo De Sanctis said:

ok now it works fine. I didn't uncheck Ctrl. I also set my VRI cdu2 only for inputs.

Ok, glad its working but I don't understand from that what your issue was. By Ctrl do you mean repeats? If so, having that checked or not really depends on how your rotary buttons work, but you would usually not use repeats in rotary buttons.

12 hours ago, Paolo De Sanctis said:

The thing I can still figure out is why sometimes SerialFP2 finds it and sometimes not. Maybe I'm doing the wrong sequence (first I enter MSFs2024 Via FSUIPC, then I select the plane and start the flight then activate SerialFP2 for each device).

Sorry but I cannot help with this - I don't have any VRInsight devices and know nothing about SerialFP2.

John

[Paolo De Sanctis]

Thank you so much for your help, you have been very helpful.