I wanted to make mention of this error--don't know if my observation has been mentioned here before. Like many others, I would get the occasional g3d.dll error, usually when I was running with Tileproxy. An annoyance when it happened (usually mid flight for me) but I learned to live with it. On average I was seeing the error after every two hours or so of flight. Anyway, I recently purchased a couple of aircraft that hit my performance. The performance hit was enough to keep Tileproxy from refreshing the textures as the aircraft flew along. So I decided to lower my framerate lock to a tad below the lowest framerate observed in these two aircraft.

 

To make a long story short, I've flown about ten hours since, over a variety of scenery areas, and not one g3d.dll error. For me too much to be a coincidence. So my thought--exceeding the texture update bandwidth, whatever the system, might be a trigger for these errors even if the scenery area is "good". If this has been mentioned before, sorry--I haven't read many of the threads concerning this issue so I guess I would be the odd man out. If it hasn't been mentioned and all else has failed trying to rid your FSX sessions of this error--give my idea a try, lowering the fps lock until you either see (or don't see) an improvement with this issue. So far I am very pleased with what I've seen.

 

Regards,

 

John

I believe the newer FSUIPC has the ability to trap that error and prevent the sim from crashing. I don't know if you are running FSUIPC but I've had my limiter set to unlimited in orbx YBBN and would get that error every time within 2 minutes. When FSUIPC (the newer versions) were installed it never G3d.dll CTD on me. There was a log that showed the trapped G3D.dll crash prevention in FSUIPC.

The latest version of FSUIPC stops many of these errors. Are you using it?

Agreed FSUIPC should be marked as a must have for any FSX installation, and kept up to date.

I have FSUIPC and it DOES "trap" the g3d erros and the guy that made FSUIPC is a genious!

The latest version of FSUIPC stops many of these errors. Are you using it?

 

I did recently install FSUIPC, but the unregistered version. Does the unregistered version trap these errors, or just the registered version?

 

Regards,

 

John

I believe it does but you should realy consider purchasing a registered copy of it. It can setup and calibrate any and all of your controllers for each aircraft you have for instance. Plus it adds so much more to FSX that you never knew you needed. PLUS you would be supporting a remarkable FS God named Pete Dowson who has helped change and fix FSX for the masses. His utility is used by so many 3pd to interface with FSX.

Just to add to my last post. I think we need all the dedicated developers we can get like Pete Dowson doing what they do for our hobby. They are the people trying to fix FSX and make it more stable and flyable for us. Microsoft dropped the flightsim community and support for FSX. So these peoe are all we have left to keep our hobby alive at this point. We have been able to break in and fix some things within the FSX code without actually changing the code because Microsoft has it locked up. Developers like A2A and PMDG have expanded on and made modules within their coding to provide external fixes and enhanced characteristics of their products. When you think about it, it's realy remarkable what can be done inspite of a locked code.

Anyways I'll get down of the soap box now...

Just to add to my last post. I think we need all the dedicated developers we can get like Pete Dowson doing what they do for our hobby. They are the people trying to fix FSX and make it more stable and flyable for us. Microsoft dropped the flightsim community and support for FSX. So these peoe are all we have left to keep our hobby alive at this point. We have been able to break in and fix some things within the FSX code without actually changing the code because Microsoft has it locked up. Developers like A2A and PMDG have expanded on and made modules within their coding to provide external fixes and enhanced characteristics of their products. When you think about it, it's realy remarkable what can be done inspite of a locked code.

Anyways I'll get down of the soap box now...

 

And don't forget us freeware developers. My Landclass Assistant program and Soft Horizons textures have been downloaded by thousands of members, and I still hear from members who use them. And I was inspired by countless other freeware developers who had bigger contributions than mine--my contribution is small compared to the group as a whole. That said, Pete Dowson is a stand out, his work has the respect of just about everyone I know. If his software is the cure to my g3d.dll errors and not my own adjustments, it just adds to the unpayable debt I owe him for his work.

 

John

Your right about that THANK YOU TO ALL THE FREEWARE DEVELOPERS ASWELL!!! I personally love the work and dedication to this hobby that you have given to the community. I one made aircraft in a program called Flight Sim Flight Shop for I believe it was FS5. I made the Berkut, Lancair 320 and 360, the Cirrus VK 30 and a Gruman Tiger. I think I was one ov the first to make a non functional vc. I believe they are still downloadable in this sight someware.

Does the unregistered version trap these errors, or just the registered version?

 

It works with the registered or unregistered version.

 

Best regards,

Jim

Back to my original post--I have looked at my FSUIPC logs and they don't show any g3d.dll crashes captured. Do you have to enable something for these to appear in the logs, and if so, what options? I've flown about fourteen hours since I made my fps lock change, but that time closely coincides with my install of FSUIPC. I'd like to know if FSUIPC is what is making the difference.

 

Regards,

 

John

Do you have to enable something for these to appear in the logs, and if so, what options?

 

If you look at your FSUIPC.log you should see something like the following:

 

250 G3D.DLL fix attempt installed ok

250 SimConnect_Open succeeded: waiting to check version okay

250 Trying to use SimConnect Acc/SP2 Oct07

1685 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

1685 Initialising SimConnect data requests now

1685 FSUIPC Menu entry added

88640 Starting everything now ...

89654 Advanced Weather Interface Enabled

243393 Sim stopped: average frame rate for last 156 secs = 27.9 fps

248307 System time =

248307 *** FSUIPC log file being closed

Average frame rate for running time of 156 secs = 27.9 fps

G3D fix: Passes 32510, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 74 Allocs, 74 Freed

 

If it finds anything while you are flying and traps the g3d.dll error, it will tell you how many null pointers, bad pointers and separate instances the g3d.dll error was fixed so FSX would not crash.

 

Best regards,

Jim

I don't see any mention of this line: 250 G3D.DLL fix attempt installed ok.

 

I'll check all the logging options and see if it appears.

 

John

Then you do not have the latest FSUIPC.dll installed.

 

Best regards,

Jim