John Dowson

Can you show me your FSUIPC7.ini and FSUIPC7.log files please, the latter generated with logging for Axes Controls activated/checked. load the G36 and move the throttle through its full range and back to idle, then exit FSUIPC7 before attaching the files. Thanks, John

Glad to hear it - thanks for the update. John

If your key does not validate, it is either because you entered the details incorrectly or the required VC++ redistributables are missing. As you re-installed windows 11, it is most probably the latter. So, first try re-installing the VC++ redistributables,. Otherwise you can try manually creating your key file. Please see the provided Installing and Registering FSUIPC7 document, section Invalid Key Problems. John

The logs you attached are from your previous installation, v7.3.10. The message doesn't make much sense - it is saying it can't find the file that you double-clicked to run... You also do not need to run the installer as administrator - it will automatically request admin privileges. Can you download the latest version (7.3.14), unzip the file and try again - running without admin privileges. If you get the same problem, then it is a problem with your windows installation. Check/verify your windows installation and maybe also your disk integrity. You could also try opening a command prompt window, change working directory to the installation folder, and then run the installer from there.

Yes, sorry about that. Correct file now available.

The license has been renewed, now valid until 29th November 2022 (inclusive). John

Note also that such strange issues can occur if you install by running the installer from withing the zip file, rather than extracting it first. So please download the latest version, extract/unzip the file, then run the installer to re-install. Show me you log files (InstallFSUIPC7.log and FSUIPC7.log) if you still get issues. John

I don't know much about WidevieW, but I thought thar was for setting up multiple monitors on multiple PC's for the scenery view. Maybe try asking on the WidevieW support forums. John

I don't have access to that link. However, it is not important - better if you could respond to my previous comment. If there is no FSUIPC7.log file, please show me your InstallFSUIPC7.log file. Also check to see if there is anything in the windows event viewer. What was the previous version that you were using? Are you using any anti-virus software? If so, maybe check that to see if it is blocking FSUIPC7 somehow. Note also that the latest version is 7.3.13. John

There is only one changed flag per offset, and when the first event.offset function is called the flag is reset. So the second, and subsequent, event.offset calls will only be made if the flag is changed again. This is why you see a descending number of calls for each event.offset on the same offset. You should only use one event.offset call for each offset. Yes, that is one way to change this. Or just have one event.offset call and function (for each offset), and call the other functions from the one event.offset handling function. John

Ok, but that is a shame as you cannot now verify the fix. I did some basic testing but I will test further before I release this. John

That is a question for the FSUIPC Client DLL for .Net sub-forum. John

I have no idea as to why you would want to do that, but no, that is not possible.

0x66C0 is free to use. What do you mean by 'but that is not working'?

Changing the plane can result in the profile not being used. However, sounds like the FSUIPC7.ini file isn't being saved. Can you please check that you have not installed in a windows protected folder, such as under Documents or Program Files. If so, please re-install into a different and non-windows protected location. So FSUIPC7 is crashing? Please check the installation location first, but if your problems persist please attach your FSUIPC7.ini and FSUIPC7.log files. John

And? Just ignore it. There are many issues with the MSFS logging console. See https://forums.flightsimulator.com/t/console-log-message-issue-repeated-log-messages-make-console-unusable John

The currently available trial license is still valid - at least until the end of today. I will provide a new trial license on Tuesday the 1st November.

Your ini file (extract) is rather strange, as lua assignments such as 64=N81,9,L54:R,0 -{lshift+Q: Press=Lua DC6_RPM_24 }- should really be written as: 64=N81,9,CL54:R,0 -{lshift+Q: Press=Lua DC6_RPM_24 }- i.e. with a C before the L. I don't know why the 'C' is missing from your assignments... However, I have corrected for the lua/preset confusion for luas with an index of 64 or greater in the attached version if you would like to try it. This should automatically re-write your ini correctly. Any issues, please attach your full FSUIPC7.ini file. Sorry about this - I am surprised that this hasn't been reported previously... Regards, John FSUIPC7.exe

Correct No. Edit the ini file when FSUIPC7 isn't running, or if it is running, only edit when the axes assignment panel is open (as you are editing an axis calibration assignment), and once you have made the changes, click the Reload button to reload the changes. John

Opentrack (or Smoothtrack) maybe using FSUIPC, but I don't know anything about this software and cannot really advise, especially when using such an old version of FSUIPC. Not helpful to me, as I don't know that software, so not much point posting screenshots here. If you post anything for me to look at, it should be your FSUIPC3.ini files so I can see what, if anything, is assigned to control the view. You can also try activating logging for Axes Controls, and see if what view pan controls are logged when you use the headtracker. I would check this, and the Smoothtrack/Opentrack support forums. Sorry, but - as I said, I just don't think I can help you with this. John

Could you please attach your full FSUIPC7.ini file. What was your previous version? There has been no change in this area for a while... It looks like the control numbers I am using for lua files are clashing with the ones for presets (when the lua file number is > 63), which is a bit worrying... I will check this (tomorrow), but please first attach your ini file. Thanks, John

Sorry but I don't think I can help you with this. Does FSUIPC3 have anything to do with this? i.e. is the head tracker seen and assigned in FSUIPC3? I only have experience with TrackIR and that interfaces directly with the FS, and so FSUIPC is not involved. I suspect it to be the same in your set-up, and the issue is most probably related to the Smoothtrack software - have you tried their support? Why? I would assume that it is sending its output to what you have selected, namely FS2002/2004 John

That is strange...it shouldn't matter whether FSUIPC is started before MSFS, auto-started by MSFS, or manually started after MSFS has started. Could you maybe check this again (i.e. use auto-start) to see if you get the same issue. Thanks, John

Can you please attach your FSUIPC7.ini and FSUIPC7.log files and I will take a look. Do you see anything registered in that window (i.e. joystick number or letter and axis letter)? If so, please let me know what is registered. John

No problem.