John Dowson

But what type of variables are they? Are they scoped lvars? Then they are probably scoped lvars. MobiFlight will read these by executing a calculator code script and getting the value in the response. In FSUIPC, I do not provide/allow for a response from executing calculator code. Again, this depends on the variable type. If they are scoped lvars, you can only get the value, and add this to an offset, by writing/copying the value of the scoped lvar to a standard lvar, and then read or add this to an offset. You would need to update the value of the lvar (from the scoped lvar) at regular intervals (e.g. at 6Hz) as well, so that the lvar holds the current value of the scoped lvar. You can do this using a lua script.

It all depends on what variable types they are. They won't be simvars, or A-type variables, as these are only defined by MSFS/Asobo. They could be lvars, hvars or input events (also known as b-vars). First, with the aircraft loaded, try listing the available lvars (Add-ons->WASM->List Lvars). Do you see them listed? You can also try listing the available Input Events (Log->List Input Events) - do you see them there? Note that MSFS2024 also has a new type of lvar (local variable), called 'scoped lvars'. There is currently no way to discover such vriables, but you can update them using calculator code. To read them, you would need to use calculator code to write the value to a standard lvar, and then read that. See If it is a scoped lvar, it may also be available as an Input Event, so please make sure you check there.

Yes.

By default, lua scripts are only loaded/recognised when placed in the FSUIPC7 installation folder. If you are using a subfolder, you need to add LuaPath=Scripts to your [LuaFiles] section. Do NOT manually edit or change the [LuaFiles] section (apart from the LuaPath entry) unless you know what you are doing. The list if lua files is maintained by FSUIPC. The ipc.display function is no longer reliable in MSFS, as it depends on the Simconnect_Text function which is no longer available. You need to use the Wnd library for display. The documentation for this function does say: This was working for basic display in earlier versions of MSFS. but has basically been unavailable for quite a while. I will update the documentation to make this clear. John

What works - the one I attached? Please try building this yourself, if you have not already, and check that that works. That would be the first step. Maybe, I am not sure, but as its just a c lib I would have thought it would be a fine in a console app...first make sure you can build and run the UIPCHello example. If that works, maybe convert your example to a win32 app to see if that works.

One way, but why not just define a macro...

There are two ways to send mu;tiple controls on a button or key press: 1. Use macros. 2. Overload the controls. e.g. make the first assignment, then comment this out in your ini, then reload the assignments and make the second assignment. Repeat until you have all the assignments, then uncomment the ones you commented out and reload the assignments again. These are documented in the User guide, page 27: John

If these controls don't work when assigned externally, this should be reported and fixed by Cowansim. There are a couple of input events, that way work, but I am not sure they are the same (I am not that familiar with helicopter controls): If those are the same as the cyclic lat/long controls, you could maybe try those, but I suspect they are different and you will have to assign in MSFS until this is fixed by Cowansim. Best to tag a user for a direct question, e.g. @Nevarc ? John

All 3 parts if the key (Name. Address/Email & Key) must exactly match the details shown in your purchase email or SimMarket account. Try cutting and pasting all three parts of the key from your purchase email. If it still doesn't validate, you probably need to update your VC++ redistributables. Download and install the latest combined VC++ redistributable packages (both x86 and x64) from https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist If you still have issues after updating those, let me know your purchase order number (do NOT post key details!) and I will check them here. John

Hi Ray, That offset is just for the 'Fuel Tank Selector', and it is not a custom control. To set this, you would use the Offset Word Set control. To empty the tanks, try writing 0 to the tank level offsets (using Offset Dword Set😞 John

All three parts of the key (Name, Address/email & key) must EXACTLY match the details in your purchase email (or SimMarket account), othrwise your key will not be valid. This is why we recommend to copy and paste these details from your purchase email. I also gave you a key file with the correct details that you were not putting in the correct place. I really don't understand why you had such difficulties with this.... John

Are you sure that the FSUIPC7.key file exists in that installation folder? If so, are the contents correct (i.e. your name and address))? Me neither... Why not? Are you using anything else other than Windows Defender? Maybe try installing on a different drive, to see if that makes a difference.

The WASM module is loaded by MSFS and should be running. If FSUIPC cannot connect to the WASM module, please show me your FSUIPC7.log file.

But the key file is still not in your installation folder: If it was in your installation folder, the User Name and User Addr would be populated from that file. If it is there, and it has the correct name (please check!), then something else must be blocking FSUIPC from reading this file. Does your S drive have any special permissions associated to it? There also seems to be an issue with your internet connection: Either that or your anti-virus is blocking FSUIPC7. Did you check your anti-virus?

Your log shows: i.e. there is no FSUIPC7.key file in your FSUIPC installation folder. As I said, you need to place the FSUIPC7.key file in your FSUIPC7 installation folder, ie. copy it to S:\MSFS2020\ But if that is your actual MSFS2020 folder, then you should install FSUIPC7 in a different location. It should be in its own folder, not installed into any MSFS folder.

Has APLv2 been updated to recognise MSFS2024? If not, you could try writing 13 to offset 0x3308 (best done using the ipcInit.lua script) to fool APL into thinking that MSFS2020 is running and not MSFS2024. Otherwise I do not know why APLv2 is not connecting properly - you should ask about this on the APL forums, You can post FSUIPC7.log files here and I can check for any errors when its not connecting, but if FSUIPC7 is connected and functioning normally. it will be an issue with APL. John

What says 'demo'? Why are you being so cryptic? There is no such thing as a 'demo' in FSUIPC....it is either licensed or unlicensed. Did you re-install the combined VC++ redistributables, both x64 and x86, as I asked? If you saved that key file to your FSUIPC7 installation folder, then please show me / attach your FSUIPC7.log file.

Probably. '\' is the lua escape character, so any lua strings that want to use this character as it is must use '\\' (or '\b'). So all lua functions that take a string argument that contains a path will need this escaped. There are many such functions. What documentation? I am not going to state this in every lua function that accepts a file path. Consult the lua documentation or google for details on lua, e.g. https://how.dev/answers/what-are-escape-characters-in-lua John

Looks like I added GetInputEventValue twice instead of adding getInputEventValue. I will correct this in the next release. John

No. Nothing has changed - if it has, the many add-ons that use the FSUIPC7 would no longer work... Did you try compiling and running the provided test program (UIPCHello)? I have also attached this for you to try - does that connect to FSUIPC? John UIPChello64.exe

Your license validates just fine. I have PM'ed you a key file to try. John

Did you try the Axis Cyclic Lateral/Longitudinal Set controls? Also maybe check for any relevant Input Events. So the Axis Cyclic Lateral/Longitudinal Set controls don't work? Check for any relevant Input Events or Lvars.

Show me your order number and I will check your details. Please note what in 99.99% of the the reports on this are down to user error... John

It could be the wav files you are using - see It may have a bit_sample_rate value that prevents it from being played (if so, it can be converted). Can you attach one of the wav files here and I will check them, and also maybe try with a different wav file (e.g. the one attached). That custom logging of x20 should also help....show me your FSUIPC7.log file with that added, and remove logging for Lua Plugins and Log Lua Separately (I like to see everything in the same log file) - the ipc.log statements should be enough.. bong.wav

Sorry but I have no idea. Is there maybe a difference in the privileges when you start ProSim before or after WideClient? Why does ProSim stop working - can it see the FS and/or FSUIPC? You could try changing the ports used by WideServer/WideClient, but from what you say I don't think this will help. Are there any changes from Prosim 2 to 3 that could cause this? Have you asked on ProSim support?