Sign in to follow this  
thomamaxi

Prepar3D v3 Not loading since latest Windows 10 Preview update build

Recommended Posts

Hello,

 

I would really be grateful if someone could kindly point me in some direction as to how to get beyond the loading screen in prepar3d. It just sticks there trying to load the opening screen of prepar3d. This has only happened since I updated the very latest Windows 10 preview build.

 

 

I have tried deleting the Prepar3d.cfg but no joy.

 

Paul

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Hi Paul,

 

This probably won't help (sorry!) but your post reminded me about a minor issue I have been faced with since day one of my latest build.

 

If I run P3D or any of the 3D games installed on my rig after first boot then I know they will load part way and then lock-up with the appearance of 'The graphic driver has stopped responding' message. Shortly afterwards the driver recovers and there is no problem thereafter. So far, I have not been able to resolve this issue, but found that performing a simple Restart 'fixes' the problem and there is no recurrence thereafter. So my routine now is: Cold Boot followed by a Restart. Fortunately my system boots quite quickly so it's not too bothersome.

 

Before anyone makes the suggestion, this issue has persisted through many graphic driver updates so there must be a cause common to all of them - perhaps it has nothing to do with the running driver per se, but is occurring at some point when the graphic driver components first load. With P3D v3.1 the sim will load as far as the F22-Raptor on the runway at Eglin and I know it has frozen as the Speed Trees on the right are not moving.

 

So, if you haven't already done so, why not try performing a warm Restart and then see if your loading problem persists. I'm still on W7 Pro 64bit and have no interest in moving to W10 yet awhile - there really is no pressing need or requirement to do so.

 

Regards,

Mike

  • Upvote 1

Share this post


Link to post

Hi Mike,

 

Thank you for taking the time out to reply. Honestly I am not 100% sure what you mean by a 'warm start up' but I will try safety mode and see if that can kick start anything to get it moving.

 

Paul

Share this post


Link to post

Hi Mike,

 

Thank you for taking the time out to reply. Honestly I am not 100% sure what you mean by a 'warm start up' but I will try safety mode and see if that can kick start anything to get it moving.

 

Paul

Hi Paul,

 

Ah, apologies. Warm Restart/Restart = Warm boot = Reboot and is performed while the computer is running and without having to power down (shutdown):

 

http://whatis.techtarget.com/definition/reboot-warm-boot-cold-boot

 

Regards,

Mike

Share this post


Link to post

Paul, check file C:\Users\your_username\AppData\Roaming\Lockheed Martin\Prepar3D v3\dxdiag.txt whether it has actual date. If yes you can find there where is the problem. Yesterday my P3D v3.1 was crashing during startup. I found that FSUIPC is the problem so I installed the newest version and it fixed it.

Share this post


Link to post

Hi Paul,

 

Open Prepar3D.CFG in Notepad (create a copy first to be on the safe side) and look for SHOW_SCENARIO_WINDOW=1. You will find it under the heading [uSER INTERFACE]. Change the 1 to 0 and save the file.

 

Run P3D and see whether you can now load all the way into the sim.

 

Regards,

Mike

Share this post


Link to post

Hi Mike,

 

Thank you for your reply. Unfortunately it didn't work :(

 

Paul

Share this post


Link to post

Recently I had a similar problem: Out of a sudden P3Dv3.1 did not start anymore (never reached the scenario screen). In many cases, thats my experience, dll.xml is the bad boy. Thus, I deactivated my dll.xml by renaming it to dll.xml.off . After this P3D started as usual. Then, normally I reactivate the dll.xml  and start disable/enable various entries in this file to find the culprit.

 

This time it was much easier. Just renaming it to dll.xml.off - starting P3D sucessfully - renaming it back to dll.xml has cured the problem. 

 

Don't ask me why ...  Sometimes I don't "understand" my machine and rather more I do not understand my actions. But as long it works ... :wink:

Share this post


Link to post

Hi Harry,

 

Thank you for your post. Can you pleaes tell me where this 'bad boy' resides?

 

Thanks

 

Paul

Share this post


Link to post

I looked in the dixdig file and came across this:

 

 

Diagnostics
---------------
 
Windows Error Reporting:
+++ WER0 +++:
Fault bucket 124579321317, type 5
 
