John Dowson

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

Ok, yes - just checked my log file and it also says Windows 10, event though i am on 11! I will look into this. I cannot see that image you attached - What does it say? Are you sure that this is coming from FSUIPC, and not an FSUIPC client? I cannot see a message 'IPC request contains bad data' anywhere in FSUIPC7. I see you are also using an unregistered version. What FSUIPC7 clients are you using? Have they been updated for FSUIPC7/MSFS? If the message is from a client, you need to contact the support for that client. John

Found a cut-and-paste error in the locking, which resulted in a lock being obtained but not released. This is corrected in the attached version. Sorry about that. John FSUIPC7.exe

Did you try with those alternative dlls I posted? I think not as they haven't been downloaded. Can you please try them and report back. It would be helpful to know why the Mode C button in VPilot isn't working with FSUIPC installed. As VPilot doesn't use FSUIPC, I really cannot understand this issue. Locating the version where this problem first occurred would help, which is why I would like you to try with the dlls I posted. John

No, the only changes in that last version were relates to the WAPI (lvar/hvar access interface). Both of the hangs are due to the same reason, which I suspect is due to multiple threads holding/waiting for locks (i.e. one thread has a lock on X, waiting for a lock on Y, while the other has a lock on Y, waiting for a lock on X) during shutdown, or the WAPI thread os trying to exit while a lock is held but hasn't been released. I will revise the locking code I recently added (and add more logging to try and track this down). Are you using the additional ini parameter I added: KillLuasOnSimStop=Yes ? John

Then please follow that post and post there if any issues. I will close this topic. John

That is the old method of starting FSUIPC7 with MSFS. This was replaced (around a year ago) with the prescribed method of using the EXE.xml file. A few other add-ons are known to corrupt this file, and if the file is corrupted then the FSUIPC installer cannot update this file. Check your InstallFSUIPC7.logg file - you should see errors about the EXE.xml file there if this is the case. This issue is covered in the provided README.txt file (as well as in many other support requests!) under Problems running FSUIPC7: John

Some programs don't close properly with the close option, so try the KILL option instead: Run1=KILL,C:\Program Files\Navigraph\Simlink\NavigraphSimlink.exe or you can use both: Run1=CLOSE,KILL,C:\Program Files\Navigraph\Simlink\NavigraphSimlink.exe John