qqwertz

That is probably it. I have a RCAF livery for exactly these two airplanes, and the 738 livery from flightsim.to only had texture files, no proper directory structure. I just called it RCAF, and that will likely interfere with my KingAir. I'll try it out and will let you know if the problem persists. Thanks a lot, John. Peter

Two days ago, I installed the PMDG 738 in MSFS (all latest software, FSUIPC7 7.3.19 on Windows 11). I now wanted, for the first time since that installation, make a flight with a different airplane (Kingair 350 analog by Blacksquare), which used to work fine until now. However, I can do what I want, FSUIPC always assigns the B738 profile to this airplane. I does not so this at least for several other airplanes. I tried editing the FSUIPC.ini file (see attachment) and removed any reference to the KingAir, and deleted its profile. I moved the new 738 entries to a different location, so that it is not the last entry in FSUIPC7. I restarted MSFS and my computer, all in vain. How can I get the KingAir to work again? Thanks for any help, Peter FSUIPC7.ini

Hello John, many thanks for your quick reply, and apologies for my belated response - life got in the way. >> Also check that the buttons/switches you are using are not also assigned in MSFS. I think that was exactly the problem. I cannot tell for sure since SU12 was installed today, but the switches were also assigned to flaps increase/decrease in the simulator. After I deleted that, flaps worked fine with FSUIPC. The airplanes where I encountered problems only have three flap positions. Hence, if both FSUIPC and the simulator increase flaps, I would go from up to down in one step. Thanks a lot for your help, which likely has resolved my issues. I will report back in case I encounter more difficulties. Cheers, Peter

I have a strange problem: I have assigned flaps to one of the switches on my yoke. The assignment is done differently for different airplanes. Sometimes I map the switches as a key press (F6/F7), sometimes as an FS control (flap incr/decr). It is always mapped to an incremental increase or decrease, never to flaps full up or full down. For the last few weeks, however, flaps go only to the full down or full up position, regardless how I made the assignment. Even worse, when I fly a plane without a profile-specific assignment, FSUIPC appears to block any change in flaps. I can then neither operate the flaps using my yoke, nor in the VC, nor via keyboard. I discovered that the problem is resolved after I open the button/switches assignment page and click on "reload all buttons". After that, flaps work with incremental increase again. However, I have to do that every time I start my simulator. I only understood that this is a FSUIPC problem now, but in hindsight I can tell that this started some time during the last 2-3 weeks. Any help would be greatly appreciated. Thanks, Peter

Hello John, thanks a lot, that general advice to use logging did the trick. Helicopter controls seem to be a bit special in the sim, but I got it to work as I wanted 🙂 Cheers, Peter

I am trying to assign an axis for throttle in the new default helicopters in MSFS, but I cannot get it to work. I am using the latest version of FSUIPC7, and I use "helicopter throttle axis" in FSUIPC7. The axis of my TQ6+ is found and assigned in FSUIPC7, but it just doesn't do anything in the game. Almost all other axes assignments with FSUIPC work just fine. Only the condition lever in turboprops doesn't work either (since SU10, I think), but I was OK with setting that in the VC. The throttle is a different matter, though. Thanks for any help you may offer, Peter

Thanks so much for your continued support of the flightsim community. I will get FSUIPC5 as soon as you will release it. Peter

I finally got it to work by deleting FSUIPC.ini and removing all my FSUIPC settings. I am not sure if I can use FSUIPC axis assignments with other planes, so far all planes that I tested worked with the new approach that does not involve FSUIPC. I will report if I run into a problem with other planes because of this change. Peter

I am now certain that on my system the problems are caused by the new PMDG 747: - After a flight with the 747, P3D will not restart unless I reinstall FSUIPC. If I do, everything works (mostly, see below) fine. - If I do not use the 747, then P3D is able to restart without reinstalling FSUIPC - PMDG discourages the use of FSUIPC for calibrating yokes etc in the manual - There is a bug in the autopilot of the 747 when FSUIPC is used. The AP always disconnects after a few seconds unless a certain option in the PMDG setup is changed, see http://www.avsim.com/topic/503044-747-v3-autopilot-issue/ - Engine performance is ridiculously bad with FSUIPC enabled: http://www.avsim.com/topic/503546-flight-dynamicsweight-and-balance-issue/ Peter

