John Dowson

First, please use the FSUIPC7 / MSFS support sub-forum for all issues/questions with FSUIPC7 and not the main support forum which is for all other versions/products. I have moved your post. Yes. The main cause of such stuttering is excessive logging by MSFS. Can you check the MSFS logging console to see what messages are logged, and if they are being logged at a very fast rate (you will need to activate Developer mode in MSFS to see the logging console). Does this occur with all aircraft or only a selection (please try both simpler/ GA aircraft and more complex ones)? Excessive logging can be caused by FSUIPC requesting variables from the new fuel or electrical system in an aircraft that does not use them. FSUIPC does not do this by default, and so if this is the cause it is due to a simvar being requested via the myOffsets.txt file. So, if using that file, check to see if it has any such simvars added and if so you should only use that file when flying an aircraft that uses the new systems. Please attach your FSUIPC7.log and FSUIPC7.ini files, as well as your FSUIPC_WASM.log file. Please only attach files once FSUIPC7 has exited, and only attach the WASM log file after exiting MSFS.

I am not sure I understand this - how is your controller assigned, in FSUIPC or elsewhere? The software cannot send such events to FSUIPC and all events are received from the FS. So I suspect that it is the Elite software that is sending the events to the FS, and then FSUIPC is receiving them for logging purposes and possibly for calibration. It should be possible to calibrate such events when not assigned in FSUIPC or when assigned but not with 'Send direct to FSUIPC Calibration', as long as the ini parameter AllowSendToFSCalibration is not set to No. If you cannot see any movement in the elevator trim calibration tab, could you please activate logging for Axes Controls, load your aircraft, move the assigned elevator trim axis through its full range and back again, exit FSUIPC7 and show me / attach your FSUIPC7.log and FSUIPC7.ini files. John

I have updated the display vals.lua script to use the Wnd library in the attached version. John display_valsW.lua

If you are having issues, please attach your log files (FSUIPC_WASM.log and FSUIPC7.log, with appropriate logging activated) and I will take a look.

What do you mean? You should be able to control this aircraft already, either via standard controls, lvars or presets - there are currently 386 presets available for this aircraft. There is currently no access to the iFly SDK - I will look into adding these (as read-only offsets) at some point when time permits - see John

No - as I said, the folder for saved flights is determined by the FS.

No - the folder for saved flights is determined by the FS. FSUIPC delegates the flight save/load operations to simconnect API. Unfortunately in MSFS2020 (and MSFS2024) the flight save function is still not working 100%, and is still documented as "NOTE: The current status of this function is NO ERROR, NO RESPONSE", which is Asobo's way of saying that this function still isn't 100% reliable. So the flight load/save functionality needs to be used with caution, and seems to work better in some aircraft and not in others. There is nothing I can do about this in FSUIPC and this needs to be fixed/addressed by Asobo. John

This has been on my To-Do list for quite some time already - I will look into adding such functionality when time permits. John

What does this mean? Have you consulted the documentation? No point posting such a cryptic message...please explain your issue more clearly, and make sure you have read the documentation,

It seems that nil is no longer being returned when the lvar doesn't exist. I have corrected this now in the attached version, so your script should work with this version as it is: FSUIPC7.exe John

Ok, I will leave it as is in the version I posted above.

Those look to be LINDA macro files that are using mouse macros. I don't have the FSLabs for P3D so can't really advise, Why don't you just try and define your own macros for these functions? See the section on Mouse Macros in the User Guide. Do any if the standard controls work? What do you see logged when you operate these functions in the VC? If a control is logged, try assigning to that.

I asked for WAPI debug logging (Log -> WAPI -> Debug) mot WASM debug logging, but it doesn't matter. You should rename your script - raas_power_switch contains 17 characters, and there is a limit of 16 chars for lua script names. This can cause issues. But the problem is this: It seems that nil is no longer being returned when the lvar doesn't exist. I have no idea why or when this stopped working - I will investigate this next week, For the time being, change that to: Are you sure that lvar name is correct, and its not FS2CREW_RAASPRO_MASTER_SWITCH? John

What do you mean? What happens when you run the uninstaller, either directly or from the windows app management panel? Why do you think this? FSUIPC should not interfere with any other add-on.

The default hot key to open the FSUIPC7 main window is Alt+F.

Please see the README.txt and the Installation and Registration guide for all registration issues. John

What does this mean? Is the problem fixed, or are you asking/telling me to fix this? I still don't understand your issue - did you ask FSLabs support?

Yes - I left it in the standard units provided. I could convert to m\s or ft\min if thats more useful...but the units shouldn't matter as long as you know what they are/are documented. As I am adding this as a new value, I can add in any units.

Both should work, but if you are adding to an offset as UB (Unsigned Byte), then you should use ipc.writeUB, and not ipc.writeUD. Your lua script doesn;t make much sense. Why are you reding the value of offset A000, when that would be passed into the event function, e.g. function ToggleRAASPower(offset, value) ... end And why are you writing to update the lvar, when that event function is being called on the lvar change? With that script running, the lvar will just always stay at the same value, either 0 or 1. But I think your issue is that the lvar is still not being added to the offset. Are you still seeing a message like this: 5437 **** Lvar 'FS2CEW_RAASPRO_MASTER_SWITCH' not found: cannot add to offset 0xA010 ? Can you please set WAPI Debug level logging, as well as logging for Lua Plugins, and show me your FSUIPC7.log file as well as the lua script again if modified..

I don't know if XPUIPC writes the version number to offset 0x3308 or what that version number is if it does - try logging it. You could also check offset 0x3304 (FSUIPC version number) or 0x3124 (FS version).

You could also try offset 0x3BF8 which holds the FLAPS NUM HANDLE POSITIONS simvar, and maybe 0x0BFC (FLAPS HANDLE INDEX) for the current position, Offsets 0x0BE0 and 0x0BE4 are the trailing edge flaps. There are separate offsets for leading/trailing (see 0x30E0-0x30FE), but you can't really use these values to determine the flaps detent: It doesn’t correspond to the equally spaced notches used for the control lever. You could also try offset 0x0BDC (FLAPS HANDLE PERCENT): Flaps control, 0=up, 16383=full. The “notches” for different aircraft are spaced equally across this range: calculate the increment by 16383/(number of positions-1), ignoring fractions. See also offset 3BFA below.

I have added the PLANE TOUCHDOWN NORMAL VELOCITY simvar to offset 0x0654 (as a 4-byte float, in Ft/s) in the attached version if you would like to try this. John FSUIPC7.exe

Please attach your FSUIPC7.ini file. You may need to calibrate with no reverse zone... If you cannot reverse via calibration, you can use FSUIPCs axis scaling facility - see the section Additional parameters to scale input axis values on page 42 of the Advanced User guide. Basically you need to add a scaling factor of ',*-1' to the axis assignment line in the FSUIPC7.ini file. John

Are you sure that was the script that was running? The line numbers in the log don't match that script... There are errors in the ipc.log statements in that script - you need to provide one string argument and cannot provide separate arguments. Try the attached and show me the log again if any errors. John raas_power_switch.lua

That is an error on line 50 of the lua script - please attach that script. No - the offset will be populated when the lvar becomes available,