John Dowson

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

Please try the attached version, 7.3.21b. To use/activate this feature, you need to add the following to the [General] section of your FSUIPC7.ini file: LogLuaNew=Yes I don't think I will add a UI option for this, as I doubt it will be used much - lua logging has worked this way for many years and nobody has requested this before. Cheers, John FSUIPC7.exe

Can you please attach your FSUIPC ini file so that I can see your assignments & calibration. This sounds like you have the No Reverse Zone box checked, but if that is the case then this should really apply to all throttles - it isn't which is strange. Your ini file will tell me what is happening.... John

Yes - you are not using the joyletters facility (you should!), and the j and b letters are just placeholders for the joystick id/letter and button number Change to You should also switch to using JoyLetters. Just change to AutoAssignLetters=Yes This will prevent issues if your joystick ids change. John

Then something else, e.g. the GoFlight Interface Tool, that must be controlling the lights - the driver I provide does not do this, for FSX, P3D or MSFS. As I said, the driver does not know what the switch is assigned to, and cannot set the light to the correct state for the assignment. If you still have P3D installed, please check this. The GF driver is the same for P3Dv4, P3Dv5 and MSFS. John

This would be a huge amount of work and complicate the UI, as well as the ini file format, for little benefit - I will not be adding this. I could add a menu option to Reload Presets so that any changes to the events.txt and myevents.txt are made available for assignment without restarting FSUIPC7. John

I have checked in P3D and it is the same - are you sure that you weren't using a lua script to handle the lights in P3D? If so, you can probably use the same scripts for MSFS. The lights aren't controlled by the driver as this would just indicate the switch position (up or down). What you want is for the light to indicate is if the function assigned to the switch is on or off, so to do this you have to use an offset (or maybe an lvar) to determine if the light should be on or not, and so this depends on what the switch is assigned to. There are quite a few support requests on getting the GF indicator lights operational - for example, see the following: But if you are setting/assigning your GF switches in MSFS the same as in P3D, the lua scripts you used for P3D should also work (although can depend on aircraft) in MSFS. John

Ok. Also, if you don't need repeat, which you don't if these buttons are rotary buttons, then you should use 'CP' and not 'CR'. If these are rotaries, then there are also other ways do achieve fast/slow assignments. - see John