Hi,

Here's my problem, I've been having the blurry scenery problem. I play around with the settings and things look great for a few minutes then go blurry. Today on a flight from JFK to ATL it happened again. So I set the sliders to a rather extreme setting to the right. My system is pretty decent, everything went fine until I got fairly close to Atlanta and suddenly "fatal error" I looked at the event viewer and the cause of the crash was the infamous g3d.dll. I installed the latest version of FSUIPC since I read that this fixex this particular problem. Possibly I was wrong? I'm considering deleting this troublesome .dll file and seeing if it will install a fresh copy from the DVD. Here's my system info,

 

Hardware AMD 840T quad core processor 2.9 Ghz

Memory 6GB DDR 3 (not quite sure speed)

HDD 1TB SATA

Video Nvida GT 9600

 

Scenery FS Global 2010

Ut USA X

Ut Europe X

Complete package NW US from ORBX plus Northern Rockies

Various add on airports

Any help would be appreciated.

 

Ed Kammerman

Most likely you had some FSX settings set too high. With your system, you won't be able to move your sliders very high. I would save/backup your current fsx.cfg, restart fsx and let the sim rebuild it to the default settings. I know the default settings won't look very good but if it stops your crashes, then you know the culprit. It the fsx.cfg settings are the issue, you can then start moving the sliders forward one more notch, run fsx, and continue doing that until the crashes begin again.

 

In the g3d fix thread, Pete, the developer of FSUIPC and the one who fixed the g3d CTD for most people indicated this does not fix the problem for everyone flying in locations around the world. It just fixed this particular problem everyone seemed to be getting. I was getting all of my g3d crashes in FTX/Orbx scenery PNW area and think most everyone else did too. If I went back to the default scenery and flew again in the PNW, I would not get a crash. Your ctd happened outside of this area so it's new and why I suggest lowering your fsx settings.

 

What OS is installed? Is it 32 bit or 64 bit. The 64 bit OS handles memory better than the 32 bit.

 

Best regards,

Jim

 

Forgot to add you might want to check out the FSUIPC.log in the Modules folder right after you get the crash and maybe provide that to Pete at his website or in an e-mail. It will give you more info about the crash.

100%, Jim. That 9600 is basically a low-end GT 8800 - which Noah used on his PC way back when. This is an FS9 machine, Ed, that's really being pushed to it's limit.

 

To stop blurring, the Global Texture Resolution must be up all the way, and, if you have it in the fsx.cfg - the ...

 

[Main]

FIBER_FRAME_TIME_FRACTION=0.xx

 

...should be above 0.2 in order not to have road and ground textures blurring as you fly over/above them.

Thanks guys. I'll check out what you've told me and update my post. OS Win 7 Home Premium 64 bit. After deleting my FSX config. file and relaunching FSX and letting it rebuild the config. file, I ended up missing a lot of my aircraft.

After deleting my FSX config. file and relaunching FSX and letting it rebuild the config. file, I ended up missing a lot of my aircraft.

 

Yes, you'll have to select yes when asked to trust some aircraft and gauges again. When you select, for instance, the PMDG 737, you'll be asked to trust items again. If you don't then, you will have problems running the aircraft. The FSX.cfg will not cause missing aircraft. Again, this is why many people rebuild their fsx.cfg periodically as it cleans up fsx. Some people uninstall FSX and reinstall it. This is better than that and much faster and easier. Your OS only manages memory for your computer better but it will not allow you to raise your fsx settings very high unless you upgrade.

 

Best regards,

Jim

Hi Jim,

I did all the trusted aircraft, modules and gauges but still missing aircraft and liveries. I'm still wondering about replacing the g3d.dll with a fresh copy

 

Ed

Hi Jim,

I did all the trusted aircraft, modules and gauges but still missing aircraft and liveries. I'm still wondering about replacing the g3d.dll with a fresh copy

 

Ed

 

