Dirk98

Patrick, it is a known fact that GF doesn't work well with USB3. That's why before building my new system I researched the latest mobos for enough internal USB2.0 connectors. ASRock mobos usually still have 3 of them (internal connector can accommodate x2 USB ext.). So I added 3 external usb2.0 boards and used them for connecting hubs with my GF gear. Dirk.

Pete, which file exactly do you want me post? Which is p3d crash log file? Where is it? Thanks, Dirk.

Now, this is how I've fixed this crash at first P3D launch: 1. I ran SimConnect.msi installers from the redist folder 2. I removed SimConnectP3D3.dll folder (ver. 3.0.0.13948 from FSUIPC4.95 install) 3. I deleted *.wx files from Documents\Prepar3D v3 Files\ folder 4. I switched off wxstationlist.bin file in Weather folder Only after that P3D launches seamless on the the first run after pc reboot. Do I still need SimConnectP3D3.dll and wxstationlist.binfiles? Thanks, Dirk.

Sorry Pete, I think I misinterpeted your post, you rather pointed to the old version of Prepar3D.exe that you found in Beavis's log, didn't you? Dirk.

If I run all SimConnect.msi files in redist folder, do I need SimconnectP3D3.dll in Modules folder at all? Thanks,

Luke, I renamed wxstationlist.bin to wxstationlist.bin.off and removed all *.wx files in Documents\Prepar3D v3 Files folder. Rebooted my PC and launched P3D - still the same problem. My FSUIPC version is 4.95 and Prepar3D.exe is: Prepar3D.exe version = 3.2.3.16769 Thanks, Dirk. PS: Don't I need wxstationlist.bin at all? Does it ever get regenerated?

I'm having a similar problem on the first launch of P3D with the freshly installed FSUIPC after each reboot of my PC as posted in this thread: http://forum.simflight.com/topic/81463-fsuipc495-crashes-p3dv32/ Pete, please note the latest version of Prepar3D.exe version = 3.2.3.16769 not "Prepar3D.exe version = 3.0.10.14945" And it's been there since 16-03-07. Can that be the key to my problem posted in my thread? Thanks, Dirk.

I'm having a weird problem with FSUIPC4.95 installation crashing my vanilla P3Dv3.2 in Win10 x64 on each first launch of P3D. It took me 4 days of research, multiple uninstalls and Acronis recover to pin this problem down to FSUIPC4.95 install. I would never imagine FSUIPC could to that to me. )) So, each time when I reboot my pc and launch P3D first time I hear some Win10 system chimes followed by Errpr: "Prepar3D exe has stopped working". I close the program and launch P3D again. Second launch produces only the chimes but no Errors and all seems to work OK after that, no matter how many launches I make. Soon as I reboot - the story repeats the same. Very weird. If I edit FSUIPC entry in DLL.XML to Disabled>True< the problem is gone, no chimes no messages. Please help. Thanks, Dirk.

Why so lean?

Burkhard, when does MyAirportsshort.dat file get created first time? With the installation of MTX6 before launching it for the first time? Thanks,

What is "UT2 tool", do you mean UltimateTraffic2.exe? Thanks,

AIFP is an important tool, so thank you for bringing this to light. Sabre.

I have this problem in UK2000's Heathrow v3 on Rwy 09L but on 27R AI always lands ok.

My OS is set to US English, including the DOT as a decimal separator. So I still need your help to sort out the problem with "Failed to read MyAirportsshort.dat file" at the launch of MyTraffic Interactive. Thanks,

Do we still need to use quotes for MyTraffic path in FSX.cfg? Now it is: "F:\MyTraffic Professional\MyTraffic\Aircraft" I'm curious because I tried with qoutes and without quotes and the traffic seems ok in both cases. Please advise, Thanks.