John Dowson

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?

I added the sound.adjust and now I get sound out of all of my sound devices, so not sure why its not working for you. Add that custom logging and see what it logs - this is my log: John

FSUIPC takes its key input from the P3D main window (class name FS98MAIN). Any key sent to that windows class should be picked-up by both P3D and FSUIPC. event.key is a lua event function that calls the handling function when a key is pressed. FSUIPC needs to see/receive the key press/release events for this to work. FSUIPC runs as a dll inside of P3D. You need to get P3D to recognise the key press, then FSUIPC will also see it.

Tested on my machine and I only get sound out of one of my 7 devices. Not sure why, but I don't have time to look into this at the moment. I will make a note and look into it when time permits, but this won't be for quite a while.

You could also try sending a Throttle1/2 Decr control after the Set Throttle1/2 Reverse Thrust On or Set Throttle1/2 Reverse Thrust Toggle control on the button press. To send multiple controls, you need to edit the ini (comment out the first assignment, make the second one, then uncomment the first one). No idea why that would be. Is the button being triggered and the control being sent? Logging would tell you this (Buttons & Keys and Events).

Select the Custom entry under the Log menu, and enter x20...

12 is an arbitrary limit - I could increase this to 20 or 30 maybe, but I think that would be the maximum for display in one window. To log an arbitrary number of lvars, you could roll out your own lua script to do this. Attached is also one that you can use - this does string matching for including and excluding lvars to be displayed. John LogLVars.lua

@Nilsooo Could you please report back on this - I would like to understand why this is not working for you as it seems fine here. John