Jim,

 

Here we go again. ObjectFlow_P3D module is an issue around the Flytampa Dubai rebooted area -only on decent.

I tried flying between YMML and YSSY with ObjectFlow_P3D module disabled - and during decent start towards YSSY a g3d.dll error was encounted.

I then tried disabling all the modules in dll.xml and nothing is working. Same issue even if I remove the dll.xm file from the programdata folder.

I will try enabling everything including ObjectFlow_P3D module.. I did fly with a different livery of pmdg 777-300ER.

Will try the original livery that was tested between VABB and OMDB. Hopefully its just a livery issue.

 

Its so frustrating.. no matter what I do, an issue crops up!!!! I am so tired of testing and just want to be able to fly like I used to

 

M

 

 

I then tried disabling all the modules in dll.xml and nothing is working.

 

When you rename or move the dll.xml AND exe.xml (or rename them), none of those modules will load at startup so you will not be able to use those add-ons.  What you are doing is investigating.  If none of the modules are loaded and you no longer get the crash, then it is one of the modules that is most likely defective and you have to find the culprit.  Mostly the culprit is near the end of the file as those were the last modules installed.  If you know how to edit files, you could cut out several modules and paste them into a temporary Notepad file.  Fix the dll.xml so that it is complete and save and run P3D.  If no crash.  Go to the file where you pasted the other module entries and paste one or two of them to the dll.xml.  Save and try the flight again.  Do this until all of the modules are returned.  That's what I did to find the cause of my StackHash errors.

 

Best regards,

I know that, what I meant was even after removing the dll.xml file, the g2d.dll error kept happening and that's why I feel stuck now.

I will try enabling everything including ObjectFlow_P3D module and fly with the original pmdg 777-300ER livery that was tested between VABB and OMDB.

Hopefully its just a livery issue.

I 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.

Thanks for all your help so far Jim. Something is very screwed up with my current install. I just can't pin point what it is.

If I may piggy back on this dicussion..., I've been having similar issues since doing a fresh install of P3Dv3.3.  I was getting CDT about 30 sec to 10 minutes after loading P3D with the PMDG 737.  I did exactly what Jim recommended - merging the dll.xml and exe.xml files and then deleting said files in the appdata/roaming/lockheed martin/P3Dv3 folder. I made sure there are no duplicate entries in the merged dll.xml and exe.xml files and the spacing between entries is appropriate. I also reinstalled the FSDT add-on manager and that seemed to fix my problem, but the g2d.dll error re-emerged last night.  

 

I am noticing that despite deleting the dll.xml and exe.xml files in the appdata/roaming/lockheed marting/P3Dv3 folder ,both are being reappearing, and it seems Active Sky is the culprit as the following entry keeps getting rebuilt:

 

<Launch.Addon>

    <Name>as_connect</Name>

    <Disabled>False</Disabled>

    <Path>as_srv\as_btstrp.dll</Path>

  </Launch.Addon>

 

I am wondering if having this entry in the dll.xml and exe.xml files in both folder locations might be causing an issue. 

 

Todd

I am wondering if having this entry in the dll.xml and exe.xml files in both folder locations might be causing an issue.

 

I just noticed that too and thanks for bringing it to my attention.  I had the entry in the dll.xml in Roaming and in Program Data for the past two days and I have been running P3D quite a bit since then and I have not had any crashes.  The entry belongs in the AppData/Roaming dll.xml as that is where HiFi decided they want to have it installed.  Perhaps in the future they will move the entry in the dll.xml and exe.xml to the Program Data section.

 

Back on the 23d of June when I was having my StackHash, I found that the entry for ASN was missing in the dll.xml in the Program Data folder so added it.  I had previously consolidated my two dll.xml's and exe.xml's.  My StackHash crashes stopped and I have flown several flights since then without any problems w/ASN.  I have now removed the entry in the dll.xml in the Program Data folder and will allow the one in the AppData/Roaming directory to remain.

 

So, in the case of my StackHash crashes, it was the missing entry that was causing the crashes, not any duplicate entries.

 

Best regards,

Hi Jim,

 

As a last ditch effort, before rebuilding the whole P3D and many many Orbx addons again, please advise how do I clean rebuild the dll file with the following entries..

 

default dll location for fsuipc, orbxflow and PMDG is : C:\Users\MnM\AppData\Roaming\Lockheed Martin\Prepar3D v3

Contents of dll.xml in this location is:

 

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

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.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>FSUIPC 4</Name>

    <Disabled>False</Disabled>

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

  </Launch.Addon>

</SimBase.Document>

 

FSUIPC is uninstalled.

Orbx objectflow has been uninstalled by running moduleinstaller.exe which is located here : D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery

How to do I let the PMDG Interface and RAASPRO entries be rebuilt without having to uninstall and reinstall PMDG 777 - anyone any ideas ??

 

Once the above is known, I will then delete the Prepar3d.cfg, exe.xml and dll.xml files and let the respective programs rebuild it where ever it is supposed to be.

If all fails and I still get the g2d.dll error then will clean install P3D then PMDG and then only after successful test flights, install every other addon.

 

