-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Christopher Hall
-
-
Hello,
Please tell me this problem is well-known and I'm just blind:
Prepar3D v3.1 crashes specifically when I have any button assigned on my X-55. There is no error generated in FSUIPC4.log, The Prepar3D application log shows an error faulting an unknown module. A clean reinstall doesn't fix the problem. I also have FSX:SE installed on this same PC, using the same ini file, and it works like a champ. I connected an old X-52 to P3D and haven't gotten any problems yet. I have uninstalled vJoy, checked the power management on all USB ports. I plugged the stick and throttle directly into the PC. Reinstalled the Saitek drivers.I have attached my latest ini file. I don't know what value there is in that. If i delete it, the problem goes away until a program a button.
I have had P3D v3 since day one and have yet to use it the way I need to.
Thanks in advance.
Chris
i7-4770 3.4GHz | NVidia GeForce GTX 750 Ti v361.91
Oculus Runtime 0.8 | FlyInside Pro 1.2 | Leap Motion Controller
Saitek X-55 | LM P3D v3.1 | Windows 10 -
Fixed with the latest version.
Thanks! -
i7-4770 3.4GHz | NVidia GeForce GTX 750 Ti v358.78
Oculus Runtime 0.7 | FlyInside Beta Pro 0.4002 | Leap Motion Controller
LM P3D v3 | FSUIPC v4.947c Windows 10With the HMD on, I can only launch P3D v2.5 or v3 if FSUIPC is disabled.
When I launch v3, after a few minutes, the Prepar3D splashscreen disappears, but the executable stays running. When I launch v2.5, the app crashes to desktop right when the scenario should load.I already had a debug session with the developer of FlyInside, he created this png illustrating the problem without his software installed.
-
+1
i7-4770 3,4GHz
16GB RAM
GTX 750 Ti Driver v
Windows 10
P3D v3
FSUIPC 4.945a
PMDG 737NGX
FSDT GSX, XPOI -
I have the same problem. The mode switch on the throttle is logically part of the stick. It works, but FSUIPC does not respond to the throttle. I have tried toggling AutoAssignLetters to no avail.
What I do find interesting is that FSUIPC seems to only load the joystick that is set as the default USB Game Controller in the Control Panel.
See below:
[JoyNames]AutoAssignLetters=Yes0=Saitek Pro Flight X-55 Rhino Stick0.GUID={4337C890-3778-11E4-800A-444553540000}1=Saitek Pro Flight X-55 Rhino Throttle1.GUID={43302770-3778-11E4-8007-444553540000}2=Razer Tartarus2.GUID={432021E0-3778-11E4-8003-444553540000}3=Saitek Pro Flight X-55 Rhino Stick3.GUID={4333D0F0-3778-11E4-8009-444553540000}A=Saitek Pro Flight X-55 Rhino StickA.GUID={4337C890-3778-11E4-800A-444553540000}D=Saitek Pro Flight X-55 Rhino StickD.GUID={4333D0F0-3778-11E4-8009-444553540000}C=Razer TartarusC.GUID={432021E0-3778-11E4-8003-444553540000}D=Saitek Pro Flight X-55 Rhino ThrottleD.GUID={43302770-3778-11E4-8007-444553540000}B=Saitek Pro Flight X-55 Rhino ThrottleB.GUID={43302770-3778-11E4-8007-444553540000}
FSUIPC4 buttons crash P3D(?)
in FSUIPC Support Pete Dowson Modules
Posted
Each of the devices is listed twice. 2 & 3 are the actual device assignments. 9 & 12 were assigned from vJoy, which I removed completely per Shaul's instructions. There is no driver installed when I run pnputil, yet 9 & 12 persist. P3D never crashes as the result of assigning and axis. The FSUIPC interface allows me to assign buttons to 9 & 12. I once managed to get the interface to recognize 2 & 3 directly, but P3D still crashed.
Currently I have the X-55 installed with the latest Saitek drivers. No vJoy installed. FSUIPC still shows 2,3,9 & 12. P3D does not crash when I rename FSUIPC4.key.
The part that confuses me is that P3D crashes because I assigned a button, and not because I used it. It doesn't matter which button. I will ask LM and Shaul.
Thanks