Urrrrgh.. Can't wait for a 64bit version of Prepar3d v4 so that all addons can be rebuilt from scratch in a correct fashion !!!

Wrong! Most addons will be just recompiled, and NOT newly written from scratch. 64Bit will increase VAS. Not more, not less

Installed P3Dv3.3.5.17625, all orbx for P3Dv3.3 products and Flytampa OMDB rebooted 2.4 for P3Dv3.3

 

Ok, some successful outcome overnight..

by default the following dll.xml files were created in P3D -

 

1. appdata folder - DLL.xml containing: 

 

<?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>FSUIPC 4</Name>

    <Disabled>False</Disabled>

    <Path>Modules\FSUIPC4.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>PMDG Interface</Name>

    <Disabled>False</Disabled>

    <Path>PMDG\DLLs\PMDG_Interface.dll</Path>

    <DllStartName>module_init</DllStartName>

    <DllStopName>module_deinit</DllStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>RAASPRO</Name>

    <Disabled>False</Disabled>

    <Path>.\RAASPRO\RAASPRO.dll</Path>

    <DllStartName>module_init</DllStartName>

    <DllStopName>module_deinit</DllStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>ObjectFlow_P3D</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>D:\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>

  </Launch.Addon>

</SimBase.Document>

 

2. Programdata folder had a dll.xml file with:

<?xml version="1.0" encoding="Windows-1252"?>

 

<SimBase.Document Type="AceXML" version="3,0" id="dll">

    <Descr>AceXML Document</Descr>

    <Filename>dll.xml</Filename>

    <Launch.Addon>

        <Name>TargetInfo</Name>

        <Path>Gauges\TargetInfo.dll</Path>

    </Launch.Addon>

    <Launch.Addon>

        <Name>Fury_1500</Name>

        <Path>Gauges\Fury_1500.dll</Path>

        <DLLType>PDK</DLLType>

    </Launch.Addon>

</SimBase.Document>

 

I have managed to create one dll.xml file in C:\ProgramData\Lockheed Martin\Prepar3D v3 witht he following contents:

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="AceXML" version="3,0" id="dll">

    <Descr>AceXML Document</Descr>

    <Filename>dll.xml</Filename>

  <Disabled>False</Disabled>

  <Launch.ManualLoad>False</Launch.ManualLoad>

    <Launch.Addon>

        <Name>TargetInfo</Name>

        <Path>Gauges\TargetInfo.dll</Path>

    </Launch.Addon>

    <Launch.Addon>

        <Name>Fury_1500</Name>

        <Path>Gauges\Fury_1500.dll</Path>

        <DLLType>PDK</DLLType>

    </Launch.Addon>

  <Launch.Addon>

    <Name>FSUIPC 4</Name>

    <Disabled>False</Disabled>

    <Path>Modules\FSUIPC4.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>PMDG Interface</Name>

    <Disabled>False</Disabled>

    <Path>PMDG\DLLs\PMDG_Interface.dll</Path>

    <DllStartName>module_init</DllStartName>

    <DllStopName>module_deinit</DllStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>RAASPRO</Name>

    <Disabled>False</Disabled>

    <Path>.\RAASPRO\RAASPRO.dll</Path>

    <DllStartName>module_init</DllStartName>

    <DllStopName>module_deinit</DllStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>ObjectFlow_P3D</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>D:\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>

  </Launch.Addon>

</SimBase.Document>

 

The above has helped with flights between OOMS and OMDB..Even after installing OMDB rebooted, no issues.

ORBX YMMLv3 to stock P3D YSSY results in a CTD with the following errors..

 

1.

 

Log Name:      Application

Source:        Application Error

Date:          8/18/2016 8:47:18 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-PANCNE2

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: 0x2204

Faulting application start time: 0x01d1f93d4d14d418

Faulting application path: D:\Prepar3D v3\Prepar3D.exe

Faulting module path: D:\Prepar3D v3\g2d.dll

Report Id: 218a9180-6531-11e6-a9df-d017c2d321d0

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-08-18T10:47:18.194613100Z" />

    <EventRecordID>7095</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-PANCNE2</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>2204</Data>

    <Data>01d1f93d4d14d418</Data>

    <Data>D:\Prepar3D v3\Prepar3D.exe</Data>

    <Data>D:\Prepar3D v3\g2d.dll</Data>

    <Data>218a9180-6531-11e6-a9df-d017c2d321d0</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

 

