John Dowson

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.

If presets stop working, it is usually due to the WASM crashing. This is a known issue, and is caused by continua scanning for lvars. See this FAQ entry for details: With 7.5.0 and 7.5.1, this should be the default, i.e. LvarScanFrequency should be 0 by default in these versions. If it isn't, you have an FSUIPC_WASM.ini file in your WASM persistence storage area - remove that file or update there. If that is not your issue, I will need to investigate further. But this will be next year now as I am now on holiday until January, sorry. This is available in several other topics if you search, but I do not usally provide older versions. If you need to select a profile, this means that the aircraft you loaded was NOT already associated to a profile. This is almost certainly due to you not using substrings for your aircraft profile names. Are you aware of this, i.e. once you add an aircraft to a profie, you should then edit the name of that aircraft in the profile to use a substring that matches all variants. If you don't do this, using the same aircraft but with a different livery will NOT match the profile. Alternatively, you can use the aircraft folder to determine profiles, using the UseAirLocForProfiles parameter. Please see the provided documentation on using profiles, profile substrings and using that parameter. Otherwise, I will need to see your files showing your issue. You should ALWAYS attach files if you have an issue - your ini and log files tell me a lot for such issues. And pleas give a topic an appropriate title....

Presume you mean 7.4.17... And here I presume you mean 7.5.1... When did you add this - did you do it when FSUIPC7 was not running? If not, try again... This is the only change that can cause this issue, and adding that should fix it. This has been confirmed by several users. If that is not your issue, then I will need to investigate further. But I will not look into this until the New Year now. But please try again with this set to confirm.

👍

Looking at your log, when a Flaps Inc command is being sent, a Flaps Down control is also being seen: and similarly, when a Flaps Dec command is being sent, a Flaps Up control is also being seen: These additional up/down controls are NOT coming from FSUIPC, so they must be either coming from MSFS itself or somewhere else. Please check your MSFS assignments, and make sure you check both the General and Aircraft specific assignments. Also check the assistance options. I have checked a few aircraft here and do not see this, so it must be something in your MSFS settings. John

I have checked this here now and it looks like in both cases (i.e. when using FS Controls and when using presets) what is happening is that both controls are being sent, but the FS is only responding to the first control. I am not sure why this is happening, but really you shouldn't be sending the slow/small inc/.dec control when sending the fast one. To prevent this, add another preset condition in the slow control to be only sent when the trigger button is off, i.e. change: to John

Cam you please attach your FSUIPC7.ini and FSUIPC7.log file, the latter with logging for Events and Buttons & Keys activated and showing your issue, i.e. load an aircraft, activate the flaps Increment and then exit. Also check that the button is not assigned in MSFS2024..

Better to disable controllers in P3D completely, otherwise it has a habit of silently re-assigning them. So please first try with controllers disabled. If you still get the same issue, please activate logging for Axes Controls and show me / attach both your FSUIPC6.ini and FSUIPC6.log files and I will take a look. Note that I have now finished for the holiday season, but I will take a look at your files over the weekend when I find some spare time. Regards, John

I have finished now for the day (and year really!), but will take a look over the weekend when I have some spare time...

Please attach files rather than posting extracts... It is strange that I cannot see a button 2 press event logged, but the condition does change from false to true, and the control is being activated. The fast controls use offset 0x07D4 and set the AUTOPILOT ALTITUDE LOCK VAR simvar. If this is not working, then the aircraft doesn't use that simvar (or uses it in conjunction with something else) . Try assigning to the AS1000 presets instead, i.e. AS1000_AP_ALT_INC_100 AS1000_AP_ALT_INC_1000 AS1000_AP_ALT_DEC_100 AS1000_AP_ALT_DEC_1000