That would only work if corrupted. The chance of corruption of that dll is slim. Have you ran sfc /scannow to see if you have any corrupted files - http://pcsupport.about.com/b/2009/05/25/sfc-scannow-repairs-windows-files-the-easy-way.htm? That scans your system for corrupted files and fixes them. The g3d.dll is a system file and does not belong to FSX. That's puzzling you are missing aircraft and liveries. Deleting fsx.cfg will definitely not remove any aircraft or liveries. Sounds like you might have accidentally deleted a folder or moved an fsx folder to another directory or drive. Make sure all your aircraft are listed under SimObject\Airplanes. That could be the cause for the g3d.dll error as fsx was looking for an aircraft or gauge or panel or sound file and could not find it where it was suppose to be located. Open up Windows Explorer and click on the drive where FSX is suppose to be located. Then type 'aircraft' or 'panel' or 'texture' in the search box in the upper right corner. It will then find all the aircraft or texture folders throughout your C: drive. If all looks okay and everything is located under SimObjects\Airplanes, then do the same for your other HDD's. If they were accidently deleted, they could be located in the Recycle Bin. Just double-click that icon and see if they are there. If so, click on the file and select Restore.

 

Best regards,

Jim

Hi Jim,

Everything as far as aircraft et al is in it's proper place. It turns out the g3d.dll is in my main FSX folder. Where in my Windows folder does it belong? System or system 32 or sysWOW64. I also rolled back my driver to one from May, that helped alot. Since all you snobs (LOL) think my video card is "cheap" what do you recommend for an upgrade based on my hardware that woul be a good compromise between budget and performance?

 

Ed

Hi Ed,

 

I really apologize for giving you the wrong info. You're right. It is a FSX file that belongs in the fsx folder. The latest I have is dated 9/26/2007 - and it was updated with Acceleration. I still doubt it was your g3d.dll that is the culprit. As I stated before, the G3d.dll was being called by something in FSX and, for some reason, couldn't load it so it crashed FSX. You can put the Acceleration disk in your DVD player and select 'repair' when the options come up and it will reinstall everything including the new g3d.dll. Did you ever find the missing aircraft? A missing gauge or texture could cause this problem as some program in FSX is looking for it and it's not where it is suppose to be.

 

what do you recommend for an upgrade based on my hardware that woul be a good compromise between budget and performance?

 

I'm not an expert on graphics card (well not an expert in computers either!) but there's a GTX 550 on sale at Amazon.com - http://www.amazon.com/EVGA-GeForce-Mini-HDMI-Graphics-01G-P3-1556-KR/dp/B004S5CCP4/ref=dp_cp_ob_e_title_0 for $130 and that's an unbelievable price for a 500 Series video card.

 

Best regards,

Jim

Hi Jim,

Since I made a backup copy of my FSX.config, I restored it and got all my aircraft and liveries back. Unfortunately I don't have the Acceleration Pack. However I did add the missinglibraryalert=1 to my scenery section of my FSX.config file. We'll see what that shows. Thanks for the advice on the card. Another good site for deals is www.buy.com

 

Ed

Unfortunately I don't have the Acceleration Pack.

 

So you have SP1 and SP2 installed instead? SP2 should have the updated g3d.dll. If you can find the sp2.exe, click on it and select 'repair' and it will reinstall the g3d.dll. The missinglibraryalert entry in your fsx.cfg should stop your g3d.dll but will not solve the problem. We were doing that when trying to fix the other g3d.dll crash. But, at least, you won't have a crash as FSX will simply stop and show the error and you can continue on. At least you won't get a crash and you might be able to identify the area that is causing the issue.

 

Best regards,

Jim

Hi Jim,

Date of my g3d.dll is 12/10/07, so I'm guessing it's the most current version, I did the library alert entry for just that reason, to see if it's a scenery issue. Thanks for your help :Money Eyes:

 

Ed

Hi Jim,

Just an update. It turned out to be a combination of scenery settings and that darn culprit HEAT!!! My system is a little over a year old and pretty clean inside. For things to work properly I have to take one side off. The ventilation vents aren't enough.

 

Ed