Event Name: SkyDriveClientError
 
Response: Not available
 
Cab Id: 0
 
 
 
Problem signature:
 
P1: OneDriveSetup.exe
 
P2: 17.3.5892.0626
 
P3: OneDriveSetup.exe
 
P4: 17.3.5892.0626
 
P5: 0x80040692
 
P6: Installer
 
P7: application.cpp
 
P8: 151
 
P9: 
 
P10: 
 
 
Any thoughts?
 
Paul

Share this post


Link to post

Hi Mike,

 

Thank you for your reply. Unfortunately it didn't work :sad:

 

Paul

Hi Paul,

 

I didn't really expect it to work, but thought it might be helpful as part of the troubleshoot.

 

Not sure, and I could be wrong, but the dxdiag report may prove to be a red herring and has nothing to do with your problem.

 

My money now would be on Harry's suggestion. You will find the file DLL.XML here:

 

C:\Users\Your Username\AppData\Roaming\Lochheed Martin\Prepar3D v3

 

If you come up empty then you will need to change a setting to reveal hidden files:

 

Control Panel > Folder Options > Click the View tab and under Advanced settings, click Show hidden files, folders and drives and then click OK.

 

If you need to Edit the file use Notepad. Please create a copy first just in case!

 

Good luck!

 

Regards,

Mike

Share this post


Link to post

Maybe is this one:

Here is the complete list of known issues with Insider Preview Build 11102:
 

 
  • Some PC games will crash switching from windowed mode to full screen, upon game resolution change, or upon launch due to a bug in Windows graphics stack. We have observed this with The Witcher 3, Fallout 4, Tomb Raider, Assassin’s Creed, and Metal Gear Solid V but it may occur with other titles as well.

I'd rollback to the previous build and see if it works. If it does, set your Win10 to slow update so you can get all bugs ironed out before it reaches you.

Share this post


Link to post

If you've got the NVidia card then run the NVidia Control Panel and Restore all profiles in Manage 3D Settings.



On some systems the Win10 upgrade may have altered permissions. Check the P3D program folder (where it is installed), Properties, Security, Users group, has Modify (and Write) permission.

Check the data folder has the same permissions:
C:\ProgramData\Lockheed Martin\Prepar3D v3
 
 

In Prepar3D.cfg check the default flight is set:
[uSERINTERFACE]
SITUATION=C:\Users\[you]\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default
(check the default flight is original)


If that doesn't clear it, check out the dll.xml as was said. Find it in:
C:\Users\[you]\AppData\Roaming\Lockheed Martin\Prepar3D v3
Renaming this file is a good way to temporarily check there's nothing going wrong in there to prevent the sim starting up.


 

Share this post


Link to post

Hi Steve,

 

Thanks for your post. I am not sure about the userinterface. Here is my CFG

 

[uSERINTERFACE]
Map_Orientation=2
PAUSE_ON_LOST_FOCUS=1
PROMPT_ON_EXIT=1
RestoreTimeOnMove=0
SHOW_MISSION_CAPTIONS=0
SHOW_SCENARIO_WINDOW=1
 
Is it Ok?
 
Thanks for your help
 
Paul

Share this post


Link to post

I am running the latest and greatest preview build with no issues. May I suggest running ONLY the client portion of the installer and see if that gets it going.

Share this post


Link to post

Is it Ok?

Should be fine unless the file has been altered. If you don't have the SITUATION item in the cfg, then it reverts to the stock value internally and chooses anyway:

 

C:\Users\[you]\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default

 

which is the "Default Prepar3D scenario, on the runway, at Eglin AFB"

 

By deleting Prepar3D_Default.fxml P3D will make a new one when you next run it. So you can leave the cfg without the SITUATION item, and just to be sure you can rename or delete the Prepar3D_Default.fxml and Prepar3D_Default.wx

Share this post


Link to post

Hi Guys, been getting a similar prob, on P3D launch was getting "msvcp.dll is not designed to work with w10 or has a problem". Tried all the suggested fixes I found on-line a few besides, no deal. Just tried Harry's dll.xml rename (.bak) and it worked a treat. I now have P3D working again.

 

Thank Harry/Guys for you help and assistance.

 

Ken

Share this post


Link to post

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