2.

 

Log Name:      Application

Source:        Application Error

Date:          8/18/2016 8:37:05 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-PANCNE2

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: 0x1894

Faulting application start time: 0x01d1f939d473e6e9

Faulting application path: D:\Prepar3D v3\Prepar3D.exe

Faulting module path: D:\Prepar3D v3\g2d.dll

Report Id: b42dc6f1-652f-11e6-a9df-d017c2d321d0

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-08-18T10:37:05.218112500Z" />

    <EventRecordID>7093</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-PANCNE2</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>1894</Data>

    <Data>01d1f939d473e6e9</Data>

    <Data>D:\Prepar3D v3\Prepar3D.exe</Data>

    <Data>D:\Prepar3D v3\g2d.dll</Data>

    <Data>b42dc6f1-652f-11e6-a9df-d017c2d321d0</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

 

Anyone any ideas?

Successful from Orbx YMML v3 to stock P3D YSSY. Have reduced my settings to basic in addition to one dll.xml file in the program data folder as per my earlier post.

 

P3D Settings below:

 

Those settings are really bad for your system.  Too bad you have to pretty much turn off the details of P3D to use the simulator.  I hope to have an AVSIM P3D Configuration Guide, authored by Rob Ainscough, within the month of August.  Stay tuned!

 

Best regards,

HI Jim,

 

That didn't work after I installed Flytampa YSSY with LITE pack (1024 textures). Orbx YMML V3 to Flytampa YSSY results in CTD right above a ridge of snow covered mountains. Same on the way back to Melbourne over the same ridge if mountains and then flying in towards Melbourne eastern suburbs.

The same error all the time.. Just the faulting process id keeps changing.

Faulting module name: g2d.dll, version: 3.3.5.17625, time stamp: 0x5758bbc2

Exception code: 0xc0000005

A flight from Flytampa OMDB to OOMS was successful. Will try a return flight to OMDB and report back how that goes.

 

With reference to my system, my bios settings are stock - most settings are set to Auto as I have no clue how to properly setup the bios besides the XMP profile for my ram and setting my PCIE bus as GEN3 as its a GTX1080. HT has been disabled as it made no difference with it on.

I ran 3DMARK the latest pro version and all tests run fine.

As for the P3D cfg it is left as stock. I have even turned off all options in the control panel of all ORBS airports and regions. Also turned off all options apart from the wind socks animation for Flytampa OMDB and YSSY !! 

 

You are absolutely right - "Those settings are really bad for your system.  Too bad you have to pretty much turn off the details of P3D to use the simulator.  I hope to have an AVSIM P3D Configuration Guide, authored by Rob Ainscough, within the month of August.  Stay tuned!" - can't wait.

I will try and touch base with Rob Ainscough for his thoughts.. I am thoroughly baffled..

 

Regards

M

 

 

Faulting module name: g2d.dll, version: 3.3.5.17625, time stamp: 0x5758bbc2

 

Hi again Mario,

 

According to the AVSIM CTD Guide, the G2D.dll fixes are -

 

G2D.dll - This module handles plain text messages, like the frame rate counter and those other plain text messages you see periodically while running any simulator and the plain text words in the respective Menu, like the words Options, View, etc. There may be something corrupted in your dll.xml which loads menu items. Possible fixes –

• Rebuild the sim’s config, as appropriate (moving or renaming the config and then restarting the application).
• Uninstall/reinstall video card drivers or go back to previous version. Make sure drivers are not ‘beta’.
• Do not disable ORBX/FTX, GEX, and/or UTX entries via the scenery.cfg. Use the appropriate interface utility to enable/disable features in these programs.
• Move the dll.xml to a temporary folder and see if this fixes the problem. If so, there is a module in the dll.xml that is causing the problem.

These "fixes" come from searching the Internet and all of the FS websites for this error.  Other members had the problem and were able to fix the problem with one of the fixes.

 

