John Dowson

You files still show you are using an old unsupported version of FSUIPC7. please download and install the latest and only supported version. Your log file also shows that FSUIPC7 connected to MSFS. Sowhat exactly is your issue? If FSUIPC7 is not auto-starting, please see John

No problem - permission granted (well, not even needed really!). You could also add it to the User Contribution section if you like, and/or I could include it in the FSUIPC SDK download. Let me know. Regards, John

Please use the FSUIPC7 support sub-forum for all issues/questions on FSUIPC7 with MSFS2020 and MSFS2024. I have moved your post. Why are you attaching an installation log from win10 if your issue is with win11? That log file also shows you installed version 7.3.6. That is quite out of date - the latest version is 7.5.3. Please download and install that if you have not already. Only the latest vertsion is supported. What exactly is your issue? The title says that FSUIPC is not connecting - if that is the case, then FSUIPC will do nothing. I do not know what a MiniPanel or a MSFSPopup panel is, or what they have to do with FSUIPC. First, install the latest version of FSUIPC7. Run MSFS and let FSUIPC7 auto-start, and wait for MSFS to arrive at the main menu. Does FSUIPC7 connect? If not, you probably need to manually tune the auto-start parameters - this is described in the Advanced User guide, and also in the following FAQ entry: You can also try exiting FSUIPC7 and then starting it manually - does it then connect? Do you have assignments in FSUIPC? If so, your device GUIDs may have changed with the upgrade from windows 10 to 11, and your assignments may no longer be valid. If this is the case, please attach your FSUIPC7.log and FSUIPC7.ini files and I will take a look. John.

Ok, but this may take a while...I have other series issues I need to look into, besides rebuilding my PC, before I can look into any further changes to FSUIPC7. John

No, but I could add such a function. So there is no real issue - just ignore the message! Sounds like overkill - a lot of work for no real benefit.

@Reco I see you posted over on Avsim for the dodsim *.evt used in the P3D version. Does this also work in the FSX version? If so, maybe you could attach it here for other dodsim users who come across this post. Cheers, John

