Ray Proudfoot

I didn't know about 4.4 so I'm happy to give them time. You're not daft, it's excellent customer service. 👍

Maybe I'm impatient but I would have expected a question or request for additional info. You missed the e off your name. Shall I emulate Geordies and call you Pet from now on? 😁

Hi Pete, No reply to the L-M post but I see 4.4 is released tomorrow. Rather than reinstall 4.3 I might as well install 4.4 and see if that changes anything.

Hi Pete, Okay, I'll disable DLL.XML and enable controllers in P3D. Do you know the cfg entry for direct mode? I have only 4 USB2 ports so I'm limited. GoFlight stuff, mouse / kbrd take two. Check logs again. I'm sure I posted correct ones for each test.

Final logs from successful launch in case they're helpful. FSUIPC5.ini FSUIPC5.log FSUIPC5.JoyScan.csv

I plugged yoke, throttles and pedals back in and rebooted. Started P3D but rather than crash it just hung with the splash screen showing. Final logs attached. Will launch it again and let's see what happens... And it launches successfully. Now going to go for client update... FSUIPC5.log FSUIPC5.JoyScan.csv

Final test. Just the yoke plugged into a USB2 port and P3D crashed before the free flight screen. Log attached. I think there's a problem with my USB ports. Software rather than hardware. I'll try the client uninstall / reinstall option. Last chance saloon. More later. FSUIPC5.log

Hi again Pete, I plugged just the CH Pro Pedals into a USB2 port - they aren't recognised in a USB3 one - and P3D crashed. Just with one device. Files attached. I'm wondering if this is anything to do with Windows update 1809. And why just on first boot and no thereafter? I'll unplug pedals and try yoke on its own. FSUIPC5.log FSUIPC5.ini

Hi Pete, Shut down PC, removed yoke, pedals and throttles. Restarted and launched P3D v4.3. It showed the free flight menu and I went with the default. After 10-15 secs I exited P3D. Files attached. I shall now shutdown, add pedals only and try the sim again. FSUIPC5.ini FSUIPC5.log FSUIPC5.JoyScan.csv

Hi again Pete, I rebooted and added extra logging option to my original fsuipc5.ini. P3D still crashed. Various files attached. The crash report was virtually identical to above but with different fault offset. Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263 Faulting module name: ntdll.dll, version: 10.0.17763.1, time stamp: 0xa369e897 Exception code: 0xc0000374 Fault offset: 0x00000000000fb349 Faulting process ID: 0x3004 Faulting application start time: 0x01d48594cb177beb Faulting application path: D:\P3Dv4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: f326fd3c-feb0-4cd3-b43f-abfa2487ef00 Faulting package full name: Faulting package-relative application ID: I shall now remove yoke, pedals and 2 x throttle quadrants, reboot and try again. FSUIPC5.JoyScan.csv FSUIPC5.log FSUIPC5.ini

Hi Pete, The first thing I tried was to rename fsuipc5.ini forcing FSUIPC5 to generate a new one. P3D v4.3 crashed and attached are the files created. I'll reboot and add the extra checking into my original fsuipc5.ini. The Event Viewer log was as follows:- Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263 Faulting module name: ntdll.dll, version: 10.0.17763.1, time stamp: 0xa369e897 Exception code: 0xc0000374 Fault offset: 0x00000000000fb349 Faulting process ID: 0x2430 Faulting application start time: 0x01d48593bf50a20e Faulting application path: D:\P3Dv4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: 8043d4d5-df6b-44fa-8d88-f155c0a3240e Faulting package full name: Faulting package-relative application ID: FSUIPC5.log FSUIPC5.ini

Hi Pete, Just a quick one as I have to help a friend with Windows 10 this morning. P3D v3.4 was fine on the old PC but of course that was with W7 and 10 is a very different animal as we know. It shouldn't take long to get v3.4 installed but I'll try what you suggested last night first as those are fairly quick to test and report. Yes, the first addon I installed was FSUIPC5 so P3D controllers are disabled and everything is handled through FSUIPC5. It might be useful to disable FSUIPC5 (rename DLL.XML) and enable controllers in P3D v4.3. That would force it to scan for my USB hardware. But there'd be no log of course so if it failed it wouldn't point to what was responsible. I'll work on this early afternoon.

Hi Pete, Time for bed but I’ll look at removing flight sim devices and adding them back one at a time. The Saitek yoke acts as a hub for the two throttle quadrants. Only the yoke and the CH Pedals are plugged directly into USB ports on the PC. Earlier in the evening there was an entry in FSUIPC.ini saying *Missing Joystick*. I checked the button entries in the ini and I had pasted some hat switch views from the forum into it without changing the letter referencing the device. Once I removed those the *missing joystick* entry disappeared. Those entries were added by me in line with the guidance in the user manual. I also saw a message about DirectInput or words to that effect when P3D was starting but it was temporarily hidden by the splash screen. That relates to DirectX if I remember right so it could be related. I later ran the utility to check DirectX and it completed okay. Rebooted and ran P3D but it crashed. I’ll try renaming the ini first, then unplugging USB devices and then add extra logging. Hopefully one of those will either solve it or give us a clue as to what’s going on. The most confusing part is it running okay on a second attempt. Don’t understand your last question. Do you mean P3D v3.4? If so, answer is no, not yet.

Hi Pete, Thought I'd help by posting here. Following my earlier post on AvSim I was able to get p3D v4 to show the free flight menu with no EXE.XML or DLL.XML files in my appdata\roaming\L-M\p3D folder. Five reboots and five successful loads. I reinstalled FSUIPC5 so it would place an entry in DLL.XML and rebooted. Checked the entry before starting P3D and it looked fine. Launched P3D and it crashed before free flight window. But the only difference from before was the inclusion of FSUIPC5. I'm attaching various files which I hope will help. As you can see the latest fsuipc5.log didn't show all the hardware but in the JoyScan.csv you can see they're all present. I'm also including a previous successful fsuipc5.log for confirmation my hardware looks okay. Hope you can spot something because it's driving me crazy. FSUIPC5.ini FSUIPC5.log FSUIPC5.JoyScan.csv FSUIPC5_prev.log DLL.XML

Thanks Simon. I suspect it was down to the fact the router had been running less than 24 hours so maybe the previous IP addresses were still trying to be used. All very confusing (and frustrating) but hopefully sorted now.