Jump to content
Sign in to follow this  
Mike_CFII_MEL

g3d.dll crashes in prepar3d - is the problem finally fixed?

Recommended Posts

Hi,

 

Looks like Pete Dowson found a way to trap and prevent P3D from crashing from the dreaded g3d.dll error. The fix is in his latest offering of FSUIPC (ver. 4.827) and is available for download at his website. Seems its the same fix that was required for FSX.

 

********* FSUIPC4, Version 4.825 by Pete Dowson *********

User Name="REDACTED"

User Addr="REDACTED"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside Prepar3D on Windows 7

Module base=120F0000

687 System time = 25/04/2012 17:36:22

733 FLT UNC path = "\\MEGATRON\Users\stefan\Documents\Prepar3D Files\"

733 Trying C:\Prepar3D\Modules\SimConnectP3D.dll

749 Found it: trying to connect

765 FS UNC path = "C:\Prepar3D\"

1108 LogOptions=00000000 00000001

1108 Wind smoothing fix is fully installed

1108 G3D.DLL fix attempt installed ok

1108 SimConnect_Open succeeded: waiting to check version okay

1108 Trying to use SimConnect Prepar3D

4009 Running in "Lockheed Martin® Prepar3D®", Version: 1.3.3708.0 (SimConnect: 1.3.0.0)

4009 Initialising SimConnect data requests now

4009 FSUIPC Menu entry added

4041 C:\Prepar3D\FLIGHTS\OTHER\Prepar3D.FLT

4041 C:\Prepar3D\SimObjects\Airplanes\Mooney_Bravo\Mooney_Bravo.AIR

48204 System time = 25/04/2012 17:37:09, Simulator time = 11:00:02 (15:00Z)

48267 Aircraft="Mooney Bravo With G1000"

48891 Starting everything now ...

50186 Advanced Weather Interface Enabled

320691 *** G3D bad pointer trapped and crash prevented ***

1250972 *** G3D bad pointer trapped and crash prevented ***

6034634 Sim stopped: average frame rate for last 5867 secs = 29.8 fps

7884509 *** G3D bad pointer trapped and crash prevented ***

7964522 *** G3D bad pointer trapped and crash prevented ***

8173532 Sim stopped: average frame rate for last 2126 secs = 30.0 fps

8185934 System time = 25/04/2012 19:52:47, Simulator time = 09:13:34 (22:13Z)

8185934 *** FSUIPC log file being closed

Average frame rate for running time of 8010 secs = 29.8 fps

G3D fix: Passes 1399489, Null pointers 0, Bad pointers 8, Separate instances 4

Memory managed: 3313 Allocs, 3313 Freed

********* FSUIPC Log file closed ***********


Former Beta Tester - (for a few companies) - As well as provide Regional Voice Set Recordings

       Four-Intel I9/10900K | One-AMD-7950X3D | Three-Asus TUF 4090s | One-3090 | One-1080TI | Five-64GB DDR5 RAM 6000mhz | Five-Cosair 1300 P/S | Five-Pro900 2TB NVME        One-Eugenius ECS2512 / 2.5 GHz Switch | Five-Ice Giant Elite CPU Coolers | Three-75" 4K UHDTVs | One-24" 1080P Monitor | One-19" 1080P Monitor | One-Boeing 737NG Flight Deck

Share this post


Link to post
Share on other sites

Grateful for Pete for putting this into FSUIPC for Prepar3D despite his initial reluctance. I share his sentiments though. I wish this was addressed at the core of the sim and there wasn't a need to depend on a workaround to stop a sim that is actively in development from crashing. I'd understand if this was a new error but G3D crashes have been around in FSX forever and just carried right over into this one.


ASUS ROG STRIX Z390-E GAMING / i9-9900k @ 4.7 all cores w/ NOCTUA NH-D15S / 2080ti / 32GB G.Skill 3200 RIPJAWS / 1TB Evo SSD / 500GB Evo SSD /  2x 3TB HDD / CORSAIR CRYSTAL 570X / IPSG 850W 80+ PLATINUM / Dual 4k Monitors 

Share this post


Link to post
Share on other sites

That's great news. I repeated some of my flights in FTX PNW Seattle area where I usually experienced CTDs after 5 min or so. After I had installed the new FSUIPC I was able to fly 2 hours in Seattle area (high settings, fps 15-25). Even with heavy clouds and dusty weather settings (4096 REX textures) the sim kept stable.

 

I would say the problem is fixed.

 

Harry


- Harry 

i9-13900K (HT off, 5.5 GHz, Z690) - 32 GB RAM (DDR5 6400, CAS 34), RTX 3090Windows 11 Pro (1TB M.2) - MSFS 2020 (MS Store, on separate 4TB M.2).

 

 

 

Share this post


Link to post
Share on other sites

Hey Mike, I have been away from the FS side for quite a while, how do you know it is a g3d.dll error? Does it come up when it crashes as so? Last night I got an "Prepar3d.exe has stopped working error," but it didn't explicitly say that it was a g3d error.


Tyson Rose

Share this post


Link to post
Share on other sites

If you check event viewer you can check the crash reason.

 

Paul


-Paul-

Share this post


Link to post
Share on other sites

If you have any parking without a path link to aprons runways etc the scenery will crash by g3d.dll. Try to inspect your scenery .

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  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...