John Dowson

Thanks for the update. Please be aware that these forums are now closed, and will be removed at the end of the year. For any other issues or questions, please use the new Support forums which are available here: https://fsuipc.com/support/. You will need to re-register on the new forums. Regards, John

@Gilson Sorry but I accidentally deleted your post in the new forums. The first post was partial and repeated, so I deleted this but this seems to have deleted the whole thread. Anyway, you were obviously using the ipc.execInputEvent function incorrectly - it (obviously I would hope) takes the name if the input event as the first parameter, and not whatever nonsense you were previously using. And as you are executing the input event directly, there is no need to add it to an offset, i.e. remove your InputEventOffsets section as it is not needed. And I don't understand why you are even using lua for this. It is far easier to just assign your button directly to the Input Event. In the button assignments panel, check the Select for Input Events checkbox and then select the Input Event from the drop-down. No need to use lua at all for this. John

I am slightly confused by this. Is AIRLINER_LIGHTS_EXT_STROBE an Input Event? If so, you can just assign directly to that, or in lua you can use the ipc.execInputEvent function. You can it it to an offset if you like, and can then write to that offset to trigger the input event using one of the ipc.writeXX functioons. But you cannot add it to offset 65590 - that is outside the range of available offsets. Choose one in an offset area that is free for general use, such as 0xA000, e.g. to add as a byte value (for 1/0 or on/off values, or numbers in range 0 to 255 or -125 to +125) it would be: [InputEventOffsets.Default] 0=AIRLINER_LIGHTS_EXT_STROBE=UB0xA000 You can then assign to Offset Byte Setbits or Togglebits, and in lua you would use ipc.writeUB. But you only need to add it to an offset if you need to read the value for some reason. This doesn't makes sense and gives that error you see, This sends the FS control with number 65590. There is no such control with this number hence the error. Do not confuse control numbers with offsets - they are completely different things. Please also note that these forums are now closed. Please use the new support forums, available here: https://fsuipc.com/support/ John

@Robert Armstrong Sorry for the very late reply...I missed this for some reason. ADE is not compatible with P3Dv6. John

Ok, thanks for the update. And thanks for the kind words. Also, please note that these forums are now closed for new support requests, and will be removed at the end of the year. For any further issues, support id available on the FSUIPC website (fsuipc.com). Please see Regards, John

First, please not that these forums are soon closing and will be unavailable by the end of the year. Please use the new support forums - see This has been reported many, many times... As I tell everyone, for any and all installation and registration issues you should read the provided documentation before posting, namely the Installation and Registration guide. For all new installations, you will need to install the latest combined VC++ redistributables (for both x86 and x64) from Microsoft. Please see the documentation. If you had read this topic you would have also found the same advice, and also in one of the hundreds of others reporting this issue. I am closing this topic now, For any other issue, please use the new support forums. John

The usual value range for an axis is -16384 to +16383. The value range for the axis you are using (as show in the log is -16306 to 3000. So the minimum value (-16306) is ok, resulting in a max thrust (as your axis is reversed) of 88,76%. But the max value (3000) will only result in a minimum thrust value if around 41%. You can try two things: 1. Try calibrating your axis in windows game controllers to see if you can get the full range for the axis values. 2. If you cannot get the full range of values, just calibrate the script to the range of values your axis produces. So with a range of 16306 to 3000., in the lua script change: newValue = (16384 - value) / 327.6 to newValue = (3000 - value) / 193.06

Your log shows only one value being logged from your axis. I have no idea why your axis is not updating offset 66D0 when it is being moved. We need to determine why your axis is not writing its value to that offset. For the time being, can you stop that lua from running - just remove it from you [Auto] or profilw-specific [Auto..Bell UH-1C] section, whichever one you are using. then add offset monitoring to offset 66D0 using the right-hand side of FSUIPC's logging tab, as S32. Then load your aircraft and movr your throttle slowly from idle to full throttle and then back again, exit and attach both your log and ini files. Strange that this was previously working correctly, but just reversed. They are probably fine and look to be using FSUIPC-added controls or custom controls. They looked strange to me as there was no comment generated, but maybe FSUIPC4 does not auto-generate comments for such controls, like it does in other versions. I have not used FSUIPC5 / FSX for many years now and forget the differences in this compared to later versions. John

Offset logging is done via the right-hand side of the FSUIPC logging tab. However, you don't actually need that as the lua script logging is sufficient, as that will log any offsetchanges. Please also remove the comment characters from the other ipc.log statement:

No, you did not set the correct logging., You have activated lua debug logging - I did not request this and it is not needed, please remove this. As I said, you just need to uncomment the 'ipc.log' line entry in the BellUH1Throttle.lua file. You also did not add the offset logging, and the log file shows no movement in the throttle (or the lua debug logging is not showing this). You also forcibly closed the log and started a new one. Please don't do this. Please set the logging as requested and show me those files again. Please exit FSX/FSUIPC before attaching logs, and do not request a new log file.. John

Activate the logging in the lua script (remove comment characters from 'ipc.log' line) and add offset logging for offset 66D0, then test and show me your FSUIPC4.log & FSUIPC4.ini files. For the test, first move the throttle from idle to full and back again, and then exit FSX/FSUIPC4 before attaching the files. John

.Ok, thats interesting. So they are not 'scoped lvars' then.. Thanks for the update. I will make a note of this and take a look at the ProSimSDK.dll when I get time. Thats good to know, thanks. I also saw this on using ProSim with MobiFlight and FSUIPC (which may be useful): https://www.mobiflight.com/en/tutorials/aircraft-guides/prosim737.html John

Please do this. You need to: 1. Correct your aircraft profile names, as advised 2. You have a lot of general button assignments to your Macro Bell_UH1C - shouldn't these be in your .Bell UH1c profile? 3. You seemed to have assigned your axis to update offset 66D0 twice: Why is this? 4. You are starting your BellUH1Throttle lua script in the [Auto] section, so it will run with all aircraft. As this is specific to the Bell UH1, you should start it in a profile specific [Auto.Bell UH1c] section. 5. You seem to have assignments to non-exisiing macros: But it looks like the lua isn't running for some reason. Are you sure it is in your FSUIPC4 installation / modules folder?

These forums will soon be closing, and are already closed for new topics. Please see the following announcement: John / FSUIPC

These forums will soon be closing, and are already closed for new topics. Please see the following announcement: John / FSUIPC