December 31, 20169 yr Hiu, after updating to the newest HF2 via post (client.msi deinstall and install the new one) I got a p3dv3 crash in startscreen. Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.4.18.19475, Zeitstempel: 0x5851bfd2Name des fehlerhaften Moduls: symmap.dll, Version: 3.4.18.19475, Zeitstempel: 0x5851bf5aAusnahmecode: 0xc0000005Fehleroffset: 0x00029d0eID des fehlerhaften Prozesses: 0x17f8Startzeit der fehlerhaften Anwendung: 0x01d262d3eacb5f8ePfad der fehlerhaften Anwendung: C:\P3Dv3.4\Prepar3D.exePfad des fehlerhaften Moduls: C:\P3Dv3.4\symmap.dllBerichtskennung: 47c40ff8-cec7-11e6-9560-14dae9dbf824 Any solution? Developer www.facebook.com/Crossfeed-Design Phil
January 3, 20179 yr Author So nobody can help me I guess I need to reinstall p3d again. Any advice how to do so? Is it possible, to keep addons installed and just deinstall p3d then install it again? Developer www.facebook.com/Crossfeed-Design Phil
January 3, 20179 yr Moderator Just uninstall the CLIENT and reinstall it. See how that goes. Vic RIG#1 - I9 14900K MSI Pro z790 RTX 5070Ti 40" 4K Monitor 3840x2160
January 3, 20179 yr Do you have chase plane? I had The same thing after updating to v1.5 and it went away once I tuned off Chase Plane Mark CYYZ
January 3, 20179 yr Author already tried to reinstall the client several times. Didn't solve the problem. And no haven't chase plane at all Developer www.facebook.com/Crossfeed-Design Phil
January 3, 20179 yr Only other thing I can suggest is. 1) backup your p3d.cfg, delete original and let P3D build a new one. 2) Make sure to run with no loaded dll's (so you probably need to backup and rename the xml.dll and xml.exe files). I think this will at least give you confidence that its a P3D issue and not something else. If it still happens you may need to do a complete reinstall (although I almost always think this is extreme and should not be necessary) Mark CYYZ
January 3, 20179 yr Author Only other thing I can suggest is. 1) backup your p3d.cfg, delete original and let P3D build a new one. 2) Make sure to run with no loaded dll's (so you probably need to backup and rename the xml.dll and xml.exe files). I think this will at least give you confidence that its a P3D issue and not something else. If it still happens you may need to do a complete reinstall (although I almost always think this is extreme and should not be necessary) Already tried 1) with no result. but will try the second one. Developer www.facebook.com/Crossfeed-Design Phil
Archived
This topic is now archived and is closed to further replies.