a340500 Posted June 23, 2016 Share Posted June 23, 2016 Hi Team, I have been experiencing P3Dv2, V3 CTDs with the error g2d.dll. I worked with avsim and narrowed down the module to ObjectFlow_P3D via this thread http://www.avsim.com/topic/489722-p3d-v32-33-g2ddll-error-exception-code-c0000005-exception-offset-000d7803/page-2 I have currently disabled the module in the dll.xml file and all PMDG 777 flights are now completing without issue. Please shed some light as to how can I resolve this. FTXC2 Diagnostic Reporter reference is ot6b0aa6e723897eb71d94b1fe43d34e9c Please let me know what further information do I need to provide. Prepar3D_v3_Academic_3.3.5.17625 (Latest build) ObjectFlow Prepar3D module version 1.0.13.2 Location : D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery CTD details with ObjectFlow_P3D module enabled is Log Name: Application Source: Application Error Date: 6/23/2016 3:15:11 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-K7LRFKD Description: Faulting application name: Prepar3D.exe, version: 3.3.5.17625, time stamp: 0x5758bb31 Faulting module name: g2d.dll, version: 3.3.5.17625, time stamp: 0x5758bbc2 Exception code: 0xc0000005 Fault offset: 0x000d7663 Faulting process id: 0xf74 Faulting application start time: 0x01d1cd08e151cb41 Faulting application path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe Faulting module path: D:\Lockheed Martin\Prepar3D v3\g2d.dll Report Id: 754ca68d-3901-11e6-be28-305a3a0172c9 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-06-23T05:15:11.711706800Z" /> <EventRecordID>7869</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-K7LRFKD</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>3.3.5.17625</Data> <Data>5758bb31</Data> <Data>g2d.dll</Data> <Data>3.3.5.17625</Data> <Data>5758bbc2</Data> <Data>c0000005</Data> <Data>000d7663</Data> <Data>f74</Data> <Data>01d1cd08e151cb41</Data> <Data>D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data> <Data>D:\Lockheed Martin\Prepar3D v3\g2d.dll</Data> <Data>754ca68d-3901-11e6-be28-305a3a0172c9</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Regards, Mario Link to comment Share on other sites More sharing options...
Guest Posted June 23, 2016 Share Posted June 23, 2016 Hi, Objecflow is normally updated to v3.3.5 on start of P3D. If that process is locked, that's normal OF doesn't work and makes P3D crashs in case of pass by the warning Link to comment Share on other sites More sharing options...
Guest Posted June 23, 2016 Share Posted June 23, 2016 G2d.dll is generally linked to FSUIPC which has the same behaviour than ObjectFlow if not at the latest version Link to comment Share on other sites More sharing options...
a340500 Posted June 23, 2016 Author Share Posted June 23, 2016 Hi Richard, I have FSUIPC4 v955c installed which is the latest version. Please advise what can I do to stop these errors.. It only occurs when enabling the ObjectFlow_P3D module in dll.xml M Link to comment Share on other sites More sharing options...
Guest Posted June 23, 2016 Share Posted June 23, 2016 ObjectFlow.dll is updated by ORBXlibs. Once installed, it's auto-checked to have latest any time P3D is launched. Link to comment Share on other sites More sharing options...
a340500 Posted June 23, 2016 Author Share Posted June 23, 2016 Is there a manual method to clean uninstall the module ? I tried deleting the file but it didn't appear like it was removed. I have downloaded the offline module from here : Link to comment Share on other sites More sharing options...
Penzoil3 Posted June 24, 2016 Share Posted June 24, 2016 If you un install, none of your People Flow etc. will work. Link to comment Share on other sites More sharing options...
a340500 Posted June 24, 2016 Author Share Posted June 24, 2016 My intention is to uninstall Objectflow.dll and let it automatically install when I next start P3D. So is there a manual method to clean uninstall the module ? I tried deleting the file but it didn't appear like it was removed. Link to comment Share on other sites More sharing options...
Ed Correia Posted June 24, 2016 Share Posted June 24, 2016 You can run the moduleinstaller.exe in the Orbxlibs scenery library to uninstall the module. As Sue says, scenery items that use OF won't appear. I don't believe your issue is due to the module though, plenty of people using PMDG and OF without issue and I have not heard of any problems from the PMDG team themselves about it. Link to comment Share on other sites More sharing options...
a340500 Posted June 24, 2016 Author Share Posted June 24, 2016 Thanks Richard, Sue and Ed, I'm beginning to think that I need to bite a huge bullet and clean install P3D then PMDG and then fly a test flight after installing every addon.. It will be a very slow and painful experience but I think it needs to be done. Please close this item I do believe the fault is NOT with the module. Link to comment Share on other sites More sharing options...
Ed Correia Posted June 24, 2016 Share Posted June 24, 2016 No problems, nothing like a clean reinstall now and then. I find by doing that I only reinstall addons that I know I'll be using, so its a good time to assess what you need and not burden the system with unused addons. Link to comment Share on other sites More sharing options...
a340500 Posted July 10, 2016 Author Share Posted July 10, 2016 Ok, have finally found something that seems to have helped. 1. I rebuilt w10x64, Installed drivers. 2. Installed a third party Driver updater and updated all drivers and VC++ (BIG MISTAKE). 3. Ran 3Dmark and tested Graphics and machine with stress tests - PASSED. 4. I then reinstalled P3D, PMDG, NavDataPro, PFPX and flew a flight vanilla, addon scenery. - VABB to OMDB - PASSED. 5. Installed a P3Dv3 compatible thrid party OMDB - Flew PMDG 777 - VABB to OMDB - FAILED - G2d.dll. I then googled the third party product and g2d.dll and found that VC++ installs may be an issue. I noticed I had a whole bunch of VC++ from 2005 till 2015.. thanks to the third party Driver updater. 6. I uninstalled all VC++ versions. Rebooted 7. Ran w10 windows update - Auto installed MS VC++2008, 2010x64 and 2010x86. Rebooted 8. Ran P3D - Flew PMDG 777 - VABB to third party OMDB - Success!! Am now installing FTX Global and Vector and will then test the same flight and then ORBX YMML and third party YSSY.. Status : Possible solution. DO NOT LET a third party Driver updater run..Have uninstalled the program. Please keep this thread open as monitoring. Link to comment Share on other sites More sharing options...
a340500 Posted August 26, 2016 Author Share Posted August 26, 2016 Hi Team, I have installed every orbx region and airport from scratch and the g2d.dll errors prevail. At this stage, I only have Orbx addons. Please advise what is the best method of disabling or uninstalling each of your airports and regions one at a time? My plan is to fly a few PMDG777 flights after disabling every orbx addon until the errors stop. Regards, M Link to comment Share on other sites More sharing options...
Ed Correia Posted August 26, 2016 Share Posted August 26, 2016 Unticking the scenery library entry temporarily disables it. Link to comment Share on other sites More sharing options...
a340500 Posted August 26, 2016 Author Share Posted August 26, 2016 thanks Ed will give that a go Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.