Bumblemus Posted January 18, 2018 Share Posted January 18, 2018 Hello everyone, I located an error while departing San Diego to JFK: g3d.dll crash near these coordinates: N32 51.84 ; W116 15.02 I use Open LC NA + SA. The error happens even without an add-on plane, Active Sky, Sky force or anything else. Thanks, Bumblemus Link to comment Share on other sites More sharing options...
Stewart Hobson Posted January 18, 2018 Share Posted January 18, 2018 Please Google this error and you'll find many references. It is particular to FSX, as I recall, but there may be many causes. It can be remedied by installing the freeware version of FSUIPC, as I recall. Link to comment Share on other sites More sharing options...
Bumblemus Posted January 21, 2018 Author Share Posted January 21, 2018 Hello Stewart, Thank you for your answer. I tried what you did without success. However, when I desactivate Open LC NA, there is no error, but this is the case with UTL too. Today, while descending to Washington KDCA, an error occured near the waypoint "COURG" (FRMM3 STAR) twice: I didn't even have an error in the windows event viewer. I just have this message: DllHost (10072,G,0) La fonctionnalité bêta EseDiskFlushConsistency est activée dans ESENT en raison des paramètres du mode Site bêta 0x800000 I permit myself to advise you here because I see some users reported similar "P3D exits" over Yukon. The last windows update seems very unstable and without a doubt for something in these multiple errors. Thanks, Bumblemus Link to comment Share on other sites More sharing options...
Stewart Hobson Posted January 21, 2018 Share Posted January 21, 2018 Hello, again! I'm sorry I am no help with your error message. Perhaps an Italian speaker can help you with it? Cheers! Link to comment Share on other sites More sharing options...
Bumblemus Posted January 21, 2018 Author Share Posted January 21, 2018 French actually :-) Here is the english version: DllHost (11700,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site It is not an error, it is simply an event that make P3D stop working. Cheers! Link to comment Share on other sites More sharing options...
Stewart Hobson Posted January 21, 2018 Share Posted January 21, 2018 Oops! My apologies, monsieur! That message is still a mystery to me, however. Sorry! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.