M

 

 

How to do I let the PMDG Interface and RAASPRO entries be rebuilt without having to uninstall and reinstall PMDG 777 - anyone any ideas ??

 

The dll.xml and exe.xml are not default files so they cannot be rebuilt.  The only way to get the entries back is to manually place them into the dll.xml (copy and paste)  or reinstall the product.

 

Best regards,

Ok, have finally found something that seems to have helped.

 

1. I rebuilt w10x64, Installed drivers.

2. Installed IOBIT Driver Booster 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, no scenery. - VABB to OMDB - PASSED.

5. Installed FLYTAMPA  OMDB REBOOTED - Flew PMDG 777 - VABB to Dubai. FAILED - G2d.dll.

I then googled Flytampa and g2d.dll. Found that VC++ may be an issue.

I noticed I had a whole bunch of VC++   from 2005 till 2015.. thanks to IOBIT Driver Booster.

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 Dubai - PASSED!!

 

Will now install every other addon and test thoroughly..

 

Status : Possible solution. DO NOT LET Driver Booster or any Auto driver updater run..Have uninstalled driver booster.

Please keep this thread open as monitoring.

 

 

Status : Possible solution. DO NOT LET Driver Booster or any Auto driver updater run..Have uninstalled driver booster.

 

 

I noticed I had a whole bunch of VC++ from 2005 till 2015.. thanks to IOBIT Driver Booster.

 

Uh, wasn't your problem BEFORE running the driver update program?  Driver Booster (or any Driver Update program) will look at the programs Windows 10 and any other programs, like P3D, FSX, any P3D addon already installed and update them if necessary.  If it saw a Microsoft Visual out of date, it would have updated the component as it is needed for games.  Windows 10 most likely installed the Microsoft Visuals or updated them.  Look in your Add/Remove Programs and then look at Installed Updates and you will see what Windows 10 did (correctly).  I have a feeling you had the 64 bit versions installed as you thought since you are running a 64 bit OS, you need the 64 bit versions.  But P3D and FSX are 32 bit programs and it needs and uses the x86 versions only.  You can leave the 64 bit versions.  Won't destroy anything.

 

Thread will remain open.  Hopefully your problems were fixed by the Driver Booster program.

 

Best regards,

 

Microsoft Visual 2005 w/SP1 and 2008 w/SP1 are required for FSX installations.  Individuals will install products that were developed for FSX and not P3D and try to get them to work in P3D.  Those programs will look for Microsoft Visual 2005 and 2008.  Microsoft Visuals are used to make sure a product is installed properly.  I believe P3D installed Microsoft Visual 2013 during its installation.  In any case it appears Driver Booster was the solution to your problems as you are now able to run P3D w/o a crash. 

I have a few programs installed like 3DMark, PowerDVD, Nero, MS office and a few others like 7zip, acrobat reader etc...but I have a habit of installing all - including system drivers as an administrator. Could this be the cause of the g2d.dll and other errors?

In short, I don't think Driver booster should not really cause any issues right?

 

I was trying to install 3DMark as an administrator and the program warned against it and that's when the penny dropped.

 

Luckily as I have so few programs installed, so is it worth rebuilding windows 10 and installing all drivers and programs as a normal user and only install P3D as an administrator and then run P3D as an administrator always as per the PMDG introduction guide?

 

Cheers,

Mario

 

 

Luckily as I have so few programs installed, so is it worth rebuilding windows 10 and installing all drivers and programs as a normal user and only install P3D as an administrator and then run P3D as an administrator always as per the PMDG introduction guide?

 

The g2d.dll is used for displaying text in your sim.  I would suspect the issue for this error is somewhere in your dll.xml or exe.xml.   The error is not all that common but the CTD Guide, on page 31, has a list of possible solutions I found around the Internet, including AVSIM. 

 

Installing P3D into a non-default folder, like K:\Prepar3D v3 might work but never ever a guarantee.  Every time I have had a crash and could not fix it, I would reinstall Windows and then P3D and then slowly install the add-ons. Always worked but again, no guarantee.  Whenever I reinstalled the add-ons it was a slow process.  Many of my add-ons never made it back and maybe that's the reason my problem was fixed.  I had a bad add-on.

 

Best regards,

Just an update, have rebuilt windows and installed all the software including P3D as a normal user but am running p3d.exe as an administrator. Have installed the T7 but can't activate it yet as the license has expired. PMDG will reset my license once they've resolved manual activation issues at their end. So going to wait another week I guess. 

Update - Have activated the T7, installed all of the P3Dv3 ready Orbx Products only and the g2d.dll errors are back!

1. Will move the p3d.cfg, DLL.xml from the %appdata% directory,

2. move dll.xml and exe.xml file from the programdata\lockheed martin folder and try a flight.

If no errors then will leave p3d.cfg as stock and fly a flight followed by introducing exe.xml then each of the entries for dll.xml.

 

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

 

 

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

 

How will a 64-bit sim have anything to do with this? I don't see anything in your problems that will automatically be cured by a 64-bit simulator.

 

Cheers!

Luke