Sign in to follow this  
davecessna

G2D Error Mid-flight

Recommended Posts

I am also getting g2d.dll errors midflight. I highly doubt it's hardware issue because my temperatures and voltages are very stable, and all other games work fine. I've noticed if I'm a bit too cavalier changing EZDOK views, I can crash the sim running PMDG 737 NGX with the above mentioned error. Anywho, I hope somebody finds the fix.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

The G2D error has nothing to do with temperatures and voltages.  See the AVSIM CTD Guide, page 32, has possible solutions for this error.  I suspect the dll.xml or exe.xml.  If you moved your the entries in your dll.xml in the folder where your p3d.cfg is located to the dll.xml in the folder where your scenery.cfg is located, that could be the problem as your entries may be corrupted.  There are some entries in the dll.xml that must remain in the dll.xml located in the same folder where your p3d.cfg are located.  Currently, I have the following still located in this folder:

 

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>ObjectFlow_P3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>K:\Prepar3D_v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>as_connect</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp.dll</Path>
  </Launch.Addon>
</SimBase.Document>

 

As stated in the CTD Guide, move your dll.xml to a temporary folder and see if this fixes the problem.  If you have two dll.xml's, move only one, and see if it fixes the problem.  If so, the problem is in that copy of the dll.xml.

 

Best regards,

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this