John Dowson

Not sure I fully understand this...why would the hat switch have double the number of functions, especially as you are already holding down one of the hat switches, so how can you trigger the others? Or do you mean that you are using a button (hat switch or otherwise) as a type of 'shift' key, and holding this down when you press another button triggers some sort of virtual button instead of the original button? We usually don't recommend using other config software if assigning in FSUIPC. FSUIPC reads your device directly at a low level and probably won't see these 'virtual buttons'. To achieve something similar in FSUIPC, you can use the Compound Button functionality, which allows you to specify actions for one button which are dependent on the state of another button (or switch). See the Advanced User guide for details (P22 in the FSUIPC6 manual).

👍😎

Ok, then you need to uninstall and re-install some VC++ redistributables. Please see the provided README.txt: I wouldn't do this just Yet. That error is most likely shown when MSFS tries to start FSUIPC7. However, it certainly shouldn't crash the sim - it should just prevent FSUIPC7 from starting. Anyway, uninstall and re-install the VC++ redistributables and see how you get on.

Does MSFS run without FSUIPC7 installed? Can you manually run FSUIPC7 (without MSFS running)? I see Pete has also replied: Uninstalling FSUIPC7 and running MSFS would verify that it is an MSFS installation issue. If its an MSFS installation issue, then check the Asobo forums and/or raise a ticket with them.

Great! Please try the attached version: FSUIPC6.dll

So MSFS is crashing even before it even tries to start FSUIPC7? It is the EXE.xml file that is created or updated, not the .exe. Did you install the FSUIPC WASM module into your MSFS Community folder? If so, try (temporarily) moving it out of your Community folder to see if that helps. Do you have anything else installed there?

Please try with this version: FSUIPC6.dll I can only see it occasionally in event.button, but I've added some extra logging around event.offset in the dll above.

Ah, sorry - I attached a debug build rather than a release build so you will be missing some windows dlls to run that. I'm going to add some more logging and I'll post a correct build later today for you to try.

Could you also try the attached version please: FSUIPC6.dll

Yes, the lua's were running as they were killed when you quit. Strange. What do you mean by this? The log should show each line of the lua being executed, so what wasn't expected? I've done further tests here and I can occasionally get an event.button not firing, but its very random, and never occurs when I step through in the debugger. I also can't get it to happen when I add additional logging to try and work out what is happening. Its very strange. - I'm thinking it could be a timing issue between different threads. I will keep investigating... John

You can either: - assign a button or key to the List Local Panel Vars control and use that - use the lua script log lvars.lua, included in the lua examples zip (in your FSUIPC documents folder).

Is this when MSFS is in full-screen mode? Strange, as I don't see this behavior. What happens if you press alt+f and then click the FSUIPC task bar item? And if you press alt+ enter (when MSFS has the focus - to put MSFS back in windowed mode) and then alt+f to display the FSUIPC window, does it then display ok? Has it always been like that for you? Nothing has changed in this area since initial release and this is the first I have heard of such issues. Do you have anything running (or an MSFS option maybe) that is keeping the MSFS window on-top?

I was also just replying when I saw Pete has replied... You should try this and also maybe activate logging for Buttons & Keys, and take a look at the log when you press the buttons (assigned to the flaps controls) and compare it to what is logged when you use the F6/F7 keys. You can post your FSUIPC4.log and FSUIPC4.ini files here and I'll take a look. John

Done.

Hvars are made known to FSUIPC7 via the use of *.hvar files. Do you have such files installed for the aircraft you are using? I don't think the installer will remove any hvar files that you added, although it may over-write the provided hvar files under the Community WASM folder so you may lose any changes to those files, which is why it is preferable to keep your (user) hvar files in the WASM persistent storage area. Please see the Advanced User guide (P44) on how to use hvars with FSUIPC7.

You should be able to run MSFS without an internet connection. What happens when you try to start MSFS from its own menu entry or desktop icon (or via the steam app if using steam)? I have deleted the similar posts you made in an unrelated topic (FSUIPC PFC Random Input - Need Assistance).

MakeRunways is a separate download, and is compatible with all versions of P3D, FS2002, FS2004, FSX and MSFS (all on Windows 10). It is available from www.fsuipc.com or the download section in this forum. If you already have it installed, it should work with MSFS, but make sure you are using the latest version. John

Ok, thanks - and yes, please update if you manage to resolve. One thing though, on this: Has the com bit-speed been changed to use that required by the device? Maybe worth double-checking. Other than that, good luck and please report back if/when you manage to solve. John

Your FSUIPC7.log file shows that it was MSFS that crashed, and FSUIPC7 exited normally: FSUIPC7 will exit when MSFS CTDs. If you check your Event viewer logs, I'm sure you will see and MSFS crash report entry before that of FSUIPC7. As O said, when MSFS CTDs, this creates an exception in FSUIPC7 as the SimConnect handle is no longer valid. This will generate fault reports in FSUIPC, but they are handled gracefully. However, when FSUIPC7 is auto-started by MSFS, it must close when MSFS is no longer available, otherwise the MSFS process will not exit cleanly. So, your problem is with MSFS - you need to check the Asobo forums on CTD issues and raise a new report if necessary. If you want to verify this, start FSUIPC7 manually BEFORE you start MSFS, and uncheck the option Exit with FS. You will get an error when MSFS tries to start FSUIPC7, but this can be ignored. When you do this, you will see that if/when MSFS CTDs, FSUIPC7 keeps running. So the promlem is with MSFS/Asobo, not FSUIPC. John

Previous license only expired yesterday. I will generate a new one in a couple of days. John

FSUIPC7 doesn't do anything with devices unless you tell it to. In fact, I don't think it will even recognise the devices unless you have installed any specific drivers so that they are recognised as HID joystick type devices. Maybe you can show me your FSUIPC7.log and FSUIPC7.ini files. Do you have the FSIOPC7 WASM module installed? If so, maybe test with removing that temporarily from your MSFS Community folder, to see if there is an issue with overlapping events. You can also try activating logging for Events to see what, if any, events are being sent that could maybe explain the behaviur you are seeing. I believe so, although I haven't actually used SPAD.next with FSUIPC7, only with FSUIPC6/5 and P3D. It integrates well with FSUIPC on those platforms, but you may wish to confirm about MSFS on SPAD.next support.

I have just checked your details here and they validate fine - are you sure that you are entering them correctly? Did you try running FSUIPC7 - does it run ok? I will PM you a key file with your registration details and you can try that. John

First, please download and update to v7.2.8. Then replace the FSUIPC7.exe with the attached one and try again: FSUIPC7.exe If you still get a CTD, please show me your FSUIPC7.log and FSUIPC7.ini files, as well as the Event viewer info, thanks. The Event viewer info you posted shows that it was MSFS that actually crashed first, causing an issue in FSUIPC7 afterwards. If you check your FSUIPC7.log file, you will most probably find that it exited automatically due to MSFS crashing.

There was a dereferencing error on adding an lvar to an offset with the format UD which has now been corrected. Sorry about that. John

I thought you were using 7.2.0d? Please try the attached version. You will need to re-install 7.2.8 first (as the 0.5.4 WASM is needed): FSUIPC7.exe