John Dowson

You should create a new profile, not clear the default profiles. If you create a new profile for each device it will be empty (by default), and if set for your devices/controllers it should load again the next time you restart MSFS. John

Why are you creating a new topic when you have already created a topic for this issue to which I have already replied? Please use the other topic: John

Try temporarily renaming that and let FSX built a new one, and see then if you get a CTD...

I am not holding out much hope... Did you actually do a full re-installation of FSX or just copy exes and dlls from your backup, as you say in the other post? I ask as it does look like this is related to your FSX installation... John

After you have checked/re-installed the VC++ redistributables, if you still get the CTD, can you try with the attached dll please: FSUIPC4.dll John

Btw, did you actually do a full re-install? Reading your other post, it seems that you were copying the EXE and DLL files from your back-up rather than doing a full re-installation.

Ok. forget the above...I just found your previous post with the same problem: You should have continued in that topic rather than starting a new one.... What vc++ redistributables do you have installed? Maybe try uninstalling any of the following if installed: 2015, 2017, 2019 & 2022. Then install the latest combined package from https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170. John

Maybe, if it is a HID type device. You can try the included HidDemo.lua to see if the device is recognised, or try the HidScanner program first to see if that recognises the device and the button/switch changes (available from ) John

I think SP2 and the Acceleration pack are different, but the Acceleration pack includes SP2 (i.e. you don't need to install SP2 if you install the Acceleration pack). What SDKs did you install? You also need to install (in the following order): - FSX SDK 1 - FSX SDK SP1a - then the FSX SDK XPack off of FSX Acceleration. What changed from working fine to the CTDs started? How come you have only just reported if this started a year ago? John

👍🙂

To delete key assignments, use the right-hand side of the key assignments panel, where it says 'Review or delete settings here'. Also check you don't also have the assignment in a profile for the aircraft being used, if using profiles. You could always read the user manual...! John

No. FSUIPC4 has been closed for development for several years... There is nothing in the ini file that would cause a CTD. This is normal. Windows 11 is still windows 10 in the windows registry, the source of this information. Are you sure you have installed SP1 and SP2 when you re-installed FSX? Your version is reported as: fsx.exe version = 10.0.61637.0 However, I see: fsx.exe version = 10.0.62615.0 ? Can you run FSX without FSUIPC? If you haven't tried that, please do - just temporarily rename your FSUIPC4.dll to FSUIPC4.dll.unused (for example) so that it is not loaded. If it runs without FSUIPC, and you are running with SP1 and SP2 (the version numbers may be different if not using steam, I'm not sure...) then we can add more logging to try and get more info... John

I have PM'ed you a full complimentary license. John

Only the first post by a user requires moderator approval. I see no post of yours in that thread. The user in that thread is also using the Aerosoft A320, so it may not work with the ProSim 738. You can try posting again, and you can also notify the user by using the @<username> notation. John

Yes (it is a wrong assumption)... I don't know what your SIOC SC-Pascal software does, but I presume its more like a driver and is specific to your hardware device. LINDA is an interface built on top of lua to make lua assignments easier (well, that is an over-simplification - see the LINDA documentation and web-forums for better description). I presume you will need the SIOC software even if you decide to use LINDA, but I don't really know - these are questions for your hardware provider/manufacturer. I can't really help you with hardware I don't have and know nothing about. Ok. I will post one here for you to try later today... John

If the manufacturer provides a SIOC, then this is what you be using. However, I cannot help you with this - you need support from the manufacturer. The pascal SIOC does not replace lua. You probably don't need a registered version of FSUIPC if using the SIOC, but the SIOC documentation should tell you if you need FSUIPC, and if that needs to be registered or not - I really can't advise. This old post is from a user also using FSUIPC with hispapanels and a PMDG aircraft - reading this it looks like they were using a registered version for assignments: I can provide you with a time-limited trial license for FSUIPC4 if you would like to try the registered facilities. Ok. But there are also cards for using MobiFlight with Hispapanels - see https://hispapanels.com/tienda/en/105-mobiflight John

This post is quite old now... If FSUIPC7 is not starting with MSFS, please follow the instructions provided in the included README.txt: If that doesn't solve your issue, show me your InstallFSUIPC7.log file and also your EXE.xml file (whose location can be found in the InstallFSUIPC7.log file). John

Are you even using WideFS? If so, I doubt very much this has do do with FSX crashing... This is usually due to a corrupt weather file. Try disabling weather by setting NoWeatherAtAll=Yes to the [General] section of your FSUIPC4.INI file. If this solves it then either your wxstationlist.bin file is corrupt, or one of the .wx files saved with scenarios is bad. To resolve this, delete all of the .WX files from your FS Documents folder (where your flights are stored), and the file "wxstationlist.bin" in your <user>\AppData\Roaming folder for FSX. John

FSUIPC6 us an embedded dlll, so if you start P3D as admin, then FSUIPC6 will be loaded with admin privileges. John

@Framac Please try the attached version where the lvar/hvar display window has been re-activated. John FSUIPC7.exe

The post I referenced just shows you how to calculate the control number and parameter to use the custom controls for PMDG aircraft. Once you have determine what control and parameter to use, you can either assign this to the button switch (FSUIPC registered only) or write this to offset 0x3110. FSUIPC only recognises HID joystick type devices for direct assignment, but other non-joystick type devices can be used via lua. Both of these facilities are for the registered version only. I cannot advise if FSUIPC would recognise your hardware. Many users/home cockpit builders use MobiFlight in conjunction with FSUIPC (unregistered) to control via FSUIPC offsets, so you could possibly look into that. John

Hi Max, I asked Pete about this, as he also uses the Prosim 738 this is his reply: John

All PMDG specific offsets are read-only. To control PMDG aircraft, you need to use the PMDG custom controls. You can use these in the free version by using the general control offset at 0x3110. See the following first part of the following topic on how to control PMDG aircraft using the custom controls - the latter part of the topic describes how to assign the controls to buttons/switches/keys, but you can also write the control number to offset 0x3110: John

Is it FSUIPC7 that is crashing, or MSFS? If MSFS crashes, FSUIPC7 will exit. Please check your FSUIPC7.log file (you can post it here) to determine if it is exiting or crashing. Also, check the windows event viewer, there should be crash events there - if they are for MSFS you need to report to Asobo/MSFS. If there are crash events for FSUIPC7, then post them here. Note there is also an issue with FSUIPC7 when running on Windows 11, where it thinks MSFS has exited and so closes, but MSFS is still running. If this is your issue, check the README.txt (in the FSUIPC7 zip file you downloaded) which will tell you how to resolve this particular issue. John

That is why you should attach your scripts... I'm not going to laugh, i'm not even going to look... I haven't got time to look at such a lengthy lua script. I am trying to help you recognise key presses/releases, nor debug such a lengthy script... You keep saying that you are having issues with keypresses or releases not being recognised, so why don't you just try a simple script to test this, as I keep asking. Try running the following lua script and tell me what you see logged when you press the k, l and m keys: function keyUpDown(keycode, shifts, downup) if downup == 1 then ipc.log(keycode .. "Key Down") elseif downup == 0 then ipc.log(keycode .. "Key Up") end end k = 0x4B -- k key l = 0x4C -- l key m = 0x4D -- m key event.key(k,0,1,"keyUpDown") event.key(l,0,2,"keyUpDown") event.key(m,0,3,"keyUpDown") When you run that and then press: - the k key, you should see the key down logged - the l key, you should see the key up logged - the m key, you should see both the key down and the key up logged If that is working for you then your issues is with your script. Try lua debug logging to see what is going on.