John Dowson

Ok, then for some reason MSFS hasn't created the registry entries which tell FSUIPC7 where MSFS is installed. There is no much I can do about this. FSUIPC7 will still run ok, but this will have two consequences: 1. the FSUIPC WASM module will not be installed 2. the auto start component will not be available For the WASM module, you can download this from www.fsuipc.com, and copy the WASM module manually to your MSFS Community folder. For the aut0-start component, you can manually create the required EXE.xml file following the instructions in this thread: John

The easiest may to achieve this is to overload the assignments to the button by editing your FSUIPC7.ini file. Locate the assignment to the first lvar in the macro, it will look something like this: <index number>=P<joyId/letter>,<buttonId>,CM1:1,0 -{Macro <macro file name> L:ASCRJ_OVHD_LDG_LEFT}- then copy this line and duplicate twice, then change to give both a unique <index number> and increment the macro index, to end up with something like <index number>=P<joyId/letter>,<buttonId>,CM1:1,0 -{Macro <macro file name> L:ASCRJ_OVHD_LDG_LEFT}- <index number + 1>=P<joyId/letter>,<buttonId>,CM1:2,0 -{Macro <macro file name> L:ASCRJ_OVHD_LDG_LEFT}- <index number + 2>=P<joyId/letter>,<buttonId>,CM1:3,0 -{Macro <macro file name> L:ASCRJ_OVHD_LDG_LEFT}- You don't need to change the annotation/comment - FSUIPC will update this when it is next ran. If you do this when FSUIPC7 is already running, you can reload the changes from the buttons assignment dialog panel using the 'Reload assignments' button. John

The WASM will load any .hvar files whose name is a substring match to the aircraft name, as reported in the log (from the aircraft.cfg file). So A320FWB.hvar wouldn't match, so use FWB.hvar or TAM.hvar, or even the full "FWB TAM.hvar".

Do you have a Steam or MS Store version of MSFS? Have you ran MSFS at least once before trying to install FSUIPC7?

32-bit software/drivers can still run on a 64-bit system, as long as whatever is talking to it understands that it is a 32-bit program... I would just try it on a single system first. If you use/need FSUIPC, you can first try with a trial license, available in a sticky post at the top of this forum. WideFS7 is compatible with FSUIPC7, if you want to go down the client PC route. However I don't know anything about SimKits UCC2, so maybe other simkits users' opinion on how to get this working with MSFS would be more helpful. Maybe try the SimKits or Asobo forums. John

hvars are only recognised by FSUIPC7 if they have been registered via an appropriate *.hvar file, located either under the FSUIPC WASM installation folder or under your MSFS persistent storage area. See the Advanced User guide for details. If the hvars were previously available and are no longer visible, this suggests that either the *.hvar file(s) matching the aircraft name has changed, or the aircraft name has changed and no longer matches the name of the aircraft you are loading. So, please read the Advanced User guide so that you understand how hvars are recognised, and then check the folders. If you require further help, activate debug level logging in both the WASM and WAPI (instructions in Advanced User guide) and show me your FSUIPC7.log and FSUIPC_WASM.log files. John

Ah, yes - you didn't mention that! Ok, good. Sounds like the windows 11 installation may have screwed up the installed VC++ redistributables. Interesting. Cheers, John

i would try that. Of there is no .ini or .log files, that usually means that FSUIPC cannot write to the installation folder due to Windows protection. Try installing in a different folder (e.g. D:\FSUIPC7) and running MSFS again to see if the .ini and .log files are created. Nothing to do with your issue though. But for me to take a look at your issue, I need to see an FSUIPC7.log file produced form the session where it CTD'd. John

Strange, if that is the full contents of your installation folder. There is no FSUIPC7.ini either - have you assigned anything in FSUIPC7? From your installation log, I see you installed under D:\Program Files\fsuipc. Is D:\Program Files your windows Program Files folder, and thus protected? If so, you should uninstall and re-install in a different folder.

No, the FSUIPC7.log file, not the InstallFSUIPC7.log file. I don't really need to see it if it says that FSUIPC7 exited normally due to MSFS no longer being available. Just take a look at the log file. You can post it if you like.

In your FSUIPC7 installation folder - if you don't know where that is, use the File->Open Installation folder... menu option from FSUIPC7. If you can't see the FSUIPC7.log file, see the annex in the installation and registration guide. John

Even stranger.... I suspect something is wrong with your windows installation. I'll take a look (maybe later today, more probably tomorrow) to see if I can add some extra logging to see what is happening. In the mean time, can you try uninstalling your VC++ redistributables and reinstalling - instructions are in the README.txt that comes in the zip download. John

