Helmi67 Posted September 19, 2017 Share Posted September 19, 2017 Dear team, after running my Prepar3D_v3_Professional_3.4.22.19868 sim since May 2017 without any troubles yesterday I updated (just by chance) all my ORBX products now via FTX central to be uptodate... ORBX GLOBAL + EUROPE_LC + VECTOR + LOWI (in this given sequence) NOW it unstable: Almost everytime when I start my sim I get after the loader progress bar is almost through, at the same stage, the following fatal error message (please see the screenshot below): Now today I performed a clean installation (admin rights, no virus scanner, CC Clean etc) from scratch, and I noticed that after the final installation of ORBX LOWI the errror occured again (and it did not go away even after its deinstallation, that's the nuisance). I only know that I moved from LOW V1.05 (purchased release mid of May 2017) to V1.10 and I guess there is something wrong with the latest version. Therefore my question: I do not want to spend hours on debugging, I would be happy if I could rollback / download ORBX LOWI V1.05 from somewhere ? or does anybody have an idea what this general fatal error message could mean ? So far my entire system was fully stable for month. All the Win10 Updates with security changes could also be a problem for stability. My Win10 event protocol starts with a .NET run time error (please see also my screenshot) ******************************************************************************************************************************* indows.Interop.MSG ByRef, ******************************************************************************************************************************* I have .NET 4.6.2 and .NET 4.7 installed (these existed already before my ORBX update) Many thanks for further ideas or hints - the LOW scenery was so nice and suddenly its all instable after an arbitrary update. Regards Helmut Link to comment Share on other sites More sharing options...
Nick Cooper Posted September 19, 2017 Share Posted September 19, 2017 Hello, please try this: Quote You should open the properties tab of Prepar3D.exe and then the compatibility tab. Then tick the compatibility tab and select Windows 8, click on Apply. Link to comment Share on other sites More sharing options...
Helmi67 Posted September 19, 2017 Author Share Posted September 19, 2017 Hi Nick, thanks for the your quick idea, which I tried out but unfortunately did not make any differerence even after a reboot: Do you know if there is a P3D log file, which traces the start up process apart from the "Win 10 event viewer" I am still counting on the "rule out principle". My windows user is Helmi 67, and I read in some P3D forums that "special characters" might confuse the P3D start up process. But I believe a space character between Helmi 67 should not cause conflicts with certain P3D path names ? A work around is a new win user name, but this requires a new P3D installation to get rid of Helmi 67 -> Helmi67 Currently I am using... C:\Users\Acer\AppData\Roaming\Lockheed Martin\Prepar3D v3n mapped to I am still confused how to tackle this fairly nifty error problem. I can only tell, that it never occured before since I own P3dV3, and the ORBX Updates triggered it somehow. It could well be situated now in the P3D environment. Also a P3D V3 repair did not help, the crash still happens at 80% of all start ups always at the final stage "loading air, train, sea traffic" regardsless of higher graphics settings etc. There seems a link broken.... Thanks for another hint or idea how to identify this issue best ? Helmut Link to comment Share on other sites More sharing options...
Helmi67 Posted September 20, 2017 Author Share Posted September 20, 2017 Hi Nick, is there any chance to download manually and rollback ORBX Vector and ORBX LOWI to the release valid as of Mid of May 2017 ? Thanks Helmut Link to comment Share on other sites More sharing options...
Helmi67 Posted September 20, 2017 Author Share Posted September 20, 2017 I just noticed in the P3D forum that the recent Win 10 Update KB4038788 causes crashes like mine http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=126667 for all that may concern this issue I will follow this hint next. Helmut Link to comment Share on other sites More sharing options...
Helmi67 Posted September 20, 2017 Author Share Posted September 20, 2017 RESOLVED deinstallation of win 10 Update KB4038788 solves the problem. The remaining question is which side needs to adapt its software? Is it MS, Prepare3d or ORBX ? Thanks Helmut Link to comment Share on other sites More sharing options...
Nick Cooper Posted September 20, 2017 Share Posted September 20, 2017 Hello, There is already a topic on this, which I quoted from. There is no remaining question except why a fix would work for some and not for others. Link to comment Share on other sites More sharing options...
Kiwon kim Posted October 2, 2017 Share Posted October 2, 2017 Same as me.. I reinstall over and over P3D V3.. I found that 3rd party add-on making a crash with P3D including ORBX product... Link to comment Share on other sites More sharing options...
Matt McGee Posted October 15, 2017 Share Posted October 15, 2017 On 9/20/2017 at 12:51 AM, Nick Cooper said: There is no remaining question except why a fix would work for some and not for others. My fun meter is pegged. I was excited to see your compatibility mode fix, but unfortunately it didn't work for me. Not happy with Microsoft. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.