Benchmark programs like 3DMark have little bearing on P3D and FSX usage.  So what if your system has high fps running 3DMark?  Does it mean P3D or FSX is supposed to run with high fps too?  Unlikely.  P3D and FSX are not modern software programs and they are plagued with addons.  LM is working on increasing FPS and VAS usage and I think they did an excellent job with v3.3.5.  If you just run a "naked" P3D w/o any addons, it should run great.  No G2D errors.  No NTDLL errors.  No OOM's.  Then you add addons and things go downhill fast.  So blame the addons.  Not P3D.  LM did not make any of the addons.  If the addon was developed and then tested by LM techs and certified, then I can understand your concerns.  But the LM techs did not.

 

If I get an addon that starts crashing soon after I install it to P3D, I'll uninstall it or try to figure out a way to get it to work in P3D.  I know P3D is working perfectly but why is the program crashing after I install the addon?  Sometimes the addon has just too many features or eye-candy.  I can live without some of the features so I'll remove them and see if that works better.  If I cannot get it to work, then I'll look at the addon's website and forums to see if they have a solution or suggestions from other users.

 

Hopefully you can find out which addon is causing you the blues. 

 

Best regards,

Jim

Hey Jim,

 

Just to be clear, I am in no way blaming P3D or any vendor at this stage.. Its just my ###### luck I guess.

 I just can't figure out this problem. The errors are back to square one, nearly every flight irrespective of region ends in a CTD with a G2D.dll error just as decent is about to begin.. 

I can't understand how a combination of unaltered P3D - cfg file with basic P3D settings, P3Dv3 updated addons from ORBX and Flytampa once installed results in these bloomin g2d.dll errors..

I give up !! Am depending on good old FSUIPC auto saves. I just reload the last saved flight and continue till landing.

 

On the other hand, I was having a look at what files are in the Appdata folder and am baffled to see a prepar3d.cfg text document that is identical in content to the Prepar3d - CFG file.. 

 

I tried deleting the prepar3d.cfg text document and it just gets recreated.. I have no idea if this is correct and I have just gone into paranoia of doubting everything... please see below:

 

 

Regards,

M

Ps. Please let me know once the AVSIM P3D Configuration Guide is ready.. can't wait to have a read and try it out..

 

 

I tried deleting the prepar3d.cfg text document and it just gets recreated..

 

The text file is created if there's a crash.  Microsoft intended to have everyone send it along with your scenery.cfg to Microsoft techs so they could diagnose the reason for the crash.  Not sure if LM does the same.

 

Best regards,

Thanks Jim, that explains it.

Ok, just my lucky day I guess but I might have finally stumbled upon something. 

1. I went through the AVSIM_Lockheed_Martin_Prepar3D_Guide and used scruffduckSoftware's Simple Airport Scanner to delete duplicate afcad airports which I posted here http://www.orbxsystems.com/forum/topic/121042-duplicate-orbx-ade-files-found/#comment-1088774 as they were Orbx related. But it made no difference - the g2d.dll errors prevailed.

2. I then read somewhere to try and move the LOD Radius slider to the left most. Still no joy. Finally I decided to move it to the extreme right to MAX.. What could possibly get any worse - right !!! Wrong ! it helped. G2d.dll errors gone !!!!!! For the life of me I can't figure how.. I did overclock my 6700K to 4.6Ghz using Asus Aisuite 3. Maybe that helped - who knows.

3. I flew Flytampa OMDB to OKBK and return, YMML to YSSY and return no g2d.dll CTD. I tried to increase the FSUIPC autosave interval to 480 seconds from 60 second - Bang!! g2d.dll CTD after a few seconds. I reverted that setting back to 60 seconds and P3D was stable again.

 

So moral of the story.. the combination of Orbx Scenery, PMDG T7, FSUIPC and P3Dv3.3.5 are a disaster. There is no way of knowing where to look incase a g2d.dll error pops up.

 

I will now fly a few more flights around KSFO and KJFK.. (other trouble areas) and report back.

If all good, will then install REX stuff - REX Ess Plus and REX TD+Soft Clouds and see how that goes.

 

Last, will post all my settings if its still working ok.. Wish me luck.. I am still looking for that blue moon out there.. :-P

 

Regards,

M

Too good to be true... LOD Radius setting makes no difference today. Flying YBBN to YPPH and have had 2 CTDs with g2d.dll already. Tried to move the LOD Radius setting tot he left to Ultra and still CTD..

 

