John Dowson

As does setting the Log -> Lua Plugins option. Why is the saitek script filling the log if you are logging your luas in separate files? If there is a separate script for polling your Saitek devices, this should be logged in a separate script. You can also start some scripts in debug mode, using the LuaDebug control. There is no ips.runluaDebug function. Otherwise, you could include the ipcDebug.lua in the scripts you want to debug. This is included in the provided lua example scripts (in your documents folder. If you take a look at that, you can see how the lua debug logging works - by setting hooks. You could also use this and add your own functions to both set and clear the hooks, and so enable/disable the debug level logging. I am busy the next few days but I can look into this further next week if needed.

Ok, so they work - that is interesting, and rather surprising. The SimConnect_CameraSetRelative6DOF function is no longer documented in MSFS, so shouldn't be available, although it does still exist. It was previously documented as "No error, No response" (i.e. not working), not sure when it was removed. i won't be making any changes to this, except maybe in the documentation. John

Also, please see the following for the simvars that can be used to read (and update/write) the camera state: https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Camera_Variables.htm You can add these to free FSUIPC offsets it you want to access them. John

No, sorry - there is currently no camera interface in the MSFS SDK and the 6D0F functions are also not available - those offsets shouldn't be used. I will mark them as such. Ok, that is interesting - I will check this and mark it as available.. John

Do you mean for this to: 1. turn off lua debug/trace logging, or 2. prevent the logging of ipc.log statements? If 1, then I don't think this is a good idea as all lua activity, including the polling, should be logged. If you want to control the logging in the script itself, you can use ipc.control with one of the logging settings controls - from the Advanced User guide: if 2, I don't see that much need either, although maybe useful to turn off logging statements added for debugging purposes when developing a script, but then you could also remove or comment these out when done. So I don't think this would really add much. John

Here (and attached) is a sample lua script for the GF-T8 lights for the Cessna 172. I have assigned the switches in the same order as in the aircraft - beacon, landing, taxi, nav and strobe. The current light switches positions for the C172 are held in lvars, so I am using the lua event.Lvar function to pick-up the switch position and set the light accordingly. Note the call to gfd.SetBright - this is necessary to set the leds to full brightness (when on). The logging statements have been commented-out - you can re-enable these for testing purposes, if needed. To use this script, make sure that it is running by adding it to your FSUIPC7.ini's [Auto] or (better) profile-specific [Auto.xxx] section, e.g. If you need help in modifying this for another aircraft, let me know which aircraft you are using, as well as your switch assignments, and I can take a look. John GFLeds.lua

You didn't set the custom logging for auto-save, as advised... However, looking at your files I don't think that it is FSUIPC that is initiating the panel state save. The file being saved is called ACARS Flight.sav - do you have an acars system also running, possibly an FSUIPC client application? If so, please check this. That file name must be coming from somewhere, and its not FSUIPC... John

Pete retired several years ago. Please see the following parameters on the OOM warnings (from the Advanced User guide) - you can adjust to your needs: John

If AutoSave is not checked, then it should be disabled... Can you please set a Log->Custom value of x4 - this will then log all auto-save activity. Then show me / attach both your FSUIPC7.ini and FSUIPC7.log files from when you experience this issue. Make sure that you have exited FSUIPC7 before attaching the files.

Some aircraft do constantly emit events... With the FBW A320, I see a constant stream of axis left/right brake set events, as well as steering set events. Just turn off logging dor Axes Controls if you don'y want them logged, or you can use the DontLogThese ini parameter to disable logging of specific events, best used in your profile section as the events emitted are different for each aircraft. This event logging should not significantly affect performance. And images are difficult to read properly - next time please attach your FSUIPC7.log file rather than a screenshot. John

I can also provide an example script for one switch (e.g. a light) if you like, and you can try that and adapt and add your other switches. May take a few days before I get time to do this though,,,, I will post an example script here... John

👍😎

This issue is usually do to the axes being registered as digital on/off axis. See the following FAQ entry on how to resolve this: John

👍 Yes - if you remove the numbered entries they will be added back - they are needed to map the joyid numbers to the letters, based upon the GUIFs. Glad its all now working! Cheers, John

It can, but not via the driver, and for reasons I have stated several times now.

No, they are needed. You can delete the <<MISSING JOYSTICK>> line though, as this is there as you referenced a 'j' device.

You only have throttles 3 and 4 calibrated in FSUIPC, not 1 and 2: Please calibrate all 4 throttles. And set or clear the No Reverse Zone checkbox, as appropriate for both throttles - you cannot have this different for each throttle device., And if you want the full range of the throttle (i.e. -16283 to +16383), then you need to set UseAxisControlsForNRZ=Yes in your [JoystickCalibration.747] section. Please see the Advanced User guide on this setting, As you are using 2 throttles on one device and 2 on another, it may be difficult to calibrate for both, especially if one device has a reverse zone (or reverse button trigger) and the other not. You need to assign/calibrate to what works for you. Also, I recommend you change: to John

There are various ways to use and configure GF modules, If using FSUIPC, for all flight simulators that I support, you only need the driver that I supply, nothing else - and anything else installed can possibly interact with the FSUIPC driver, causing issues. It may be possible to use the GF drivers or software with FSUIPC, but if any issues arise I cannot help unless such software is first removed - I cannot support other peoples software, I have never used or tried the GF drivers. Maybe you were using that in P3D, with or without the FSUIPC driver. I can only give you information on how to use the software I provide, and the FSUIPC GF driver doesn't, and never has, controlled led lights or displays. You need to use FSUIPC's lua interface for these. John

Why would you even consider doing that, as it is those entries that were causing your problem? You don't want to re-introduce the same issue, which wasn't actually causing any functional problems, that you have gone at lengths to resolve... John

$APPDATA and %AppData% are the same thing - just different symbols used by the software to designate a windows environment variable. If AppData exists and is correct, I have no idea why the installer can't see this file. Please remove what you added, and attach your InstallFSUIPC7.log file. If the installer cannot read that file, for whatever reason, you will just have to manually install the WASM module and manually set-up the auto-start - that is all this is needed for. John

No, that is the default. I am locking this topic now as SU12 has been released.

Have you ran MSFS at least once before trying to install FSUIPC7? For steam installs, the UserCfg.opt file should be in the following location: $APPDATA\Microsoft Flight Simulator\UserCfg.opt where $APPDATA (usually) resolves to C:\Users\<your username>\AppData\Roaming If that cannot be found, the installer presumes that you have an MS Store version. So, as I said before, check where your UserCfg.opt file is located, and check that $APPDATA is set correctly. John

Note also that such issues may be dur to a poor com cable/adaptor used - see John

Why? The version you are trying to install is v7.2.16 - the latest and only supported version is 7.3.20. Please download and install the latest version, available from fsuipc.com. Are you using the MS tore version of MSFS? If so, the UserCfg.opt file should be in one of the following locations: $LOCALAPPDATA\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt $LOCALAPPDATA\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\UserCfg.opt If you get the same issue, determine where your UserCfg.opt is located, and check that the windows environment variable $LOCALAPPDATA is set correctly. See https://www.howtogeek.com/787217/how-to-edit-environment-variables-on-windows-10-or-11/. John

What does this mean - do you actually have a question? The message is self-explanatory... Any issues, please explain what they are and attach your InstallFSUIPC7.log file. John