Does the lua continue or exit with that error? No. Input Events, like lvars, are aircraft specific. However, input event names may be shared between aircraft (although they will be different Input Events, and maybe with different values. That is what you have to do... If you want to use the same script with multiple aircraft, different Input Events, then just check the aircraft name (offset 0x3D00) and then use/set the name of the appropriate Input Event to use. You can always have a default Input Event to use if the aircraft is not known by the lua script, but if that doesn't work then you would have to edit the lua to add another condition to set the Input Event name for the new aircraft. Note I have had a severe crash on my development PC (after a Windows Insider Upgrade) and I currently have no access to the FSUIPC source or development environment. Therefore support will be limited for the next week or two while I rebuild my systems. John

These errors are due to the fact that MSFS has crashed and is no longer available. As I keep telling you, there is nothing wrong with FSUIPC7. This needs to be fixed by Asobo.

You could maybe try removing the FSUIPC WASM from your community folder. You won't have access to lvars or presets, but that would test if its the WASM thats the issue, not FSUIPC7 itself. There was a report/comment on that link I posted that said this fixed the issue.

There is nothing wrong with FSUIPC and there is no fix, unless SimConnect is no longer backwards-compatible (which I very much doubt!). This needs to be fixed by Asobo. This has happened on previously beta releases and is usually fixed in a subsequent beta update. As I said, there is no way I can fix or investigate a sim CTD, only report this to Asobo.

...and are you sure this is related to FSUIPC7? i.e. does it run normally without FSUIPC7 running? There are lots of reports of CTDs in this beta version - see https://forums.flightsimulator.com/t/ctd-loading-into-1-5-10-0/727551 And I cannot investigate MSFS crashes - you need to report to Asobo. Even if the SimConnect API has changed, it should be backwards-compatible, so I am confident, even if this issue is provoked by FSUIPC7, it is an issue for Asobo and must be fixed by them. John

As this is in the beta, you should wait for a fix in the beta. FSUIPC7 is an external app and in no way should it crash the FS. Maybe check the Asobo beta forums to see if anything has been reported there regarding simconnect apps. I have had a severe crash on my development PC during a windows update and cannot look into anything at the moment until I have repaired this. John

As long as windows recognises the card as an HID joystick type device, and revognises the buttons, then FSUIPC will see them. I have no direct experience with such cards, but many people use them with FSUIPC so I don't think it will be an issue. John

Its in the Using Lvars section - see page 48, under Logging Lvar Updates. John

For controls, you should start with the standard controls, not offsets. For example, the standard control for AP altitude hold would be the AP Alt Hold control (65726). Note that the standard way to determine what control to use is for any button or switch to set logging for Events (Log->Events), open the logging console (Log->Open Console) and then toggle/set the switch in the virtual cockpit and see what is logged. If anything is logged, use that. Note that many MSFS aircraft continually emit certain events, and these are different for each aircraft. These can make using the log difficult, so best to ignore these by setting the DontLogThese ini parameter (see the Advanced User guide for details). Many MSFS aircraft, especially third party/add-ons, do not use the standard controls/events. For such aircraft, check to see if an MF preset is available - you can use the search interface on the MF HubHop site: https://hubhop.mobiflight.com/presets/. All MF presets should be available for use in FSUIPC7. Some aircraft also use their own custom controls (e.g. PMDG, FSLabs, etc). For such aircraft, check the documentation - and there is a FAQ entry on using custom controls with PMDG aircraft. If there are no standard events, presets or custom controls that work, you can look at the available lvars or preset events, or examine the switch/button behavior to see what it is using - see the following article: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/ If you require any further help, please let me know the aircraft you are using. John

Listing lvars shows the currently held value by FSUIPC, which is a max of 166ms or so out of date (using the default update rate of 6Hz). There is already a facility to log lvar updates, either to the log or a separate ext window. This is done via an ini file section (at the moment) - see the Advanced User guide. John

There may be an lvar that you could use - try listing them to see if any look applicable. John

Just received further information: if you press tab to check and nothing happens, this means the mouse macro facility can't be used. The whole thing about mouse macros is that it’s all a code hack, especially in FSX, and some parts of the FS code just aren’t constructed in the manner where they do work. The test offered at the creation phase is to check that, and if it doesn’t work other methods have to be used to action the function desired as mouse macros won't work. A lot of later add-ons did not use the original library-provided methods for implementing their controls. And that is where the problems are, and there is nothing that can be done in FSUIPC to get around this John

No point attaching images - they don't tell me anything that you have not already told me. Did you try my recommendations? Maybe also leave the Module line in as it looks like this is needed (although I have never seen this before!). I have never seen parameters 23 and 24 used before - I though these should be in the 1-17 range, as the documentation states. But if it doesn't work, there is not much I can do about this. FSUIPC4 has been closed for further development for many years. And I don't have much experience with FSX and certainly don't have the dodosims 206, which also doesn't seem to be available anywhere either. My PC has also now died after the latest windows (insider) update, so cannot do anything at the moment or until I have sorted this out... Sorry I can't be of more assistance. John

The log you attached shows that FSUIPC7 did not connect, and was still running when you attached the log file. Please ALWAYS exit FSUIPC before attaching files. And please leave FSUIPC7 running at least until MSFS arrives at the main menu. Your issue is almost certainly due to the auto-start parameters not being tuned correctly. I cannot advise what to use with that log file you attached for the reasons already stated. Try tuning the auto-start parameters yourself (see the documentation or that FAQ entry I referenced) or provide me with a better log file and I can advise what to try. Also check your EXE.xml (location is logged in the InstallFSUIPC7.log file if you don't know where that is. If there are multiple entries for other apps, then you can also try making sure FSUIPC7 is started first. You can also attach this and I can take a look. John

The logging I requested would just confirm that the auto-brake threshold wasn't being used, but I think that was added in a later version of FSUIPC 7 than the one you are using anyway. You should update to the latest version of FSUIPC7. John

Did you not read my previous comment: You are not using an airbus, so this parameter has no effect. If you want to mimic this in airliners, then you would need to use a lua script. Note that you are using a very old version of FSUIPC - 7.4.17. I only support the latest release, which is 7.5.3. Please update if you require further support: You need to set the logging flags then exit FSUIPC and let MSFS auto-start it, as then I can see/check the logging. John

Looks like you are using the PM 737. The brake release threshold is only applicable to airbuses, as these are the only aircraft that use this brake release mechanism (although I see in the documentation that this is omitted!). Try setting the logging for Extras before the aircraft is loaded - this should then log a message indicating if the brake release threshold is applied or reset. John

Ok, that makes more sense then, and it will be because FSUIPC is not connecting to the FS. The log file should reveal why. John

What has changed? Can you show me / attach your FSUIPC5.log file showing this issue. If there are any log files from Pegasus, please also attach them. John