I should have made one more test :) P3D didn't start again, but did so after reinstalling FSUIPC. It seems that for now I have to reinstall it every time before launching P3D Peter

Hello Pete, It looks like you are on the right track regarding PMDG planes. I was able to resolve the problem doing the following. - I uninstalled the new PMDG 747. This didn't change anything at first - I disabled all dll modules in dll.xml . P3D then started normally - I re-enabled first FSUIPC and then subsequently all other modules. P3D was able to get to the start-up screen after each change. - I then launched the default flight with success. Except that the FSUIPC menu and functionalities were gone (with the module being enabled) -I re-installed FSUIPC. After that it was working fine again. - I re-installed the 747. When I only started a flight with it there were no problems after restarting, but after I initialized the plane to cold & dark and restarted P3D, the problem reappeared. - After that, I set SavePreviousFlight=No in FSUIPC.ini, but it didn't help. By the way, RAAS remained disabled during these procedures. - Re-installing FSUIPC fixed the problem. This long list is simply an accountof my trial and error session. I would guess the essential elements are to re-install FSUIPC and to add SavePreviousFlight=No in FSUIPC.ini . I will let you know if the issue occurs again. Thanks and best regards, Peter

Hello Pete, sorry, I forgot to mention that; I have read the posts about restarting P3D and tried to eliminate this possibility. - I restarted my computer and did nothing but starting P3D, but even then I get the same problem. -I do not have the files "Previous Flight.wx" and "Previous Flight.fxml" in C:\Users\username\Documents\Prepar3D v3 Files\ (and that directory is the one used by P3D for the error log), nor anywhere else, possibly because I am using AS16. I also tried to delete the AS16 weather files (activeflightplanwx.txt, current_wx_snapshot.txt, LastDownloaded.Wx), but it had no effect. - I always launch P3D with the default airplane (F35) at the default airport, with the start-up screen enabled. - I am using the registered version of FSUIPC under Win 10. Thanks for looking into this, Peter

Same problem here. With FSUIPC enabled, P3D 3.4 HF3 hangs (the startup window closes but the program is still running in the task manager and consuming CPU resources). With FSUIPC disabled iP3D starts just fine. I have installed the most recent versions of FSUIPC, P3D and Simconnect. I don't use RAAS and I didn't find "Previous Flight.wx" and "Previous Flight.fxml" anywhere (except very old ones in my FSX folders). Sometimes the Windows Event Viewer shows an error message, sometimes it shows nothing. Peter

Hi Thomas, thanks a lot for your help. The last 2-3 attempts on my system were successful, so I will wait with deleting the weather stations until the problem occurs again (and then I would send the logs). I did check the logs and they refer to 4.959. Thanks, Peter

I have the same problem: The latest version of P3D 3.4 together with the latest (registered) version of FSUIPC will result in the simulator not getting to the initial screen where you can elect vehicles, flight plans etc. Here are a few more details. - I have added ManualLoad = True to the dll.xml file. P3D 3.4 works fine if I do not load FSUIPC, but it normally (not always) "crashes" if I do. - P3D is not really closing. It is still visible in the Windows Task manager and draws significant system resources (CPU load about 25%). I have to stop P3D manually there. - A fresh install of FSUIPC using the latest installer usually helps for the first 1-2 runs. After that, P3D fails to launch again. - Here is my Windows event viewer log: Faulting application name: Prepar3D.exe, version: 3.4.18.19475, time stamp: 0x5851bfd2 Faulting module name: FSUIPC4.dll_unloaded, version: 4.9.5.8, time stamp: 0x5857240f Exception code: 0xc0000005 Fault offset: 0x00067797 Faulting process id: 0x3168 Faulting application start time: 0x01d25ef2fd44e6d1 Faulting application path: D:\P3D-3.0\Prepar3D.exe Faulting module path: FSUIPC4.dll Report Id: 457a7181-a525-44aa-941d-d2f3059eefa0 Faulting package full name: Faulting package-relative application ID: - You may notice that it states version 4.9.5.8, and this may be at the heart of the problem. I have re-downloaded the 4.9.5.9 installer multiple times, and it does contain the list of 4.9.5.9 changes. However, it appears to install version 4.9.5.8 of FSUIPC.dll Thanks and best regards, Peter