qqwertz

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-v

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. Afte

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

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 insta

I have the same problem. Peter

Just to provide you with more feedback: STB is not working with my P3D3 installation either. When I start STB with P3D running, it immediately kills all traffic. The traffic is even gone after I quit everything and restart P3D without launching STB again. I am using MyTraffic 6 and had a hard time to get it running in P3D. I presume STB changed some configuration files and MyTraffic 6 took that badly, but I am not sure (still trying to get MT6 working again). I don't want to complain at all, I just wanted to let you know about this. Best regards, Peter

An update on this: some clever people on the Aivlasoft forum figured out that certain Aerosoft and Captain Sim fonts cause the issues there. I confirmed that the font issues in STB are also resolved by removing (deleting, or better moving to another folder) the following fonts: AirbusPFD.ttf AirbusPFD2.ttf CDU.ttf CDU_WXR.TTF They are from the Aerosoft A318-321 series and some Captainsim products. It appears that Aerosoft may provide a fix at some point. Peter

Hi Simon, problem (mostly) solved. I hadn't selected any traffic program because I wasn't sure whether I should use MyTraffic (Aerosoft), when I actually use My Traffic 6. After selecting the traffic program the logos were displayed :) Having said that, the ugly font still appears in some places. It looks exactly like this: In STB, this font appears in the "Select Airport" text field in the lower left corner, and under configuration->settings->Fonts. In fact, all fonts in the text fields of this page look like this, and they cannot be changed (the name changes, but not the ug

I have a minor problem with STB P3D 2.5 under Win 10: in the airline column, STB does not display the logo of the airline anymore, but it just writes the name of the airline in a somewhat unusual font (the letters are extremely plain and not spaced evenly). I have seen that for some people Aivlasoft EFB displays the same font on some occasions under Win 10, so my guess is it may be a problem with the new operating system. It's not a big problem (just doesn't look so nice), but is there a way to fix this? Thanks, Peter

Hi Pete, thanks a lot for your reply, which helped me to get on the right track. This morning I completed a long flight without the wheel and everything worked fine. I then installed a driver update for the wheel and was able to calibrate it using FSUIPC. Previously it only showed up under "axis assignment" in FSUIPC, not under "Joystick calibration". I will now do a test flight, hopefully the new driver resolves all issues. If not I will report back. Thanks and best regards, Peter