MSFS 2024, PMDG 738, FSUIPC 7.5.6b, Linda, Vri MCP combo II Boeing

What is driving the display values? Are you using the PMDG-specific offsets, and if so have you activated the broadcast of these values in the 737_Options.ini file?

Also, if using PMDG aircraft in MSFS2024, please update to the latest beta (7.5.6b), available from the News section, which has some improvements in starting/stopping the PMDG-specific threads in MSFS2024.

If you are still having issues after checking that, can you please show me / attach both your FSUIPC7.ini and FSUIPC7.log files, and provide more information on how those displays are driven.

Greetings. I don't use any specific offsets. I also fly with Black Square - Piston Duke and everything works there.
I attach FSUIPC7.ini and FSUIPC7.log

Thank you

So it is LINDA that is driving the MCP displays, via a lua script.
Unfortunately you need LINDA support. LINDA is no longer supported by the developer, but you could try positing on the LINDA support forum (on AVSIM) to see if any other LINDA users can help.

Otherwise, there are a few other things you can try.

First, please check / confirm that you have activated the PMDG SDK broadcasts for the 737-800. You almost certainly need this.

Then if the issue persists, the first thing to try would be to check if this is an MSFS version compatibility issue. You can check to see if this works in MSFS2024 when LINDA thinks you are running MSFS2020. To do this, you need to:

    1. Add the following ini parameter to the [General] section of your FSUIPC7.ini file:

           init3308=13

    2. Create a file called ipcInit.lua in your FSUIPC7 installation folder and add the following:

ipc.writeUW(0x3308, 13)
ipc.writeUB(0x3124, 110)
ipc.log("ipcInit: FS version offsets updated to MSFS2020")

That should then fool LINDA into thinking you are using MSFS2020. However, this may also have further unwanted consequences. But please try this first, and show me your log and ini files for this. 

If that doesn't work, then the next steps would be:

   1. Determining where LINDA is getting the values for the displays from (probably via offset logging)

   2. Determining where the correct values for the displays are held (again, via offset logging)

   3. Spoofing / re-directing the reading of the values using a lua script 

John

Also, your log file does show several re-connections to the FS. Do you know what caused these?

And you have a com port failure that might be an issue:

94 VRI port 1 "com0" failed to open
109 *** Preset name 'Cirrus_SF50_Vision_Jet__MSFS2024_-_Toggle_VNV_Button_in_Autopilot_On_and_OFF' exceeds max allowed length of 63 characters - ignoring
141 VRI port 2 "com3" opened

Not sure what is causing that. Are you sure that your VRI COM ports are configured correctly? Are you using the same configuration as with MSFS2020? The VRInsight com port configuration does not look correct to me. Are you not using SerialFP2? But maybe this is handled by LINDA - I don't know as I have never used LINDA or VRInsight devices. But please see the appendix in the Advanced User guide on how to set-up VRInsight devices in FSUIPC.

The other strange thing in you log file is with the WAPI / WASM connection. The WAPI is started, but no lvars are received. This could be due to a WASM crash, but this does mean that there will be no access to lvars (or presets, etc), which could also be an issue.