Can you please show me your FSUIPC7.log. I suspect that it was MSFS that CTD', and FSUIPC7 exited normally due to MSFS no longer being present. The log would confirm this. This can generate a windows fault event in FSUIPC7, but there should be a preceding event that indicates MSFS has crashed. If this is the case, you should report to MSFS, as you have done. John

This is very strange! Could you try manually starting FSUIPC7 before MSFS, and uncheck the option 'Exit with FS', then start MSFS. FSUIPC7 will then attempt to re-connect when it thinks MSFS is no longer available. Please try this and show me the updated FSUIPC7.log file. John

Good to hear! Yes, I think the custom events (those with a period '.') get translated by the handling code in the MSFS/WASM. In FSUIPC, you always need to declare (and assign to) custom events with an embedded period. Thanks! John

If the standard controls/events don't work, you need to check the available hvars/lvars. The best place to do this is to see what the MobiFlight presets use - see https://hubhop.mobiflight.com/#/list. You don't have to use the MobiFlight WASM/presets (but you can if you like), but the preset list will show you which lvars/hvars/calculator code to use. These are also available in the MF preset list. For example, for WXR - preset B747_8_BTN_WXR which uses: (>H:B747_8_MFD_BTN_WXR) (>H:B747_8_PFD_BTN_WXR) and STA - preset B747_8_BTN_STA which uses: (>H:B747_8_MFD_BTN_STA) (>H:B747_8_PFD_BTN_STA) and etc You can either use the calculator code directly using lua, or if the calc code is simply activating hvars (as the above) or setting lvars, you could use macros (overloaded to activate multiple hvars). You can test to see if the calculator code actually works by using the Add-ons->WASM->Execute Calculator Code... menu option. John

The current one expires today - I will update in a day or two.... John

Yes, but sorry - I meant 'I can only see A32NX.FCU_ALT_PULL', i.e. with a period ('.') and not an underscore ('_'). Well, its still not clear to me what you are trying to do, as I have no idea where the event A32NX_FCU_ALT_PULL comes from, how you would use it, or what handles it.... Custom events must contain a period ('.'), which is why I keep asking you to try A32NX.FCU_ALT_PULL and not A32NX_FCU_ALT_PULL, or A32NX.FCU_ALT_PUSH and not A32NX_FCU_ALT_PUSH. John

How many times do I have to say this.... Where/what is the event A32NX_FCU_ALT_PULL and what handles this? I can only see A32NX.FCU_ALT_PUSH - they are different! Well, if you assigned to ALTITUDE_SLOT_INDEX_SET then that is what you will see! And again, I do not know what the control A32NX_FCU_ALT_PULL is, or what handles that. Have you tried with A32NX.FCU_ALT_PUSH, as I keep advising.... And note that these are FBW events, nothing to do with FSUIPC7. FSUIPC7 just provides the mechanism to use custom events, via use of event files. If they don't work, you need to contact the provider of the event, i.e. FBW. John

👍

A32NX_FCU_ALT_PUSH and A32NX.FCU_ALT_PUSH are different events.... Are you using the latest dev version of the FBW? Dont think this is available in the stable version yet. Make sure that you are using the latest version of FSUIPC7, v7.2.10. The folder will be under your FSUIPC7 installation folder, which you can open from the File -> Open Installation Folder... menu item in FSUIPC7. John

Ok - I doubt the update will solve your issue, but its not worth me looking at your files when using such an old version. It sounds like a device or connection problem (i.e. hardware), but update and show me the new files and we can take it from there. John

You could try the HidScanner utility, available here: Then that would confirm it is a problem with your hub. I agree and also use powered hubs, but make sure that the hub has enough power for all the attached devices.

That is because it is not a standard MSFS control/event, but a custom event. Presumably its from a 3rd party add-on, do you know which one? It doesn't look like a MobiFlight event/preset, or an FBW one - the corresponding FBW event is A32NX.FCU_ALT_PUSH - do you mean that? To use such events in FSUIPC, you need to make an event file (*,evt) to make them known to FSUIPC. Please see the Advamnced User Manual. A bunch of event files are included in the EventFiles sub-folder of your FSUIPC7 installation. If the event is the FBW A32NX.FCU_ALT_PUSH (and not A32NK_FCU_ALT_PUSH), then you can make this (and other FBW events) known to FSUIPC7 by moving the file flybywire-aircraft-a320-neo.evt from the EventFiles sub-folder to the main installation folder (i.e. up one level). John

No, as letters have now been assigned to your controllers - if you changed that back it just wouldn't assign letters to newly detected controllers, it wouldn't make any difference to your current set-up. If you are not manually assigning letters, best to keep this set to 'Yes'. John