John Dowson

Sorry, yes - FSUIPC6 is P3D, not MSFS. I really cannot tell anything from that log file extract you attached. Try flying with the console window open and note the events that occur when you get your issue, and then try and determine where those events are coming from. I don't see how deleting your ini file can solve this, especially iff this is not caused by FSUIPC. You need to determine what is causing this issue. I do not have or know anything about the IFly 737Max, so cannot help you with this, sorry. John

First, you posted in the wrong sub-forum for support, which is why your post was not answered soooner. I have moved your post to the correct sub-forum. Please take care to post in the correct place if you require support. If using GoFlight devices with FSUIPC, you need to install the 64-bit GoFlight driver/dll, available from http://fsuipc.com/.

What do you mean by this? Can you see the FSUIPC menu item in the Add-ons menu? What happens when that is selected? Are you using the steam version? Where is FSX installed? If under a windows-protected folder (e.g. under Program Files), then you may need to run FSX as admin. Please show me/attach your FSUIPC4 Install.log file, which is located in the modules folder under your FSX installation folder.

You would have to implement your own event-driven wrapper on top of the provided SDK. Basically you would need to request the data/offsets that you are monitoring in one thread, and when the value changed you can signal this as events to other threads. I don't remember much about node-js, so cannot really help you with this. More advanced wrappers, such as Paul Henty's dll for C#, may provide an event-driven interface. And there is also the websocket server.

Asobo/MSFS recently changed the facilities API and switched from using an ICAO to using an Ident, which allows for up to 6 characters for an airport identifier. I have no idea why they did this....! I presume the Ident is the same as the ICAO for most airports.

Sorry but Pete has retired and I no longer support MakeRunways. I'll mention this to Pete and he may take a look,

Can you try the attached please: FSUIPC7.exe That version should hopefully fix this issue. There was a problem with the flags that indicated lua/preset/input event as the same bits are used when the lua file index number is 32 or higher. This should now be corrected. John

There is still an issue - it saves ok but when you restart the parameters are reset to zero. I am looking into it.... John

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. I have moved your post to the main support forum. You also posted twice - I have deleted your second post. Please note that I was on holiday over the christmas period: Check your P3D options: General -> Other Controls, and make sure Enable Advanced Mouse controls is checked. The mouse-look function doesn't work correctly without this checked in P3Dv5. John

Could you try the attached version please: FSUIPC7.exe

I've just tried here and cannot reproduce this. Could you show me your FSUIPC7.ini files please and let me know which assignments are having this issue.

I will look into this ang get back to you. John

Looks like a registry problem where your device name/guid changed... I have corrected this in the attached file, if you could try with this. There looks to be an issue with your CH Pro pedals as well, but you don't seem to have any assignments to this. Is this working? You may need to clean the registry details for this if you want to assign in FSUIPC. John FSUIPC7.ini

Please DO NOT attach your key file or publish your key details in a public forum. This invalidates your license. I have removed this file and luckily nobody had downloaded it. Can you please explain more clearly what your issue actually is and what this has to do with FSUIPC. FSUIPC will not do anything on its own accord - check your autopilot setup, and also the MSSFS assistance options - maybe coming from there?

You can use the external quickview presets: For other external quickview controls, you would need to either define your own preset, or assign a key combination to the control in MSFS and then assign to this key combination in FSUIPC. John

You should omit the 'B:', and use the input event name EXACTLY as listed by FSUIPC7. Yes, you need to use the input event names as listed by FSUIPC, not in the behaviors window. Not all input events are currently exposed via simconnect API, but Asobo have indicated that more will be available in future releases. Use the Log->List Input Events menu to determine what input events are available, and use the names exactly as specified there. John

FSUIPC numbers buttons from 0, whereas windows (and maybe ProSim) start from 1, so windows buttons 4 & 5 will be buttons 3 & 4. Please see the User guide. The interface in FSUIPC7 is slightly different to that of previous versions. The 'Options and Setting' page of previous versions was the main window of FSUIPC, with all the features available under different tabs. Now, each of these tabs is available from a menu item. Please see the documentation. How was this previously set-up? Have you tried configuring the same way? Sorry, i don't have the ProSim flight model and cannot help with specific assignments for this aircraft. Ty the prosim documentation or the prosim forums. John

You only need to register once - this generates the key file. When you re-install, you can skip registration and FSUIPC will still run as a registered copy. John

Can you please explain what you mean. Key assignments are for a key press, possibly with modifiers, but not for "sequences". You can assign to "Ctrl+L", to "O" and to "Alt+J'. Or do you want to send a sequence of key presses? If so, what is triggering them to be sent?

There is no location tagging in FSUIPC - something else must be going on.... Registration issues are nearly all due to either not having the correct VC++ redistributables installed, or by anti-virus software. You need to install the combined redistributable package, as specified in the documentation, which includes 2015, 2017, 2019 and 2022.

FSUIPC7 has nothing to do with the start-up of MSFS. If you use the desktop icon installed by FSUIPC7, this just displays a splash screen while MSFS is starting, and MSFS will start FSUIPC7 at the appropriate time. The start-up time of MSFS will depend on the number and complexity of the add-ons installed in your Community folder. John

No - only the automatic execution of lua and macro files is supported, as these run in separate threads as part of FSUIPC. For other programs, you can use the [Programs] section to start - see the section Programs: facilities to load and run additional programs on page 43 of the Advanced User guide. John

Sorry, it seems that the license expired earlier than expected.... I have generated and attached a new one (to the existing trial license topic), valid until 1st Feb, so please download and try again. John

The trial license/key file is available to download in the very first comment of this topic. John

Those errors are reported as something is trying to set those variables before the initial request to receive and control them has been completed. It looks like it is taking longer for the initial data requests from being completed on initial start-up, and it works when you restart as these initial data requests are processed a lor faster once MSFS2020 is up and running. You need to determine what is trying to access those variables and delay those requests until all of the initial data requests have been processed. Not sure what you mean by this, but you can delay any initial requests until the offsets have been initially populated, such as checking for when the FS version offset 0x3124 is non-zero. John P.S. Note that I am on holiday until the 2nd or 3rd January.