John Dowson

All updates to each product version are free, and do not require a new purchase, However, different versions of FSUIPC are for specific FS;s and require a specific license. This has been the case for over 20 years, and has been asked and commented on continually over this period. Maybe I should name them differently to avoid this waste of time..... John

I already did - it is this: Maybe the exact location is determined by the installer API I am using, which is NSIS. I don't know how that resolves the input to the exact registry location, but, as O said, just use what you find and that should be sufficient. I suspect that the location I am using will be resolved to the WOW6432Node location dor all installs (as they are all 64-bit), so just use that, Otherwise, fig into the NSIS registry facilities, but I don't see why you just don't use what you see.... John

That is strange... the installer writes and reads from that path... I have just checked my registry and I also have the entries under the WOW6432Node, as you say. However, the installer still reads/writes to that location I specified. Strange. I suspect this is some sort of voodoo that windows uses to split registry entries for 32 and 64-bit applications. Just use whatever works for you. John

This seems very strange...WideClient (and FSUIPC) knows nothing about what type of connection you are using - that is at a much lower level controlled by Windows. Are you using TCP or UDP as the transport protocol? Whatever you are using, maybe try switching to the other protocol to see if that makes a difference. I will look into this further and get back to you, although I doubt there is much I can do about this, except maybe note this strange behavior in the documentation. I have noticed that the Wnd library isn't even mentioned as being available in the current (yet very old!) WideFS documentation... Regards, John

I have not looked at (or used) the WAPI debug lib for a long time. Not even sure its up-to-date. Maybe try checking out the WAPI from github, and build your own debug library and use that - if you have your own local copy of the source, oy may also help in determining what is causing this issue. If you want me to look into this further, let me know and I can maybe take a look next week. John

The installer just writes (and reads) the key as I specified. This is for FSUIPC6 and FSUIPC7 only, which are both 64-bit, so 32-bit OS (Win7) is not supported. Any translation to the registry path must be done by windows. I suggest you just try reading the key as specified. John

Each major version of FSUIPC (FSUIPC3, FSUIPC4, FSUIPC5 & FSUIPC6) requires its own license. This is stated in many places and should be obvious as each product is available to purchase separately. I really don't understand why I have to reply to this same question several times a week - and this is the 2nd time today... John

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. I have moved your post to the correct sub-forum - the one for FSUIPC7 support. Please take care to post in the correct place for support. Have you read the provided Installing and Registering FSUIPC7 document, section Invalid Key Problems? I suspect not....please consult the documentation before requesting support - you will usually find your answer there... So, please consult that document. 99% of all registration issues are due to either the registration details being entered incorrectly or the VC++ redistibutables needing an update. John

For FS9, you used FSUIPC3. FSUIPC4 is a different product and requires a new key, available from SimMarket. If you have already purchased a key for FSUIPC4, your key details will be available from your SimMarket account. John

This seems strange as the throttle axis values look ok.... Do you notice this through actual control? I only compared the VC throttle movement to my actual throttle movement, and that looks okay, i.e. throttle positions match between my physical throttle (saitek X52) and the throttle in the VC. If there is a mismatch between throttle position and amount of throttle actually used, then this would be a question for asobo, so you could ask there... There does seem to be some issues since SU10, see here for example: https://forums.flightsimulator.com/t/problem-throttle-after-last-update-of-the-msfs2020/477252/23 Otherwise, maybe try one of the available mods to see if they make a difference. There are a couple of mods available, but I'm not sure which are now valid an useful since SU10 - see https://forums.flightsimulator.com/t/best-bonanza-mod/451819 https://forums.flightsimulator.com/t/bonanza-g36-turbo-mod-available/298769/164 https://github.com/TheFrett/msfs_g36_project/tree/development - note this hasn't been updated since SU7) For the sensitivity, you could try adding a sensitivity slope (available in the FSUIPC calibration settings), but the slopes we provide are more for increasing/decreasing sensitivity around the initial and extreme ranges, but maybe worth taking a look. Sorry I can't be of more help, John

You can always compress/zip files that are too large to attach directly. Your log shows that the throttle axis is moving through its full range. I have also tested here and it works fine in the G36 with the same assignments, so I don't understand why you are not seeing the full range in the axis movement. Do you have any mods installed for this aircraft, or have you modified any config files? You could try assigning with Send to FS as normal axis and try both Axis Throttle1 Set and Throttle1 Set controls and calibrate in the 3 page (and with No reverse zone checked). Note also that you are using 7.3.12. You cannot calibrate when assigned with Send to FS as normal axis in that version. Please update to the latest version - 7.3.14. John

You can read the installation location from the registry, from InstallDir under HKLM Software\Microsoft\Windows\CurrentVersion\Uninstall\FSUIPC7 But note that lua files don't necessarily go in the installation folder. If the LuaPath ini parameter is set (under [LuaFiles]), that will be used instead, so you would also need to read that. LuaPath can contain a relative or full path specification. John

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.