John Dowson

@Blake Buhlig Just took a look at this. Seems each 'click' on the bravo rotary is a press and release, but even the timings between these near simultaneous events seems to be a minimum of 60-80ms, so I don't think its possible to get more than 8-10 presses per second (even when PollInterval is set to 1, which is what I used for testing). Of course, you can use releases as well. Attached is a short lua script that will log fast/slow for the Bravo trim wheel and adjustment rotary, which gives logs the following: Here's the script if interested: RotariesEvent.lua It also requires socket.lua: socket.lua I'll take a look at using the com library at some point, but I don't think it will be any faster... John Later: one other thing you can try is to increase the increment/decrement (delta) value on successive 'fast' clicks, so the delta increases the more fast clicks received, and reset the (fast) delta on the next slow button press

Sorry, ignore that - it was in the package downloaded from that link provided. And yes, it does seem to just work by adding the socket.lua to your FSUIPC installation folder. I will update the FAQ entry accordingly. Thanks, John

Hi Emile, first, sorry for the delay with this, but I would like to clarify this now.... Do you have a link to the socket.lua you refer to (or attach if allowed)? I can only find this and there is no socket.lua: http://files.luaforge.net/releases/luasocket/luasocket/luasocket-2.0.2 Thanks, John Later: the LuaSocket project page at LuaForge seems to be down or gone...

@Nenad Bogojevic Looks like a problem with the build of the last version I posted. Here's one I tested - max characters allowed is 255 (or 256 with terminating \0):FSUIPC7.exe Also contains a minor update to change the value parameter when creating an lvar from a dword to a double. There's also a corresponding update to the WASM for this, but the latest published one will still work Ok.

The transponder setting is held in offset 0354, in 2-byte BCD format. So you can assign a button or key press to the FSUIPC added control Offset Word Set, giving 0354 as the offset value and 0x1200 as the parameter. John

Ok, very strange, but glad its now working.

Are you sure its not running? The installer performs a simple check to find the process FSUIPC7.exe, and if found will display a message and abort. I can't see how this check can fail - and it hasn't changed or been an issue since release....Sis you check in the windows Task manager?

@Nenad BogojevicCould you try the attached build please. Not sure why its crashing when using more than 255 characters, but I've added a check for this now. Sorry, still now working, looking into it...

It does kill and re-run the script. However, the size and position information is only used the first time the script is ran, then on subsequent runs the size & position is taken from your FSUIPC7.ini file, from your [ExtWindow] section. So, to get the new size/position, you must delete the entry for that window in that section first. Alternatively, Ext windows can be moved and re-sized manually, using the arrow keys to move and the same keys but with either the alt or ctrl modifier to resize, and the updated size/position will also be recorded in your ini file. Or you can modify the size / position directly in the ini file.

Ok, good to know it works, but it shouldn't crash when the limit is exceeded - I'll fix that and log a message when the limit is exceeded. Do you think 256 chars (well, 255 + a terminator) is enough? I could easily extend further (up to 8k, the max size held in a Client Data Area).

Have you actually tested with a calc code string > 64 characters? The limit I have currently set for this is 256 characters (and this can be increased relatively easily, but would require an update of the WASM module to handle), so maybe I was mistaken with the lua limit. I will check this - tomorrow though....

Thanks for the update - good to know! Maybe, I'm not sure yet, its something I need to look into. I'll take a look in the day or two to see if this is an easy change or not. If it looks to be something that could be tricky and/or risky, I may have to leave this limit. However, I could add an additional FSUIPC control for executing calculator code, which could except up to 256 characters (I was planning to add this anyway). Thanks for the additional hvar file! Cheers, John

If its ACARS not connecting to FSUIPC7, then you need ACARS support. I cannot support 3rd party clients of FSUIPC. If its FSUIPC7 not connecting to MSFS, I need to see your FSUIPC7.log file. It should do. If it doesn't, then you should check your InstallFSUIPC7.log to see if an error has been logged. This is usually caused by other 3rd party software corrupting the EXE.xml. Please see the included README.txt file, item 3 under Problems running FSUIPC7: FSUIPC7 does not auto-start with MSFS If that doesn't solve your issue, check one of the many support requests where this issue has been addressed numerous times....

Just posted!

The attached key file is valid until 25th May 2021: FSUIPC7.key

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.