Prepar3D v4 is not starting (due to USB controllers/joysticks/keyboards - e.g. Razer Orbweaver)

[hermes82]

anyone run into problems using touchscreen?

[fince]

Had the same issue, unplugged my Razer Orbweaver and started up for the first time.

Thank you

[STEVE1234]

Hi everyone , Hi LM support,

thank you for your support on this topic. I do not have a specific keyboard which is listed right in this topic but i have the ThrustMaster Hotas Wartdog joystick and throttle. I will to remove this USB's like descriped and report if the ThrustMaster Hotas Wartdog is also effected.

Best regards

[Ron Attwood]

[CONTROLS]
EnableDirectInput=True

Two missing little lines that robbed me of 5 hours!

Many thanks to the guy that discovered it. :-)

[johnnywutw]

jayren and zepplin,

Do either of you have any addons installed? Have you taken a look at our general debugging steps thread?

Regards,
Kayla

Hi, Thanks for quick response.

I renamed the TargetInfo.dll, no use.

Then I add the SHOW_SCENARIO_WINDOW=0 to my cfg. Also, there is no UserInterface Section in my original cfg. After adding this line, P3D does load without the scenario window. But I have a F22 crashed into the sea. And right click is disabled.

Ok, a correction. Right click is not disabled, it is just my plane is crashed and the sim keep loading the same scenario. I managed to pause the game and try to change to an airport. But once the scenario menu appears, game crashes.

I got same problem

[Chris69]

I had that crash on starting too, but

[CONTROLS]
EnableDirectInput=True

fixed that.
I have a Razer BlackWidow Chroma keyboard.

[FireRx]

thanks guys,
that help with the basic control issues here too. and will get me by til FSUIPC5 is in the pipe. Buttons setting are still nil. :)

[bradl]

I'm still getting the crash after building the scenery files and getting to the Prepar3D Scenario screen. This also occurred after running it for the first time.

Crash dump from the Event viewer is below:

Problem signature:
Problem Event Name: APPCRASH
Application Name: Prepar3D.exe
Application Version: 4.0.23.21468
Application Timestamp: 59279be2
Fault Module Name: atidxx64.dll
Fault Module Version: 8.17.10.581
Fault Module Timestamp: 546e9ecc
Exception Code: c0000005
Exception Offset: 000000000059b3da
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: ce0b
Additional Information 2: ce0bfa972b4bffe98e6830e87165821a
Additional Information 3: 3d4e
Additional Information 4: 3d4e379af8047de47ec968f5a5aa0621

Windows Event log gives me these 2 entries for the crash:

Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 000007FEF344B3DA

and

Faulting application name: Prepar3D.exe, version: 4.0.23.21468, time stamp: 0x59279be2
Faulting module name: atidxx64.dll, version: 8.17.10.581, time stamp: 0x546e9ecc
Exception code: 0xc0000005
Fault offset: 0x000000000059b3da
Faulting process id: 0x3990
Faulting application start time: 0x01d2db427eb9102c
Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\system32\atidxx64.dll
Report Id: c132ef3a-4735-11e7-ab68-84a6c82cdab6

Specs are:

Intel Core i5 3570K
ATI R9 290
8GB DDR3 memory
Gigabyte GA-Z77N-WIFI

I'm using a simple Logitech keyboard and a Logitech Wingman Extreme joystick. Nothing really fancy about it. Both were unplugged and plugged in again, to no effect.

EnableDirectInput=True also did not work.

BL.

[bradl]

I'm still getting the crash after building the scenery files and getting to the Prepar3D Scenario screen. This also occurred after running it for the first time.

Crash dump from the Event viewer is below:

Problem signature:
Problem Event Name: APPCRASH
Application Name: Prepar3D.exe
Application Version: 4.0.23.21468
Application Timestamp: 59279be2
Fault Module Name: atidxx64.dll
Fault Module Version: 8.17.10.581
Fault Module Timestamp: 546e9ecc
Exception Code: c0000005
Exception Offset: 000000000059b3da
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: ce0b
Additional Information 2: ce0bfa972b4bffe98e6830e87165821a
Additional Information 3: 3d4e
Additional Information 4: 3d4e379af8047de47ec968f5a5aa0621

Windows Event log gives me these 2 entries for the crash:

Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 000007FEF344B3DA

and

Faulting application name: Prepar3D.exe, version: 4.0.23.21468, time stamp: 0x59279be2
Faulting module name: atidxx64.dll, version: 8.17.10.581, time stamp: 0x546e9ecc
Exception code: 0xc0000005
Fault offset: 0x000000000059b3da
Faulting process id: 0x3990
Faulting application start time: 0x01d2db427eb9102c
Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\system32\atidxx64.dll
Report Id: c132ef3a-4735-11e7-ab68-84a6c82cdab6

Specs are:

Intel Core i5 3570K
ATI R9 290
8GB DDR3 memory
Gigabyte GA-Z77N-WIFI

I'm using a simple Logitech keyboard and a Logitech Wingman Extreme joystick. Nothing really fancy about it. Both were unplugged and plugged in again, to no effect.

EnableDirectInput=True also did not work.

BL.

Actually, mine is a bit more confusing. Mine turned out to be not having updated video drivers. So I updated mine, and now I'm getting a dialog box saying:

Prepar3D was unable to initialize the rendering system and will shut down. Please make sure this system has a video card that supports DirectX 11 and that the drivers are up to date.

The card I have (which is actually the r9 280, not the R9 290) supports DirectX 11.1, according to GPU-Z as well as the specs for the card, so I'm not sure why this is even giving me this error.. thoughts?

BL.

[smyalygames]

Prepar3D.exe doesn't work anymore.." and I have the option to debug.

If you have Visual Studio 2015, could you provide us with a crash dump?

When Prepar3D crashes, the option to debug through Visual Studio should appear. Attach to the Prepar3D process and then go to Debug --> Save Dump As to save the memory dump. Feel free to upload that to Dropbox or some other file server and PM me a link. Make sure you provide the full version number with each dump.

More details here: https://msdn.microsoft.com/en-us/library/d5zhxt22.aspx

Regards,
Adam

Hello, I used task manager to create the dump file, and I used Visual Studio 2017.

Here is the link: https://mega.nz/#!ZJtnyQzb!Ze926a7HNYTt ... NZhUJSh_x0

[Adam Breed]

Hi All,

We will have a fix for the Orbweaver in an upcoming hotfix. Please continue to use DirectInput as a workaround.

Regards,
Adam

[JackSwyr]

Thank you a MILLION times!

[timo_de_jong]

Hi guys so i made the change from fsx to p3d v4 recently.
so after purchasing the sim i went ahead and installed it.
when i launched it it generated all the indexes and then it closed.
when starting again i see the splash screen my mouse turns into a loading icon when hovering over it and thats it.
i see it in the task manager as a background process with not that much activity.

i dont own any razer products and i cant unplugged them because the only devices i have connected are my mouse and keyboard and my joystick. i already unplugged my joystick but still the same.

so i looked further and saw that some people added enabledirectinput=true to there cfg. so i tried that but nothing happend.
so right now im atempting the repair tool but i have not that much fate that it will work.

so please help me, i just want to fly v4

[DaiG]

I have another failing device for you: Mad Catz F.L.Y.5 Flight Stick (USB). Switching to DirectInput solves the problem for this one.

-Dai

[Woof]

I had the exact startup issues (splashscreen shows, scenrery building and then nothing, but still appearing in task manager) after trying to save the default situation as a PMDG vehicle.

I deleted the "situation=" line from the config file and all worked again.