February 3, 201610 yr Commercial Member 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 Steve Waite: Engineer at codelegend.com
February 3, 201610 yr 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
Create an account or sign in to comment