Is it only me, or is FSX much more unstable than FS9? My general opinion now that I've used FSX for quite a while, and got rid of FS9, is that it crashes quite often on g3d.dll and g2d.dll errors. I've even came some far that I reinstalled it and ONLY installed the airport I fly from and to so that it doesn't crash somewhere on the way due to flying over of another addon airport.Seems to me that the FSX engine quite cannot handle the addons like FS9 can. I had over 300 addons in FS9, here and there there was a bad one, but was quite an easy task to find the offending airport. Either it crashed when you tried loading it, or it had a memory leak, and both were easy to find.In FSX, most crashes happen while flying, and saving the flight along the path doesn't help me find the offending file/airport, since there are sometimes more in the vicinity and also doesn't crash when you load inflight, only when I start the flight from the beginning.I already opted out couple of airports, but still I tried my favourite route yesterday (EGLL-LOWW) and now instead of g3d.dll, it was a g2d.dll error.It's starting to be rather annoying the whole thing, and I'm seriously considering going back, the only thing keeping me is the high resolution which I would gladly like to keep.What's your opinion on this?

Is it only me, or is FSX much more unstable than FS9? My general opinion now that I've used FSX for quite a while, and got rid of FS9, is that it crashes quite often on g3d.dll and g2d.dll errors. I've even came some far that I reinstalled it and ONLY installed the airport I fly from and to so that it doesn't crash somewhere on the way due to flying over of another addon airport.Seems to me that the FSX engine quite cannot handle the addons like FS9 can. I had over 300 addons in FS9, here and there there was a bad one, but was quite an easy task to find the offending airport. Either it crashed when you tried loading it, or it had a memory leak, and both were easy to find.In FSX, most crashes happen while flying, and saving the flight along the path doesn't help me find the offending file/airport, since there are sometimes more in the vicinity and also doesn't crash when you load inflight, only when I start the flight from the beginning.I already opted out couple of airports, but still I tried my favourite route yesterday (EGLL-LOWW) and now instead of g3d.dll, it was a g2d.dll error.It's starting to be rather annoying the whole thing, and I'm seriously considering going back, the only thing keeping me is the high resolution which I would gladly like to keep.What's your opinion on this?

I have absolutely no problem with CTD's in FSX, but I'm still on Windows XP 32 bit. Remember Win 7 64 bit is not native to FSX, so the problems may be more related to how FSX works with the new O/S. Or maybe one or more of the addons to it, may not be fully compatible with the O/S. Have you tried running it in any compatibility modes?

I'm on Win 7 64bit and no problems here.We have similar systems and I'm surprised you're having these stability issues. I had 1 CTD a while back when I installed some dodgy scenery, but that's all. I find FSX to be very stable.That said, I am a newcomer to flight sims and I've only been using FSX for a few months. I've had no experience with FS9.Mark

HelloNo problems here but I am back on XP64 again.I have tried to run FSX on Windows7 64 twice now but always eventually run into somethingthat gives me problems, I guess that I have some addons that do not play nice together under Win7-64.Latest problem that drove me back to XP64 was Speech input becoming laggy after a certain amount of time.It could have been my speech application or my soundcard but it was repeatable every flight.I gained zero performance increase under Win7-64 compared to XP64 so I am staying with the older OSWhen I build my next machine I will revisit Win7-64 as every machine can give different results and I will most likely need Trim support by then.

Is it only me, or is FSX much more unstable than FS9? My general opinion now that I've used FSX for quite a while, and got rid of FS9, is that it crashes quite often on g3d.dll and g2d.dll errors. I've even came some far that I reinstalled it and ONLY installed the airport I fly from and to so that it doesn't crash somewhere on the way due to flying over of another addon airport.Seems to me that the FSX engine quite cannot handle the addons like FS9 can. I had over 300 addons in FS9, here and there there was a bad one, but was quite an easy task to find the offending airport. Either it crashed when you tried loading it, or it had a memory leak, and both were easy to find.In FSX, most crashes happen while flying, and saving the flight along the path doesn't help me find the offending file/airport, since there are sometimes more in the vicinity and also doesn't crash when you load inflight, only when I start the flight from the beginning.I already opted out couple of airports, but still I tried my favourite route yesterday (EGLL-LOWW) and now instead of g3d.dll, it was a g2d.dll error.It's starting to be rather annoying the whole thing, and I'm seriously considering going back, the only thing keeping me is the high resolution which I would gladly like to keep.What's your opinion on this?

Hi Word Not Allowed,FSX is far superior over FS9 (you asked for my opinion). One of the major and most common errors when using FS9 was the g3d/g2d.dll error. I really haven't seen it all that much with FSX until lately. I doubt you would ever get the gd3/g2d.dll error using FS9 with the modern systems today. According to Microsoft support G3d.dll is the three-dimensional portion of the graphics engine used in Flight Simulator. It contains the BGL interpreter for Flight Simulator. You want to make sure you have the latest updates to FSX installed. Running FSX in default mode w/o overclocking, FSX should run well and w/o getting this error. Nowadays gamers like you are trying to get the most out of their systems and are putting more and more demands on graphics engines and system memory. Based on info I obtained from Google searches, most people resolved this issue by reducing graphics settings within FSX. Some others resolved it by reinstalling FSX (that probably wasn't a solution at all for them as reinstalling only changes graphics settings until the user increases the FSX sliders). Since the g3d.dll contains a .bgl interpreter for FSX, it's possible that addon developers have not programmed an addon properly but I think it's more likely the increased stresses placed upon FSX by users who like to overclock and try to get the most out of their system. I guess this is why I have not been unfortunate as many others to have gotten this error. I seriously doubt you'll ever get the g3d/g32.dll errors using FS9 today with modern systems. Even with my "old" system, I got a 100% increase in FPS when running FS9 back in late 2006. The modern systems today can probably get another 100% increase. Sorry it's not the solution you were looking for but hope you can find a compromise with your system and FSX.Best regards,Jim

Word Not Allowed,FSX requires the best and fastest hardware available, along with a properly tweaked system.I find FSX to be much more stable than FS9. I don't have any crashes. But, I did spend a lot of time and money to get it there.If I can offer you one quick advice is to run and get a gtx 480 and install the 197.75 driver.Let me know if you need any help.

Aerosoft AES has caused this problem for me in the past under FSX.

Jim, your explanation seems very viable and reasonable.I think one must load stuff step by step as one flies around and then see when and why it crashes.DJDose, though I respect your suggestion, shelving out 500€ for the new card is not an option right now. My GTX285 must serve me as it does. Besides, I played many other games on it since I got it, and it didn't crash once in any other game. So I don't really believe that the GTX480 would be a miracle solution to my problem... and giving out such a money to maybe have a solution, is certainly completely ludicrous.Steve, I remember AES crashing FS9 when you would start up on the non-AES'd airport and fly to one with the AES, we had some big discussions here about it. I didn't experience it under FSX though. You might be right though, maybe it crashes just like that...

FSX is more stable in my experience purely in terms of the software, but it rides closer to the ragged edge where system resources are required, and if they run out, that's when you'll get problems.Al

FSX is more stable in my experience purely in terms of the software, but it rides closer to the ragged edge where system resources are required, and if they run out, that's when you'll get problems.Al

What do you consider a system resource? Memory? CPU? FPS drop is known. Memory starvation too, and if kept in the limits, what's the problem?

As a side question why use the older nVidia drivers like 197.75 and 182.50 (recommended for older cards like mine)?