aero-3fsx Posted June 3, 2017 Share Posted June 3, 2017 After spending most of the day installing OrbX scenery into P3D V4 the sim crashes on startup every time Most of the installed files were taken from P3D V3 with FTXC v3.2 I can still successfully install more OrbX regions but the sim itself won't run I had exactly the same problem last week when I installed P3D V3 on my new SSD This was solved with a new V3 config file but I don't have a backup for V4 Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 3, 2017 Share Posted June 3, 2017 Hello, then try deleting C:\Users\your name\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.cfg? Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 3, 2017 Author Share Posted June 3, 2017 Thanks for your super fast answer Will try it as soon as Southern Alaska is installed Are there any negative side effects of deleting this config file? Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 3, 2017 Share Posted June 3, 2017 I don't think so, P3D will simply replace it with a default one. Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 3, 2017 Author Share Posted June 3, 2017 Thanks for another fast answer So then I just need to reset my settings under options? Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 3, 2017 Share Posted June 3, 2017 Yes, All your settings will revert to default. If you wish to keep them, you will need to back up the existing Prepar3D.cfg file. Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 3, 2017 Author Share Posted June 3, 2017 Removed the cfg file but P3D v4 still crashing on startup The scenario window will stay on screen but as soon as you try to do anything such as set an airport it crashes Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 3, 2017 Author Share Posted June 3, 2017 All these wonderful OrbX regions on my computer now & I cannot fly My v3 install is still wrecked by a bad install of Vector which has wiped away all seas & rivers Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 3, 2017 Share Posted June 3, 2017 Perhaps you might take a look at the Windows Event Viewer and see what it is that is causing P3D v4 to stop working. As for P3D v3, unticking the Vector scenery library entries will remove it from the simulator. Link to comment Share on other sites More sharing options...
petkez Posted June 3, 2017 Share Posted June 3, 2017 I had the same problem. Was working fine until I installed Orbx. After installing Orbx P3Dv4 would crash during loading. I tried deleting the ,cfg and it didn't work. I was lucky as I just purchased a new PC and all I had installed was P3Dv4 and Orbx so I just formatted my HD and started again and this time everything seems ok. Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 3, 2017 Author Share Posted June 3, 2017 2 hours ago, Nick Cooper said: As for P3D v3, unticking the Vector scenery library entries will remove it from the simulator. Finally had to deinstall antivirus, clear every entry in firewall & a couple of other adjustments and I was able to clear the temp DL in FTX Central Am installing Vector in v3 now & nearly half way through 2 hours ago, petkez said: so I just formatted my HD and started again and this time everything seems ok. It would take me over a day to install everything again so that is out of the question If absolutely desperate I could try reinstalling P3D v4 again I am sure there is an easier solution out there Thanks to you both for your suggestions Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 6, 2017 Author Share Posted June 6, 2017 Here are the reports from the Windows Event viewer 3 errors, 2 with P3D & 1 with NETframework -------- Faulting application name: Prepar3D.exe, version: 4.0.23.21468, time stamp: 0x59279be2 Faulting module name: symmap.dll, version: 4.0.23.21468, time stamp: 0x59279b5a Exception code: 0xc000041d Fault offset: 0x0000000000031adc Faulting process ID: 0x7f0 Faulting application start time: 0x01d2dea1f51c8e2a Faulting application path: F:\Prepar3d64\Prepar3D.exe Faulting module path: F:\Prepar3d64\symmap.dll Report ID: 8f861d37-4f85-4293-b79c-009cfe0ddd14 Faulting package full name: Faulting package-relative application ID: --------------------- Faulting application name: Prepar3D.exe, version: 4.0.23.21468, time stamp: 0x59279be2 Faulting module name: symmap.dll, version: 4.0.23.21468, time stamp: 0x59279b5a Exception code: 0xc0000005 Fault offset: 0x0000000000031adc Faulting process ID: 0x7f0 Faulting application start time: 0x01d2dea1f51c8e2a Faulting application path: F:\Prepar3d64\Prepar3D.exe Faulting module path: F:\Prepar3d64\symmap.dll Report ID: f42b9a33-7ce2-4f9c-8c48-4cfe6030dcd3 Faulting package full name: Faulting package-relative application ID: -------------------- 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 00007FFF6B311ADC Stack: at <Module>.UIInterface.UnmanagedWindowsBridge.DialogFrame(UIInterface.UnmanagedWindowsBridge*, UInt32) at <Module>.UIInterface.UnmanagedWindowsBridge.DialogFrame(UIInterface.UnmanagedWindowsBridge*, UInt32) at UIInterface.WindowsBridge.DialogFrame(UInt32) at UIControls.SubMenuDialog.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Window.ShowHelper(System.Object) at System.Windows.Window.ShowDialog() at UIControls.SubMenuDialog.ShowMenu(Boolean) at MenuSystem.MenuSystem.OpenDialogCommon(UIControls.SubMenuDialog, UIControls.SubMenu, Core.AlertOptions) at <Module>.OpenScenarioStartupDialog(Int32) ------------------- Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 6, 2017 Author Share Posted June 6, 2017 Just tried deinstall of client then reinstalled & reactivated No change, P3D v4 still crashes on start Window stays up but as soon as any action is taken then crash occurs Link to comment Share on other sites More sharing options...
Richard Lincoln Posted June 6, 2017 Share Posted June 6, 2017 Hi, Were you running Antivirus Software when installing P3d? this " symmap.dll" is a common pain associated with that, I think it is worth reporting over at LM Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 6, 2017 Author Share Posted June 6, 2017 Thanks for the info I have already changed from Avast to Avira antivirus Should I now completely deinstall and reinstall P3D V4? What should I do to protect all my OrbX sceneries? Link to comment Share on other sites More sharing options...
Richard Lincoln Posted June 6, 2017 Share Posted June 6, 2017 Hi, To protect your Orbx installation, please create a Rule for FTXCV3 and your Sim Root Directory, you will need to contact LM for more information regarding reinstalling their product. Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 6, 2017 Author Share Posted June 6, 2017 2 minutes ago, Richard Lincoln said: To protect your Orbx installation, please create a Rule for FTXCV3 and your Sim Root Directory, you will need to contact LM for more information regarding reinstalling their product. What exact rule do you have in mind? I have already contacted LM yesterday & am waiting for reply Link to comment Share on other sites More sharing options...
Richard Lincoln Posted June 6, 2017 Share Posted June 6, 2017 Hi, I can not give direct support for that question, I looked up "How to create a Rule for Avira" in Google https://www.avira.com/documents/products/pdf/en/howto_avira-internet-security_firewall_en.pdf Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 6, 2017 Author Share Posted June 6, 2017 At the moment OrbX is in the P3D v4 folder structure If I deinstall v4 then all OrbX scenery for v4 will also be deleted, yes? I don't want to waste my time reinstalling that as well Is there any way I can protect this? Link to comment Share on other sites More sharing options...
Richard Lincoln Posted June 6, 2017 Share Posted June 6, 2017 Hi, You need to contact LM, repair that and then report back as to the Orbx install. Link to comment Share on other sites More sharing options...
aero-3fsx Posted June 7, 2017 Author Share Posted June 7, 2017 LM are very slow to help so I decided to try a few things after getting ideas on Avsim forum That was specifically that any old install files has the potential to ruin the formatting of the new config files due to new v4 conformity I changed the names of a few of the .cfg files so P3D V4 would regenerate them one by one I then forced the migration withing FTX Central & now everything works Thanks for the ideas etc that people contributed Link to comment Share on other sites More sharing options...
Richard Lincoln Posted June 7, 2017 Share Posted June 7, 2017 Hi, Excellent news, thanks for reporting back. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.