John Dowson

You need to activate logging for Events to see the reverse control being sent. However, as Pete has said, you have no assignments to this in FSUIPC so must be controlled from somewhere else, either the Honeycomb config app or P3D. You can still activate logging to see what events are being used though, and this may show you the difference between your v4 and v5 configs. Your FSUIPC6 is also out-of-date. You should upgrade to the latest version, v6.1.1 - only the latest version is supported. John

No, I don't think those offsets currently work for the A320. The toggle seems to change the value (from 0 -> 1 and 1->0), but when setting to 0 it quickly reverts back to 1 - so it looks like it toggles on, not off. The lvar A320_Neo_BAT_State does seem yo be writeable. There are also lvars XMLVAR_ElecMaster and XMLVAR_Electrical_Master_Battery_Turned_ON which look to be writeable, but they don't seem to do much - maybe you can check. It was reported here: that you could possibly read the battery states: However, the simvars BUS LOOKUP INDEX and BUS CONNECTION ON:6 are not currently held in any offsets. Also, the master batteries in the A320 UI are inoperable. For full control of the A320, you should really try the FBW mod (see https://flybywiresim.com/).

FSUIPC7 does not record flights. I cannot help you with smartcars ACARS, you should contact their support.

Ok. You could try a trial license first, usually available here: However, the latest one ran out yesterday. I'll post another there in a few days.

This may be useful to start with: It is quite old now, written for an earlier version of FSUIPC, but still applicable. Of course, that is just to trigger on joystick buttons. Once you have sounds working, you can then update to trigger on events.

This topic is for questions and issues on the v7.2.0 beta release, which includes a new facility for adding Lvars to Offsets using the FSUIPC7.ini. This release is available here:

Ah, ok. Didn't know about that one. I'm on the MobiFlight discord channels. I can't seem to join that one - I can only select xbox to identify, and it crashes just after signing in to my account (although I have given permissions for AlpDentifier to access my MS account).

Yes, it should be possible. In fact, there are probably some freely available scripts somewhere that do this sort of thing. There was a support request recenly from an FSUIPC user who started hearing clapping on touch-down and thought it was something that FSUIPC was doing, when it was in fact an FSUIPC lua cript they had installed and forgotten about. There is plenty of general information on lua on the web, and lua documentation provided with FSUIPC, as well as some example lua plug-ins. Fot sound, check the Sound Library section in the FSUIPC Lua Library document - to play a sound (.wav file), you can use the sound.play function.

yes, as I said, when MSFS crashes, it will cause a fault in FSUIPC. Please read my previous comment. Where/what is the MSFS discord server? FSUIPC7 is a separate process, an executable. In no way should a separate process be able to cause MSFS to crash. The fault is in MSFS.

Do you mean the MSFS menus? If so, no, FSUIPC does nothing with the MSFS menus. I don't know what would cause that. Can you? I didn't realise that, it is supposed to be disabled (no point in logging weather as there is no weather to log). I will disable it.

You log indicates that it is MSFS that crashed. I can't see your images that well (a description always better), but you have a red crash error BEFORE the FSUIPC fault report (not crash) which O [resume is MSFS. When MSFS crashes, it can also cause an exception (not crash) in FSUIPC. As you have the option 'Exit with FS' selected, when MSFS crashes, FSUIPC7 will also exit, as you could see if you looked at the log you posted: That log shows FSUIPC exiting normally due to MSFS not being available. Any MSFS crashes should be reported to Asobo via their forums, with the crash event included + crash dump files if available.

You can purchase a license for FSUIPC7 on SimMarket, not SimFlight: https://secure.simmarket.com/john-dowson-fsuipc7-for-msfs.phtml John

Yes, if you want to use them! Creating an empty profile in MSFS will remove all your assignments in MSFS. You do this when you calibrate. When you calibrate, you set the max an min deflection (using the max/min Set buttons), and then most axes also have a null zone you can set, using the middle 'Set' button. You set two values (the order doesn't matter) which will be the edges of your NULL zones. Check the documentation if unsure (The Easy Step-by-Step Way to Calibrate Your Controls in the User Guide).

You should create an empty profile for your devices in MSFS. Go to the MSFS Controls page, select your device and then click PRESET MANAGER. Then click +, and that will create a new empty profile. Give it a name and save it. You can handle this in FSUIPC7 as you did in previous versions of FSUIPC - by specifying an adequate null zone in your calibration. You can also maybe try the *SpikeRemoval (e.g. ElevatorSpikeRemoval) ini parameters, if you previously have used them, but I think that just removes max signals and won't help with smaller fluctuations.

But this is what the Rotaries.lua does for you, activating different virtual flags for fast and slow movement (in each direction). So you can assign to the fast virtual button on press and release, and the slow virtual button on press only.

Sorry, I don't know how you would get that information on Android. FSUIPC does not run/is not supported on Android. If Skydemon has access to this, maybe ask on their support forums. Unless anyone else has an idea....?

@Tony Goswell Could you try the attached dll please, v6.1.2a. Hopefully this will fix your issue. FSUIPC6.dll

I've added it in the attached dll if you would like to try it, v6.1.2a: FSUIPC6.dll You can also use this new control when auto-save is disabled. The new control is called Trigger Auto-save. Later: I have updated the dll with a minor change (the control number has changed), so please download again if already downloaded

No this is currently not possible. However, it is something that is relatively easy to add and is useful so, I will add an additional FSUIPC control that manually triggers an auto-save call. This will be for FSUIPC6 (and FSUIPC7) only (FSUIPC5 is now closed for further development). I will look into this in the coming weeks.

Are you using the same assignments in v4 both and v5? Maybe try logging buttons and keys, events and axes controls on both v4 and v5 and compare the logs on the two versions to see if there is any difference.

Please try running the installer again (do not manually uninstall first - let the installer do that). Hopefully it should work the second time. If not, you can download and install manually. For details on this issue, please see: Also, please check for similar posts before creating a new topic in future.

where did you get the WASMClient.exe from? Uoi should download the zip package, which includes the WASM. Please see the announcement page: for details: Note if you are using FSUIPC7 (registered), you don't need to use the WASMClient. Most of the functions are available directly in FSUIPC7.

Thanks for reporting this. Not sure what is causing this at the moment, but there was an update in those versions relating to the logging of ATC_MENO_OPEN/CLOSE events, and I am wondering if this is affecting the event.textmenu call. To test, could you try the attached dll please. If that has the same issue, I will look into this in more detail later this week. John FSUIPC6.dll

I've updated the installer and done some more tests, and it seems that the UserCfg.opt file could not be opened for reading on a clean installation in any circumstances. I don't understand why. However, if I try a second time to read the file, it works ok. Its very strange, but I have updated the installer to handle this. I will release this with 7.1.1 in a few days.

Can you check your FSUIPC7.log file. The console just displays the contents of this file. If that file is empty, then you have probably installed in a protected folder - show me your InstallFSUIPC7.log, or try installing in a different folder.