Jump to content
The simFlight Network Forums
Sign in to follow this  
gdavej

P3Dv4.2 crashes with FSUIPC after MS 1803 Update

Recommended Posts

Three days ago, I updated my Windows 10 Pro OS with the 1803 Feature update... bad move on my part. Since then,  I've had problems with P3Dv4.2 starting. It would suddenly die, before getting to the start screen. I have a lot of entries in exe.xml and dll.xml, and I tried commenting out entries, until I discovered that the culprit seemed to be FSUIPC  v 5.131. Before the 1803 update, I never had a problem with either P3D or FSUIPC. I believe the problem is related to the Saitek X52 Pro joystick, since the FSUIPC log seems to stop abruptly whilst scanning the joystick. I'll attach both the FSUIPC5.log and FSUIPC5.JoyScan.csv.

I have a registered copy of FSUIPC.

FSUIPC5.JoyScan.csv

FSUIPC5.log

Share this post


Link to post
Share on other sites
48 minutes ago, gdavej said:

I believe the problem is related to the Saitek X52 Pro joystick, since the FSUIPC log seems to stop abruptly whilst scanning the joystick. I'll attach both the FSUIPC5.log and FSUIPC5.JoyScan.csv.

Are there other USB joystick or game type devices attached?

Please download and run my HidScanner program, available in the Additional Useful Programs part of the Download Links subforum, and let me see its log file.

More logging of the scanning part might be useful. Try this:

In the [General] part of the FSUIPC5.INI file, add these lines:

Debug=Please
LogExtras=x200000

(make sure you get the right number of 0's there -- 5 of them!)

Then run P3D again and show me just the Log.

Also, please check the Windows Event Viewer. If the crash is recorded there, in "Windows Logs -> Application"  please copy and paste the details here. It'll be in some format simialr to this:

Faulting application name: ...
Faulting module name: ...
Exception code: ...
Fault offset: ...

etc

Pete

 

Share this post


Link to post
Share on other sites

The crash details refer to a very heavily used part of Windows -- the run time library for C/C++ programs. It could be called from anywhere (noy actually FSUIPC directly because its usage is static -- i.e ocmpiled into the FSUIPC5.DLL. The error is a stack overflow, which s unusual unless something got stuck in a recurrant action, a loop. It must be something in the DirectInput part of Windows.

The extra logging in the FSUIPC5 log definitely shows a problem, a mix-up by the look of it, in the Registry for the X52:

      125 #### Initialising Dlrectinput Axis Scanning ...
      125    (Entry from GetRegisteredOptions)
      125 ---------------------- Joystick Device Scan -----------------------
      125 Checking: \\?\hid#intc816&col02#3&36a7043c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
      125    Usage=12, UsagePage=1, =Flight Mode Switch
      125 Checking: \\?\hid#vid_06a3&pid_0762#6&24b5a767&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      125    Usage=4, UsagePage=1, =Game Controller
      125 Product= Saitek X52 Pro Flight Control System
      125    Manufacturer= Saitek
      125    Vendor=06A3, Product=0762 (Version 1.35)
      156 -------------------------------------------------------------------
      156 ****** Registry scanning: VID=06A3, PID=0762 ******
      156 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0762\Calibration\0"
      156    ... and a "GUID" value
      156    GUID= {89E68830-6754-11E7-8002-444553540000}
      156        NB: not valid for this device according to GetConfig!

The HidScanner log shows that the X52 is the last USB device listed in the Registry, so it will be the only thing causing the problem as FSUIPC does the scan in Registry order.

I think you should uninstall the device completely (including driver), using the Windows Device Manager, then re-boot the PC. This will get its Registry entries rebuilt.

Pete

 

Share this post


Link to post
Share on other sites

Thanks Pete, That did the trick. Sorry I was so slow responding, but I wanted to test a few times, make sure that the issue had well and truly gone.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.