John Dowson

There are lots if reports of CTDs with MSFS2024 - these are nothing to do with FSUIPC7. When you tun the installer, it should detect the previous installation and remove this, including the documents. If they are not removed, then this is usually because they are open somewhere. Did the previous version not het uninstalled correctly? Any problems with installation, you can show me / attach the UninstallFSUIPC7.log file (which is the log of the previous version uninstalled) and also the InstallFSUIPC7.log. But just try again first (i.e. re-run the installer), and make sure that no documents are open when you do this.

But you don't need to do this. Once you have validated your key, and FSUIPC7.key file is created whuch contains your key details, and when you update/re-install, you should just skip the license validation page. But your key details should be pre-populated (from your FSUIPC7.key file) and you should be able to re-validate them without a problem. If your key previously validated but no longer does, then either you entered them incorrectly or maybe anti-virus software is interfering. If they previously validated, then your VC++ redistributables must be ok. But please see the Installation and Registration guide for all registration issues,

There is no problem with the latest version of FSUIPC. There is probably an issue with the software you are using that is reading offset 0x3308 which holds the FS version number. This held 13 at start-up in all versions of FSUIPC7 prior to 7.5. However, as 7.5 is compatible with both MSFS2020 and MSFS2020, the version number is no longer written to this offset until FSUIPC has connected to the FS, as it needs to determine the version first. This has caused some issues with some 3rd party software. To help with this, I released 7.5.1 which contains a couple of additions to help with this. If you add: Init3308=13 to the [General] section of your FSUIPC7.ini file, then FSUIPC will again pre-populate that offset with the value 13, which is for MSFS2020.

That may be ok or could be too high. You should either tune that parameter or let FSUIPC tune this for you. See the section Auto-tuning of initial start-up ini parameters in the Advanced User guide, Also, from the User Manual on page 7:

