John Dowson

What you posted (apart from being very difficult to read!) tells me that you don't have any axes assignments in FSUIPC - your [Axes] section is empty and you do not have any [Axes.xxx] profile sections. Are your assigning your axes in FSX? If so, why not try assigning in FSUIPC, then you can try what i have already suggested. If its a boxed version, have you updated with the SP! and SP2 service pack updates? If not, please do this. And please try attaching files, rather than pasting their contents. Just drop them into the box at the bottom of the text entry box. Also, the log file you pasted was pretty pointless. You haven't activated logging for Axes controls, as advised, so it doesn't contain anything useful. I suggest you try disabling controllers in FSX and try to configure your axes in FSUIPC, and we can go from there.... John

The hvar filename must be a substring match to the aircraft name, as reported in the log file, not necessarily the same, John

Did you actually try the solution before posting again? If not, you should have done, and reported problems (in your initial thread) if you had issues. And I also use AFC_Bridge. I am just trying to reduce the number of posts, especially for know issues with known solutions, that are documented as well as having plenty of support questions on the topic. I am finding that I cannot get any new features implemented in FSUIPC7 (and FSUIPC6) at the moment due to number of support requests (and MSFS/P3D updates), most of which are either already addressed in the provided documentation, or have been reported before. I'm sorry but it does get annoying responding to the same questions again and again, when I could be doing something more useful. I am locking this topic now, as I really have nothing more to add to this issue. I will update the documentation to make the solution to this issue clearer... John

I'm sorry, but I cannot advise on the compatibility of such a devices. However, it should work, but you may want PFC (or other such device users) to confirm. I can confirm that the PFChid64.DLL is compatible with both FSUIPC6 and FSUIPC7. John

Got it working....! The issue was that I needed to explicitly set the sim connection to be used by setting the following (WAPI) ini parameter: UseSimConnection=0 (for the WASMClient, this is set in the WASMClient.ini). Setting this for the client will then force it to use the default connection defined in the SimConnect.cfg file (located in the same folder as the application). If this is not done (or if a WAPI client doesn't set the connection using the setSimConfigConnection() method), then the default local connection (-1) is used, which is always local. John

Ok. But please consult the documentation and also search the support forum for similar questions/issues before asking for help. You could have sorted this out yourself using either method. John

I have been trying to get the WASMClient to run on a 2nd/client PC, but with no success. Not sure why. It should be straightforward according to this post: https://www.fsdeveloper.com/forum/threads/simconnect-from-a-remote-computer-to-msfs.448828/ John

The indexed entries under your [Profile.xxx] sections are the substrings used to match the aircraft title, so if the substring is contained any where in the aircraft title, that profile will be used. Have you read the documentation? Also see Appendix 2, as I said. John

I must have said this over 100 times now... FSUIPC7 is a separate executable/process, and in no way should it cause MSFS to CTD. All communication from FSUIPC7 to MSFS goes via the MSFS provided SDK. ALL MSFS CTDs should be reported to Asobo, with the windows event information included. It is impossible for me to trace the cause of an MSFS CTD, that is Asobo's job. John

In your FSUIPC6.ini, in the [General] section, change ShortAircraftNameOk=Yes to ShortAircraftNameOk=Substring You can then use substrings for your aircraft names in your [Profile.xxx] sections. Please see Appendix 2: About the Aircraft Specific option and “ShortAircraftNameOK” in the Advanced User guide. John

Please use the attached key file, valid until 30th November. John FSUIPC6.key

No, it won't. You need to quit FSUIPC manually. This has now been corrected in the attached version via a new ini parameter value. You need to set: DisableMSFSMonitor=Enum John FSUIPC7.exe

For those with this issue, I have added added a different method of determining if MSFS is still running, which can be used by setting: DisableMSFSMonitor=Enum Using this will revert FSUIPC to its previous behavior under windows 10 which will allow FSUIPC7 to exit when MSFS i closed. Available in the attached version, and will be released in the next version. John FSUIPC7.exe

LM are looking into this.

You should still be able to use them but would be trickier to set-up. Usually, for speed, heading and radio frequencies, you would assign to either up/down buttons, or up, fast-up/down, fast-down, for rotaries with two buttons in each direction. It doesn't really make sense to use axes for these - and there are no axes controls for such things. Probably the easiest way to set-up such rotaries would be via a lua script. You can assign the rotary to write its value to a (free for general use) FSUIPC offset. In the lua, which should be auto-started, you can monitor the offset using the event.offset function. When your handling function receives the value, you can then compare it to the previous value seen, and then send the appropriate inc/dec (or fast inc/dec) control depending upon whether it is greater or less than the previous value received, which indicates the direction. John

Yes, shouldn't be an issue, especially if the rotaries operate on buttons (as opposed to axes). I can provide you with a trial license for FUIPC6 if you would like to try it. Of course, if you already have FSUIPC5, you can continue to use that with P3Dv4.5. John

No, it won't. You need to quit FSUIPC manually. Then that will be a separate issue on Windows 11 that will need investigating. If this is the case, please raise a separate topic and provide full information. John

It doesn't, they are completely separate applications. However, as they share a (windows) class name, you cannot run them both at the same time. No, don't touch your FSUIPC6.ini. You need to copy it to your FSUIPC7 installation folder and rename it as FSUIPC7.ini. Also, it is best to remove any aircraft from your profiles, as these, if course, won't be available in MSFS. This should preserve a lot of your settings, but some won't be available and will need to be changed. John

@NomadRider Did you update your EXE.xml as indicated, making sure that you are using the correct Path? And why are you posting in multiple threads for the same issue? Please stick to one thread. I will lock the other one. John

It would be...Why did you remove the line? What did you expect? This new ini parameter was added to circumvent this issue. I do not currently know what is causing this issue for some folks on Windows 11. If you are experiencing this, you need to add this new ini parameter. John

You can use the shortcut anyway/ Once the EXE.xml file is fixed, FSUIPC7 will auto-start with MSFS regardless of how you start it. That will also get auto-started if you add back in the auto-start element for that in your EXE.xml. See this post: John

Why? The shortcut is used to display the splash screen while MSFS is starting. If you don't want that, don't use it However, I have left the start lines in, un-commented, as some people prefer that method of starting FSUIPC7, as it gives them the ability to start MSFS without FSUIPC7 (using the MSFS icon), or to start with FSUIPC7 using the desktop shortcut (with those start lines uncommented). Note also, the auto-start is a component that you select (or not) during installation. The shortcut is created after the components have been installed, at the end of the installation process, if selected. I could probably improve the documentation on the purpose of the shortcut though... John

I believe this is a known problem and needs to be addressed by Asobo. See https://forums.flightsimulator.com/t/have-they-fixed-the-bush-trips-in-su-6/463753/112 John

Ok. Best to try without this first, and only add if you get issues. John

Windows 11 reporting Windows 10 seems to be a known issue. See https://techcommunity.microsoft.com/t5/report-an-issue/registry-value-for-windows-11-shows-as-windows-10-after-upgrade/m-p/2832683 John