John Dowson

Your logs show a few issues, but FSUIPC4 is running and was still running when you attached the log...I think....was FSX still running? The issues are: 1. You are running FSX version 10.0.61637.0, but the simconnect library being used is 10.0.61259.0: To correct this, install the simconnect.dll for your version by running (i.e. double-click in windows Explorer) the following file under your FSX main folder: F:\Microsoft Flight Simulator X\SDK\Core Utilities Kit\SimConnect SDK\lib\SimConnect.msi 2. You are running an unregistered version, even though you are using a key file containing your registration details: I am not sure why this is - can you let me know your FSUIPC4 order number and I will check your details here. DO NOT post your key file or key details! Neither of these issues should prevent the FSUIPC main window from being displayed, although the interface will only contain a few tabs as it is running unregistered. I don't understand why the window isn't being displayed... Lets correct these issues first and see if that solves things... John

Details will be in the FSUIPC7.JoyScan.csv file. If you attach that I can provide aa script to remove the entries, and you can see if they are registered correctly when re-attached.

Please attach your FSUIPC4.log file....

Maybe also check-out these posts on view control:

Have you defined and saved the quickviews? If not, do that first. Otherwise, if you have issues with MobiFlight presets, you should report/ask about this on the MobiFlight discord server (MSFS2020 channel). However, I can take a look here, but will be later today or tomorrow - I will get back to you on this once tested here. Pan Heading has not worked since the release of MSFS2020. From the FSUIPC7 README.txt: John

Do you mean that the FSUIPC main window is not displayed when you select it from the Add-on menu? Are you running FSX in full screen mode? If so, can you switch to non-full screen and see if the FSUIPC main window is hidden behind the FSX window. Also, please check the task bar - can you see FSUIPC there? Your installation log looks fine. Can you show me your FSUIPC4.log and FSUIPC4.ini files please.

Hi Ray, as well as the total load weight/mass offsets mentioned by Luke, there are the total quantity fuel offsets: 1264 4 Fuel: total quantity in gallons (32-bit integer) Ok-SimC No 1268 4 Fuel: selected quantity in gallons (32-bit integer) Ok-SimC No 126C 4 Fuel: total quantity weight in pounds (32-bit integer) Ok-SimC No 1270 4 Estimated fuel flow at cruise, in pounds per hour (32-bit integer) Ok-SimC No ...and best wishes for the New Year to you both. John

The problem seems to be with the name of your controllers in the windows registry - sometimes it reports a device name and sometimes it is empty. You need to correct for this (when it changes) in the [JoyNames] section of your FSUIPC7.ini file.

How did it help? You seem to be having the same issue.... It seems the name of your devices is now missing from the registry. I have edited your ini again to use a blank name - see if this works. If not, you will need to clean your registry. Please don't add any new assignments until this issue is resolved. I have removed the ones you added to the yoke when it was assigned the joyletter C, as these are duplicates of assignments made when it had the letter B. FSUIPC7.ini

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