The "reading result from another lvar", is that referring to Q400_YD_LIGHT ? No - I was referring to L:MJC_VAR_READ_VALUE - the readXMLIF function writes the result to that lvar, which is then used to set the actual lvar value (Q400_YD_LIGHT, Q400_AP_LIGHT, etc) . That should be fine, but better to drop the userParameter value (as its not being used (to avoid confusion) or just pass in 0: function yd_on (var, value, userParameter) ipc.writeUB ("66C0", value) end event.Lvar ("L:Q400_YD_LIGHT", 100, "yd_on", 0) Yes, Luas that wait for events always need to be started, and usually via the [Auto] or profile-specific [Auto.xxx] section.

No it didn't... The END OF PROGRAM line means that the WASM exited normally as MSFS exited. The errors occur as the WASM is trying to clear things up nicely before exiting but the simconnect connection is dead. Those are nothing to worry about. So the WASM isn't crashing - why do you think it is?

Ok, but you should at least show me your files...these are what I need to at least have some understanding of your issue - I cannot really help at all without seeing those... And a Merry Christmas and Happy New Year to you as well! Cheers, John

Have you assigned in ProSim or in FSUIPC? If its not responding, activate logging for Buttons & Keys as well as Events, and show me / attach your FSUIPC6.log and FSUIPC6.ini files, the latter showing your issue. I can take a look to see if I can see anything strange, but this depends how/where you have assigned. Note that support will be slow over the Christmas/New Year period, as I am also now on holiday and need a break.... John

Btw, why did this issue start only "lately"? Do you know what changed to provoke this issue?

There was no change at all in the WASM between 7.5.0 and 7.5.1, so if its now crashing more frequently then this is most likely due to a sim update. Did you check your WASM ini settings? If you have followed the advice in that post and are still seeing a WASM crash, please show me / attach your FSUIPC_WASM.log file.

There is no state to the push buttons, they just trigger custom controls: #define EVT_EFIS_CPT_WXR (THIRD_PARTY_EVENT_ID_MIN + 369) #define EVT_EFIS_CPT_STA (THIRD_PARTY_EVENT_ID_MIN + 370) #define EVT_EFIS_CPT_WPT (THIRD_PARTY_EVENT_ID_MIN + 371) #define EVT_EFIS_CPT_ARPT (THIRD_PARTY_EVENT_ID_MIN + 372) #define EVT_EFIS_CPT_DATA (THIRD_PARTY_EVENT_ID_MIN + 373) #define EVT_EFIS_CPT_POS (THIRD_PARTY_EVENT_ID_MIN + 374) #define EVT_EFIS_CPT_TERR (THIRD_PARTY_EVENT_ID_MIN + 375) #define EVT_EFIS_CPT_LAST EVT_EFIS_CPT_TERR ... #define EVT_EFIS_FO_WXR (THIRD_PARTY_EVENT_ID_MIN + 425) #define EVT_EFIS_FO_STA (THIRD_PARTY_EVENT_ID_MIN + 426) #define EVT_EFIS_FO_WPT (THIRD_PARTY_EVENT_ID_MIN + 427) #define EVT_EFIS_FO_ARPT (THIRD_PARTY_EVENT_ID_MIN + 428) #define EVT_EFIS_FO_DATA (THIRD_PARTY_EVENT_ID_MIN + 429) #define EVT_EFIS_FO_POS (THIRD_PARTY_EVENT_ID_MIN + 430) #define EVT_EFIS_FO_TERR (THIRD_PARTY_EVENT_ID_MIN + 431) #define EVT_EFIS_FO_LAST EVT_EFIS_FO_TERR See the FAQ section on how to use PMDG custom controls: John

Its a lua script so it takes the .lua extension, and should go in the FSUIPC installation folder (i.e. where the FSUIPC6.exe is located) unless you have the LuaPath ini parameter set, in which case use that folder. Well, readXMLIF ( 31461 ) will just call that function and return a value, which is the value of the lvar MJC_VAR_READ_VALUE after writing 31461 to the lvar MJC_VAR_READ_CODE. So it looks like the majestic interface works by writing a code to one lvar, waiting for this to be processed and then reading the result from another lvar. What global variable? Can't Mobiflight read lvars directly? If you want to make any variable/value available in an offset, just write it to spare/free offset with one of the ipc.writeXX lua functions. John

No problem. I can help with any issues or questions with FSUIPC, but for issues with specific aircraft, especially complex add-ons like ProSim, probably better to contact the support for the aircraft, I was under the impression that all the newer versions of ProSim handle the assignments themselves and don't use FSUIPC for much (although I may be mistaken). If you can't resolve your issue via ProSim, let me know and I can ask Pete (the original author of FSUIPC) as he is a ProSim user and may be able to help, although he is retired now. I don't fly airliners so can't really comment on such issues if not related to FSUIPC. Regards, John

You posted in the dll client for ,Net subforum for some reason...I have moved your post to the FSUIPC7 support. Why? If anything, you should include/attach your FSUIPC7.log file. But your issue is nothing to do with FSUIPC7, and is probably due to the MSFS patch that was released on the 20th/21st. Check the Asobo forums. I have seen posts there reporting blank panels so maybe its the same issue... Try running without FSUIPC7 - I am sure you will get the same issue....FSUIPC does nothing with visuals at all. John

Sorry, I don't use ProSim, and can only support FSUIPC. I suggest you try ProSim support or maybe AVSim. Maybe other ProSim users can help, but if you want to attract anyone's attention you really need to give your posts a better title - you don't even mention ProSim there....I will update it...

Yes, 1-byte for each EFIS mode selector switch. There are two EFIS panels, no? So there is one byte per panel. No, they are the byte values, so each byte will hold one of those values representing the position of the switch in that panel.

Yes, the WASM crash seems to be occurring a lot more often in MSFS2024. I will look into this further in the new year and provide more information to Asobo so that they can look into it. For the time being, please turn off lvar scanning - see Those settings should be the default in 7.5.0 & 7.5.1 due to this issue, but can be overridden with your own settings if you have a WASM ini file in your WASM persistence storage area. John

Yes - please see the ButtonRepeat ini parameter - from the Advanced User guide: John

Please use the FSUIPC7 support forum for all issues/questions on FSUIPC7. Please see the README.txt and the Installation and Registration guide. To run the installer, make sure that: - you extract the installer from the zip file before running it, i.e. do NOT run the installer from within the zip file - you have the latest VC++ redistributables installed - see the README.txt for further details

I am sorry but there is nothing wrong with the installer - this is a specific issue to your system. I have no idea why you are getting this error. If you are extracting the exe from the zip before running it, and have the correct VC++ redistributables installed, then the installer should work. If not, there is something strange in your system and i do nor know what to advise for this error. Does this occur as soon as you start / double-click the installer exe? I could provide you with separate folders to install manually, but you should try to determine what is causing this issue. Are you using OneDrive or any other cloud service? If so, maybe try disabling that, and check your environment variables are set correctly. When you start the installer, do you first see the User Account control box where you give permissions for the installer to make changes to your device? If not, does your account have admin privileges?

If using FSUIPC for your devices, do NOT install any logitech drivers or software. If you have already installed logitech drivers, please uninstall them and let windows install the default windows drivers instead. But your files and registry are looking a lot better, I have corrected a few things in your ini, so please try the attached: FSUIPC7.ini

Its John - Pete retired over 5 years ago now. Glad its now working, Happy Christmas! Regards, John

If you get errors running the installer, it is usually due to not having the correct VC++ redistributables installed. See either the README.txt or the Installation and Registration document which both contain details on how to update these. John

I have moved your post to the FSUIPC7 support forum. There is nothing wrong with the installer. Try downloading the latest version (7.5.1) from fsuipc.com and try again. You should not do this, and also you should not install FSUIPC7 in such folders. Just unzip and run the installer from your Downloads folder. John

The only duplicate seems to be the X-56 Rhino Stick..do you noy have two of these? If not, then windows is reporting this device with two separate GUIDS: However, it is these entries that look suspicious: as the game controller (Afterglow Gamepad for Xbox 360) and MFG Crosswinds are reporting the same GUID. Are you using the fame controller in FSUIPC? If not, maybe a food idea to ignore this device... If using the JoyLetters facility (which is active by default), then all devices (device ids) will be mapped to a letter. If you want more details, see the provided documentation - the JoyLetters are explained in the User manual. I don't understand that ini extract you pasted as it doesn't correspond to the files you attached - there are no MFG Crosswind V2 there, probably due to the duplicate GUIDs. And your log file shows that they were acquired twice. Your log file shows that it was attached when FSUIPC was still running. Please ALWAYS exit FSUIPC before attaching any files. Your registry also shows some issues with some duplicated ids which can be corrected. Can you. please re-attach those two files, but after exiting FSUIPC, and also attach your complete FSUIPC7.ini file. Let me know which devices are working and not working and we can go from there.