1st CTD

 

Log Name:      Application

Source:        Application Error

Date:          9/16/2016 9:30:57 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-PANCNE2

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: 0x1e1c

Faulting application start time: 0x01d2100a665e9ac8

Faulting application path: D:\Prepar3D v3\Prepar3D.exe

Faulting module path: D:\Prepar3D v3\g2d.dll

Report Id: 089c816f-7c01-11e6-aa2f-d017c2d321d0

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-09-16T11:30:57.270347600Z" />

    <EventRecordID>12239</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-PANCNE2</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>1e1c</Data>

    <Data>01d2100a665e9ac8</Data>

    <Data>D:\Prepar3D v3\Prepar3D.exe</Data>

    <Data>D:\Prepar3D v3\g2d.dll</Data>

    <Data>089c816f-7c01-11e6-aa2f-d017c2d321d0</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

 

2nd CTD

 

Log Name:      Application

Source:        Application Error

Date:          9/16/2016 9:51:14 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-PANCNE2

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: 0xcd8

Faulting application start time: 0x01d2100de3b8ea11

Faulting application path: D:\Prepar3D v3\Prepar3D.exe

Faulting module path: D:\Prepar3D v3\g2d.dll

Report Id: de5ed9be-7c03-11e6-aa2f-d017c2d321d0

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-09-16T11:51:14.892315100Z" />

    <EventRecordID>12241</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-PANCNE2</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>cd8</Data>

    <Data>01d2100de3b8ea11</Data>

    <Data>D:\Prepar3D v3\Prepar3D.exe</Data>

    <Data>D:\Prepar3D v3\g2d.dll</Data>

    <Data>de5ed9be-7c03-11e6-aa2f-d017c2d321d0</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

The only way you are going to figure this out is to investigate it yourself (which you have been doing).  The AVSIM CTD Guide provides the solutions I found across the Internet that worked for some.  You have to ask yourself, "did this occur with P3D v3.3.5 installed and no add-on's?"  This is why the guide wants to take you back to the default settings w/o completely uninstalling/reinstalling everything (moving the p3d.cfg, dll.xml (there are two), exe.xml (there are two), and scenery.cfg to a temporary directory and letting the sim rebuild the p3d and scenery configs).  The dll.xml and exe.xml are not default files for P3D so they will not be rebuilt.  I still think high settings are the culprit.  If the g2d errors go away, then it will be easy to move the dll.xml and exe.xml (located in two different locations) back.  Then, if the crashes occur again, you know it is a module in the dll.xml or exe.xml.  It will then be super easy to figure out which one is causing the problem.

 

Best regards,

Jim

Hey Jim, 

 

Slight progress. I upgraded client, scenery and content to P3Dv3.4 successfully by following the P3D Guide carefully on thursday night. I also reinstalled ORBX Global. I let P3D load with a clean new cfg file. I changed the settings to what I wanted but left the Scenery Objects at P3D's default of Normal and special effects at the mid setting. 

 

Today, I successfully completed a flight in the T7 from Flytampa yssy to ORBX ymml V3. 

Rebooted the computer and completed another flight back to YSSY.

 

The sim was smoother.. You may have a point about high settings or maybe LM fixed something in this version.

Will test some more flights tomorrow.. before I install REX Texture, Ess Plus and FSDT GSX and last FSDT Airports. Will keep flying test flight in between and update this thread

 

M

Hi Mario,

 

I hope it continues to work for you.

 

Best regards,

Jim

Update: I installed FSDT GSX and successfully completed 14 flights (below) since my last post. Am happy to report that I did not experience a single crash or hiccup.

YPDN(ORBX) to YPPH and return

YPDN to YSSY (Fly Tampa) and return

NZAA(ORBX) to WSSS(ImagineSim) and return

YPAD to YPDN and return

YPAD to YMML (ORBX) and return

NZAA to OMDB(Fly Tampa) and return

NZAA to YMML and return

 

Here are my settings:

 

I think it may have been a combination of installing three files - client, scenery and content of P3Dv3.4 by following the P3D Guide and keeping my settings at just what I need has finally resolved the g2d.dll errors for now..

Have to install a few more airports,  REX TD and ESS Plus. Will report back later during October.

 

Cheers,

M