hello everyone,i am frequently getting a g2d.dll error that stops fs9,it also says that the files panel,scenery cfg and dxdiag are in the report.is this a bug or is there a fix anyone knows of.would appreciate any opinions.thanks.

My bet would be that you need to upgrade your video drivers but without knowing your system I can't say for sure. It would help if you could provide the following information:Operating SystemProcessor SpeedRAMVideo CardVideo RAMDriver VersionDX9 VersionAll these items can be obtained by running the DXDIAG program. Just select "Run" fromt the Start menu, type "DXDIAG" and hit Enter.

My bet would be that you need to upgrade your video drivers but without knowing your system I can't say for sure. It would help if you could provide the following information:Operating SystemProcessor SpeedRAMVideo CardVideo RAMDriver VersionDX9 VersionAll these items can be obtained by running the DXDIAG program. Just select "Run" fromt the Start menu, type "DXDIAG" and hit Enter.

hi,i should have added that,wasnt thinking,they areos=xp homep4-2.41024 ramradeon 9600pro128mb3.10 driversdx 9brunning dxdiag shows no problems,i just reformatted a couple of days ago,it was also happening before.i also run as2004,radar contact,alert pro.is it possible to get the dll off one of the disks and reinstall it.thanks

Tony:G2d.dll is found in your Windows/System32 folder. I too have had CTD's displaying this dll file along with g3d.dll...in short, a duplicate of what you experienced. I have often wondered just what the g2 & g3d.dll files reference but have not found anyone who has the answer. Maybe someone will chime in who knows.I have the same video card as you, running the 3.9 Omega drivers. I have also had CTD's referencing a dll file within DX9b, but no solution. I suspect somewhere in my FS I have a scenery file that is triggering my CTD's, and have started a backward progression of elimination to try and find which one it is. Recently removed FS Genesis Beta landclass that was developed for FS2K2 and the Genesis mesh files for the White, Green and Adirondack mountains. I principly fly in New England, NY & PA. Since doing so, my CTD's have dramatically been reduced. YMMV.

I did a search on g2d.dll and g3d.dll on my system (XP) and they are in the Flight Simulator 9/Modules folder and not in the System32 folder. The product name for both of the modules is 'Flight Simulator 2004' created on 6/12/2003 (June), so they are not system files.I have never had that particular error, so I'm wondering why they are in your System32 folder. Maybe that has something to do with it.

These handle 2D and 3D rendering tasks respectively. Since the machine specs and driver versions look good I'd suspect the add-ons. Does it still crash without the add-ons installed?

i havent tried without the addons,i thought maybe it might be the 3.10 ati drivers.i will give a try without them and see what happens.thanks everyone.

Hello,I had several ctds as well, similar to yrs. I'll describe you below what helped in my case - no more ctds.I am not any kind of expert, i just tryed it and works !I have tested for the specific add on sceneries i have installed on my machine and it works for me,so i don't know if it is a general ctd solution, give it a try, may help you too.Open the fs9 folder (the initial one - where the sim is installed) and you'll see a file called scenery.cfg - open it using notepad.Inside this file there are all the scenery areas and their layers as well.Like bellow:................Title=Default TerrainTexture_ID=1Layer=1Active=TRUERequired=TRUELocal=SceneryWorldRemote=Title=Default SceneryLocal=SceneryBASELayer=2Active=TRUERequired=TRUERemote=Title=AfricaLayer=3Active=TRUERequired=FALSELocal=SceneryAfriRemote=..................As you see Each Area and layer have a number. Also, the Areas/Layers numbers shouldbe in order (eg, 1,2,3,4,5,.......31,32,33, etch.)In my case all these were mixed up. For example, I had Area.007 and its layer nr was 5, or Area.007and then Area.009 instead of Area.008, and so on.Normally this is not a problem and has to do mainly with the priority the sim handles sceneries. But in my case, it did caused problems.So, what i did. I renumbered all Areas starting from the one that the numbering was wrong (Area 6 in my case).Then i numbered the layers in a way that they have the same number with the Area they belong.That was it.Maybe you don't have to renumber all areas. You can experiment on that. Or change everything and then, using yr back-up file, replace areas (copy/paste fm the back-up file) untill you find which area caused the problem.Pls, before try anything, take a back up of scenery.cfg file first, either copy/paste it on a different partition or to another store device.nikolas

Bob Z:Thanks for your update on the g2d & g3d.dll file locations.You are correct and I stand corrected. Some time and many reformats ago when I was trying to find a solution to the error messages involving the aforementioned files, I went looking for them and did find them in the Windows/System32 folder. How they got there is beyond me as a check after your thread finds them completely absent from that folder, but found in the Modules folder of FS9 where they should be.In trying to recollect what I did with those files to try and correct the CTD's referencing the g2d g3d files, I remember copying them from where ever I found them, to the main FS9 folder as well as being in the modules folder. I was desperate to find a solution and would try anything. Probably makes and made no difference at all, but as I stated before, my CTD's are almost non existant now after removal of 3rd party landclass & overlapping mesh files. RegardsChris