Sign in to follow this  
martinlest2

G3D.DLL CTDs in FS9

Recommended Posts

The AVSIM CTD pdf guide says:

 

G3D.dll  – The  g3d.dll  is  indicated  as  the  faulting module  in  the  crash  report.  For most users,  this will be  fixed by  installing  the most  recent  version of  the FSUIPC Utility. The freeware  or  payware  version will  fix most  of  these CTD’s.

 

I have the latest (registered) version - FS9 - in what way will it help fix these CTDs - do I have to 'do' something, in addition to having FSUIPC installed? There is no further mention of G3D.dll..

 

Thanks.

Share this post


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

Not sure the fs9 version of the fsuipc.dll traps the g3d.dll error.  You will have to look into the fsuipc log and it will tell you whether it is actively trapping the error or not (plus the number of times it trapped the error).  I recall a recent post where the developer of fsuipc stated it is no longer required to trap the g3d error in P3D as Lockheed fixed the problem.  In any case it is not actively showing the g3d fix being installed.  If you are having g3d errors in fs9 and your fsuipc log is not showing the g3d fix being installed, then I know of no solutions other than reformatting your system, reinstalling Windows and then fs9.  I strongly believe an addon is incompatible with the version of the g3d.dll installed for fs9.

 

Best regards,

Share this post


Link to post
Share on other sites
... reformatting your system, reinstalling Windows and then fs9

 

 

that is not going to happen  :wink:

 

I did look at the FSUIPC log but didn't see anything. What does the entry look like, has anyone got an example? What is it that FSUIPC 'catches' in FSX? How does it work there?

 

Thanks

Share this post


Link to post
Share on other sites

Here is my most recent log from the latest FSUIPC for FSX:
 

********* FSUIPC4, Version 4.949 by Pete Dowson *********
fsx.exe version = 10.0.61637.0
Reading options from "K:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=52CD0000
User Name=
User Addr=
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
31 System time = 04/03/2016 15:35:03
31 FLT path = "C:\Users\JimY\Documents\Flight Simulator X Files\"
31 ------ Module Version Check ------
31 acontain.dll: 10.0.61637.0
31 api.dll: 10.0.61637.0
31 controls.dll: 10.0.61637.0
31 fs-traffic.dll: 10.0.61637.0
31 G3D.dll: 10.0.61637.0
31 sim1.dll: 10.0.61637.0
31 visualfx.dll: 10.0.61637.0
31 weather.dll: 10.0.61637.0
31 window.dll: 10.0.61637.0
31 ----------------------------------
62 Trying to connect to SimConnect Acc/SP2 Oct07 ...
62 FS path = "K:\FSX\"
171 ---------------------- Joystick Device Scan -----------------------
171 Product= Cyborg X
187 Manufacturer= Saitek
187 Vendor=06A3, Product=0836 (Version 1.48)
187 Serial Number=
187 -------------------------------------------------------------------
187 LogOptions=00000000 00000001
187 -------------------------------------------------------------------
187 ------ Setting the hooks and direct calls into the simulator ------
187 --- CONTROLS timer memory location obtained ok
187 --- SIM1 Frictions access gained
187 ASN active function link set
187 --- FS Controls Table located ok
187 --- Installed Mouse Macro hooks ok.
187 Wind smoothing may be by ASN, not FSUIPC, if it is running
187 Will switch smoothing action when ASN starts/stops
187 --- G3D.DLL fix attempt installed ok
187 --- All links checked okay
187 -------------------------------------------------------------------
187 SimConnect_Open succeeded: waiting to check version okay
187 Trying to use SimConnect Acc/SP2 Oct07
764 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
764 Initialising SimConnect data requests now
764 FSUIPC Menu entry added
780 K:\FSX\FLIGHTS\OTHER\FLTSIM.FLT

 

 

And here it is from an earlier version (note at the bottom of the report it showed what the fix did:

 

 

********* FSUIPC4, Version 4.936 by Pete Dowson *********
Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=6A3A0000
User Name=
User Addr=
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
16 System time = 02/12/2014 16:48:27
16 FLT path = "C:\Users\JimY\Documents\Flight Simulator X Files\"
31 Trying to connect to SimConnect Acc/SP2 Oct07 ...
31 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"
125 LogOptions=00000000 00000001
125 SIM1 Frictions access gained
125 Wind smoothing fix is fully installed
125 G3D.DLL fix attempt installed ok
125 SimConnect_Open succeeded: waiting to check version okay
125 Trying to use SimConnect Acc/SP2 Oct07
3292 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
3292 Initialising SimConnect data requests now
3292 FSUIPC Menu entry added
3307 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT
3307 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

5006930 Monitor IPC:024C (S32) = 983068
5016930 Monitor IPC:024C (S32) = 980636
5026992 Monitor IPC:024C (S32) = 981236
5037038 Monitor IPC:024C (S32) = 963136
5047085 Monitor IPC:024C (S32) = 988788
5056180 Sim stopped: average frame rate for last 4817 secs = 35.2 fps
5063340 System time = 02/12/2014 18:12:51, Simulator time = 17:12:13 (23:12Z)
5063340 *** FSUIPC log file being closed
Average frame rate for running time of 4817 secs = 35.2 fps
G3D fix: Passes 63095, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 2017 Allocs, 2017 Freed

 

 

Best regards,

Share this post


Link to post
Share on other sites

Thanks Jim. A pity if FSUIPC can't do this for FS9. I will have a look at the log again anyway.

 

Martin

Share this post


Link to post
Share on other sites

I did not know the g3d.dll error was a problem in fs9.  You are the first to bring it up as far as I know.   Perhaps if you contact Pete, the developer of FSUIPC, he might set up a trap for FS9 too.  I do not know how p3d was able to fix this problem as p3d is FSX with some updates.

 

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