I just did my 4th flight with g3d.dll crashes. 3 of them crashed when establishing 4000-5000 feet before capturing LOC . The other one crashed when I looked outside the left window which exactly where Frankfurt Airport is located. Those flights were supposed to land on rwy 07L, from Aerosoft Arlanda using Leonardo Maddog.

 

I tried everything I found from the internet. The only things I havent done are eliminating addon one by one and reformatting my OS (re installing FS9), I simply have no time. The last time I did that, my 'co pilot' was extremely unhappy

 

I read on FSX forum that Pete Dawson's new module seems to be the cure for g3d.dll, but it was not for FS9.

 

I reinstalled my nvidia driver, double checked that fs9.exe is patched with 4gb switch, reinstalled EDDF MA FRA and scanned it using dxtfix,removed spanair woai package which was known as the culprit for Aerosoft Barajas crash (I know they're out of business), put EDDF scenery in the scenery library lower than ESSA ---> I read this on Aerosoft forum that someone actually made it fixed by lowering EDDF below EHAM as He had the crash when flying from EHAM to EDDF ( I dont have Aerosoft Amsterdam nor Brussels), re installed AIRAC (October 2012).. and resulted in 4 g3d.dll crashes since last saturday.

 

I never had this before, neither have I encountered such persistent ctd. I have experienced ctd but I know this one is not a seasonal one.

 

Help me out guys, what should I try next? before accusing the related developers should be responsible for this, I am making sure I am not missing something here. I'm running out of time since Alitalia ended MD80's 45 year service, SAS is phasing out their MD81-82's, I cant fly routes with airlines they don't exist.

windcheck?

Hi Reason,

 

did you deactivate "all" AI Traffic testwise as a check to exclude just any AI-TRaffic-related CTD?

Have you already been at EDDF before without CTD?
I remember very suspect CTDs at UNNT; I posted about this problem perhaps half a year ago. At the end, an Il-76 of Belarusian Airforce parking in the last row was identified as the culprit. A similar phenomenon may occur at EDDF, given the pure amount of traffic there. This may be the cause particularly if you use WOAI packages using their installer routine; I heard of some packages being installed incorrect.

 

Hope you get this thing solved soon to get back on the left seat of your Maddog.

 

Greetings from Dresden

Harald

 

Help me out guys, what should I try next? before accusing the related developers should be responsible for this, I am making sure I am not missing something here.

 

Here is a extremely useful link that may be of some help in pointing you in the right direction to solve you CTD.

 

http://www.adventure-unlimited.org/faultfinding.php#fe

 

Regards

Mel

I think I once encountered an aircraft with faulty texture, it was so obvious since the aircraft has no livery, total grey. But I was taxiing at that time, so I didn't do anything. Although it didn't crash my sim, I'll start from there. Thanks Harald . Just curious where you park your 727 right about now

Let's see if it helps. Reading the site Mel suggests, there may be a complete different reason. I'm particularly aware about the AES-related problems. But ESSA and EDDF both are supported by AES. If you use AES (as I suppose), you may deactivate it at both airports and test again... However, I always start these investigations by deactivating all AI traffic nowadays as it is the reason for at least 50 % of my CTD cases.

 

My 727 is parked at her home airport Tbilisi International while I'm trying to learn something completely new...

 

 

So I took another flight with the same scenario. That makes it the 5th flight with a crash. However, I tested the route (ESSA EDDF) using Airsimmer, and experienced no crash. This is puzzling alright.. By the way, I am curious whether adding "missinglibraryalert=1" will work in fs9, has anyone tried it?

 

 

 

 

Let's see if it helps. Reading the site Mel suggests, there may be a complete different reason. I'm particularly aware about the AES-related problems. But ESSA and EDDF both are supported by AES. If you use AES (as I suppose), you may deactivate it at both airports and test again... However, I always start these investigations by deactivating all AI traffic nowadays as it is the reason for at least 50 % of my CTD cases.

 

My 727 is parked at her home airport Tbilisi International while I'm trying to learn something completely new...

 

130325 Mi-2 UGTB1.jpg

 

Been there. It was such a fun. Learning to Hover has given me hardship. Good luck Harald

 

I am curious whether adding "missinglibraryalert=1" will work in fs9, has anyone tried it?

 

It will work when placed in the Scenery section.  You're trying to pinpoint an object that might be missing or corrupted.  It might be easier to disable all your addon scenery in the Scenery Library, run fs9 and see if that fixes your problem.  If so, you can enable 3-4 scenery addons at a time until you start getting the error again.

 

Best regards,

Jim

Hi Jim. Although, eliminating method seems to be the most recommended, I have decided to reformat and reinstall. The amount of time isn't pole apart.

 

So, it is applied in scenery.cfg? I thought it should be in fs9.cfg (or fsx.cfg). Will it allow me resume the flight instead of to desktop?

It's my turn to wish you good luck for your plan to build up FS2004 new.

 

Regards, Harald

 

So, it is applied in scenery.cfg? I thought it should be in fs9.cfg (or fsx.cfg). Will it allow me resume the flight instead of to desktop?

 

It is placed in the [scenery] section of the FSX.cfg.  Not in the scenery.cfg.  Once the line has been added, it will show the missing texture or object and allow you to click okay to continue.  It will not cause a crash.

 

Best regards,

Jim

 

I think I once encountered an aircraft with faulty texture, it was so obvious since the aircraft has no livery, total grey.

 

That kind of livery problem would not usually cause a CTD (ddl error). The gray appearance is the aircraft models default color which means there is either a aircraft configuration file error such as the texture= name not being the same as the texture folder name or incorrectly named texture(s) inside the texture folder. The quickest way to find these is to determine what type of AI aircraft it is from within FS9, for example you see a parked A320 but it has no texture. Shut down FS9, go to your AI A320 folder, open the airfile with AirEd and make that aircraft viewable. (Aircraft Type=2 to =0), Start FS9 and in the select aircraft menu find the AI A320 and go down the list of liveries viewing each one. You will come across the blank aircraft and by using the livery name ie 'Lufthansa' you will know exactly which aircraft.cfg entry and texture folder is at fault. Once the error is corrected double check in the select aircraft GUI, if fixed reverse the change in AirEd.

 

Regards,

Mel

It's possible to find faulty AI aircraft textures with the method Mel describes, too. Of course you should have a suspect which aircraft could be the culprit. If you select the aircraft in the menue, once you come to display the faulty plane, mostly the textures show up but the plane doesn't spin and/or FS2004 crashes.

 

@Reason: I will be some days offline now, but nevertheless I'm interested if your new FS2004 will avoid these CTDs if you repeat your flight with the same configurations. Good luck and happy Easter days!

 

(By the way - regarding your comment on my heli attempts: Flying the Mi-2 heli is easier than any other heli I tried before (once you managed to start the engines of course) - even easier than the so said "beginners model" Ka-26. I bought both together, but I soon will abandon the Ka-26. Perhaps I will donate it to a colleage which I recently convinced to start flight simming with FS2004!)

 

All the best!

 

Harald

It is placed in the [scenery] section of the FSX.cfg.  Not in the scenery.cfg.  Once the line has been added, it will show the missing texture or object and allow you to click okay to continue.  It will not cause a crash.

 

Best regards,

Jim

 

Okay, if I got this right, I should put it under [scenery] section in FS9.CFG. It will not cause crash of course, why I want to give it a try is whether it allows me to resume flights where it should have been crashed. For example, G3D.DLL crash popped up, when I click okay, it brings me to desktop, With this mod, I may be able to resume flights since clicking okay will not drag me to desktop.

 

Thanks Jim

 

It's my turn to wish you good luck for your plan to build up FS2004 new.

 

Regards, Harald

 

Thank You Harald from Dresden .  Just a reminder, the upkeep cost is not cheap grounding those classic 727 )

 

I cant believe how many times you guys 're-format' and 're-install' fs9. That would drive me insane!!

 

Tell me about it. It does drive me insane. If the methods don't work. I'll delete EBBR and the latest version of EDDF. When some people are about to address FSX as an old platform, and some have been comfortable with Xplane and or P3D, I am here fooling around with the jurassic

 

Just a reminder, the upkeep cost is not cheap grounding those classic 727 )

 

If I simulate to be able to fly a 727, why not simulate to have the money it takes? B)

She isn't grounded at all, it's just a break to learn to fly the heli in the mountains. Today in the evening the 727 will take off from Tbilisi to Dubai (FlyTampa... )!