Archived

This topic is now archived and is closed to further replies.

G-SWSM

G2D.Dll Error

Recommended Posts

Hi.I was wondering if anyone had this issue from time to time, and if they managed to fix it in any way.I get it now and then.Was there a common cause, or was it related to a scenery file?I have also read that some think it may be a missing or corrupt texture file if there aren't any empty folders anywhere on your system.Anyone have any clues at all.Many thanks for any thoughts.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi.I was wondering if anyone had this issue from time to time, and if they managed to fix it in any way.I get it now and then.Was there a common cause, or was it related to a scenery file?I have also read that some think it may be a missing or corrupt texture file if there aren't any empty folders anywhere on your system.Anyone have any clues at all.Many thanks for any thoughts.
Here are some details on my web site, along with some links to others' comments:http://www.adventure-unlimited.org/faultfinding.phpJohn

Share this post


Link to post
Share on other sites

Hi JohnI just wanted to say that I have had your site bookmarked for ever , and using it for reference has helped me though various flight sim woes .Thank you Buddy :( :( Mark

Share this post


Link to post
Share on other sites

Steve,I recently encountered this error (G2D.dll) as well. After considerable testing I traced the cause to a newly installed paint on the Level D 767. Shame too...it was an outstanding paint.If you've recently installed any Liverys you might consider that possibility. Just a thought.Cheers

Share this post


Link to post
Share on other sites

Hi All.Many thanks to all of you for the suggestions. John, you're web site is very interesting indeed, and very useful. I have added it to my favourites and read through the whole site.I admit to being somewhat fed up with this G2D.Dll error I keep getting, and have tried just about everything I can think of. But what I will try next is disabling every single scenery add-on that I have, which by the way is pretty much just the UK2000 stuff and a few others.I noticed that you're web site points to the panels being somewhat usually responsible for G2D.Dll errors, and yet Randy came out with a point about a repaint he was using on the LDS B767, which I do own.Randy, what repaint was it, just in case I have it too.I do though convert all of my aircraft textures to DXT3.I will try the scenery disable thing and see what happens.What is frustrating about this issue is that it can happen in the daytime or evening, can't remember if I have had it at night, and it also seems to happen even if I fly the default Cessna, so I am confused about the panel side of things with that one.I had this happen the other day, I took off from the UK2000 EGLL Xtreme in the LDS B767 which was wearing the Fly Globespan DXT3 colour scheme, and I was using ASv 6.5 and had installed REX textures then closed it.I was also on-line with VATSIM at the time too. I was about FL180 and level in the cruise when all of a sudden, black screen, and long pause then the usual small MS window with FS has yada yada G2D.DLL.I will try the scenery disable thing, and not run ASv, REX or VATSIM and just fly the default Cessna. I will try this in a route from EGLL to EGCC, so I am pretty much doing the same route, but lower of course. Then if this is OK I will try it in the day time.If this seems fine, then I will try it in the LDS and do the same thing.I know this is a lot of testing and a process of elimination, and I hate to bring this up again, but it's such a pain in the a$& that it's a shame we can't fix this.I must admit though, I never thought about aircraft textures causing this!Thanks again for the help guy's.PS my specs are below my sig in case it helps.

Share this post


Link to post
Share on other sites

Steve,It was the American Airlines "Oneworld" livery for the Level D B767 by Gustavo Aguiar. An outstanding paint to be sure, but it consistently caused the G2D.DLL CTD. For me it failed consistently what I came to refer to as the "Heathrow test". I use UK2000 Heathrow Extreme aswell. It would fail after a few cycles from VC to Spot view consistently. Using a suggestion in the repainters forum here...simply resaving the textures with a DXT3 editor using "save as" option seems to have fixed it...although a bit more testing is needed to confirm that.Your situation sounds a bit more complicated if you are getting the error with default aircraft..something I have never encountered.Hope this info helps a bit.Cheers

Share this post


Link to post
Share on other sites
I noticed that you're web site points to the panels being somewhat usually responsible for G2D.Dll errors, and yet Randy came out with a point about a repaint he was using on the LDS B767, which I do own.
Ah well, just because I haven't experienced it doesn't mean it can't happen! I would be happy to add something on this if it can be proven.I am often mistrustful of non-standard texture formats - DXT3 is what FS was designed to use of course. I would be interested to know what format the offending plane started out as.Best wishes,John

Share this post


Link to post
Share on other sites

Hi John.Any thoughts on what might be causing mine to happen as it is with different aircraft.Thanks.

Share this post


Link to post
Share on other sites
Hi John.Any thoughts on what might be causing mine to happen as it is with different aircraft.Thanks.
Not really, I'm afraid, as I haven't experienced this with aircraft myself, but have you tried converting the textures to DXT3 as suggested by clipper759?Best wishes,John

Share this post


Link to post
Share on other sites

Hi.Yep, I convert all my a/c to DXT3.Just one thing though, what about the panels, I notice some are 8bit and some 24 bit etc. Should these be DXT3 as well ?Thanks.

Share this post


Link to post
Share on other sites
Hi.Yep, I convert all my a/c to DXT3.Just one thing though, what about the panels, I notice some are 8bit and some 24 bit etc. Should these be DXT3 as well ?Thanks.
Yes, sorry, you had previously mentioned that and I missed it.Hey, I'm no expert, but I would answer "no" to the panel issue. Reason being is that some panel backgrounds will look bad with a reduced number of colours. The colour black gives you transparency (i.e. windows) and if you reduce the number of colours, dark grey areas may also become black, giving you some "holes" in the wall of the aircraft. (Then you would have to plug them with chewing gum to keep the draught out, teehee). That being said, I'm passing my judgement on good looks rather than any reality of operation. But my suspicions are at specific gauges rather than panel backgrounds.But I can honestly say I don't really know.John

Share this post


Link to post
Share on other sites

Hi.Well, it just happened again.I set out from EGLL in the default Lear, NO add-on scenery active whatsoever, and NO other items running, such as ASv, REX, FS Nav nothing at all.I was about half way from EGLL to EGCC and around FL180 when it happened again. Blank screen then FS has yada yada G2D.DllI am truly stuck now. I just hope this isn't a FS Re-Install.The next thing for me to try is backing up, then deleting the FS config file and letting it build a new one.I also tried that running in compatibility mode thing and selecting Win 200, can't say it did anything.Right now I would p*$$ on a spark plug if I thought it would do any good.Anyone have any other thoughts at all!Thanks.

Share this post


Link to post
Share on other sites

Hi.I have had this CTD quite a few times, and almost only at the end of a long haul using PMDG 744..Had one just today, short after touchdown at KJFK (some freeware scenery) from EGLL (EGLL Aerosoft Scenery with AES).Very frustrating. (Having a nice ~25 FPS at EGLL heathrow with massive traffic, rainy weather and VC cockpit, and you get a CTD upon arrival after 7 hrs.. >:( )And I

Share this post


Link to post
Share on other sites

Steve,Sorry to hear the problem continues. I can confirm that the AA paint I mentioned was my problem and "resaving" the original textures has eliminated the problem. Are you using an AI program? Have you tried shutting it down if so? Bad AI textures have caused me some grief in the past.Hope you get it sorted out Mate.

Share this post


Link to post
Share on other sites

Hi.I very rarely use AI, I fly on-line with VATSIM. But I am going to try it with a different screen resolution.Strange how it has started to happen when I haven't really changed anything except add REX, but that was ages ago. and I use the smaller size clouds and selected DXT3 too.

Share this post


Link to post
Share on other sites

Hi again.Well, it just happened again, and this time I was running in 1280x1024 size. But this seems to have made no difference at all. And I was flying at night, not day time.The error message it just gave me was the followingAppName: fs9.exe AppVer: 9.1.0.40901 ModName: g2d.dllModVer: 9.1.0.40901 Offset: 000a46f5If anyone has had the g2d.dll error and managed to fix it, could you please post in here what you did. It would also be very useful to know what caused your error in the first place.Thanks for any help.

Share this post


Link to post
Share on other sites
Strange how it has started to happen when I haven't really changed anything except add REX, but that was ages ago. and I use the smaller size clouds and selected DXT3 too.
Ya, this started happening to me as well. Never, ever I had a g2d.dll error before and in the end I came to the conclusion that the only things that was changed was - adding REX... now, before accusing anybody of anything, more testing needs to be done. It could well be just one rogue texture that spoils the game.... had a loooong flight from Dubai to JFK yesterday and right on approach to 13L, a few miles before the turn to CRI VOR, suddenly all clouds disappeared and poof! a g2d.dll error. I was so disgusted that I went, resaved ALL clouds textures that REX made for me (in the main Texture folder) and restarted the flight. Went without a hitch...Bottom line is that this error creeps up once in a while and I simply cannot reproduce it. When I then re-save all clouds textures in FSImagetool, repeat the flight and all is well. Without exception!As I said, more testing is needed, because it could well be something entirely else than REX (which is more than fantastic!), but so far, events point into that direction.My 0.02

Share this post


Link to post
Share on other sites

Hi.Well, I am going to try a couple of other things now.1) I am going to install and run Memtest and see what it comes up with.2) I am going to pull out one of the two RAM sticks and see what happens, then repeat the test with the other stick etc.I can't think of anything else now.Talking with someone today, and describing what problems I have had such as the g2d.dll, and the odd blue screen of death etc he seems to think that this could all be a sign of bad RAM.If anyone has any tips on how to understand the results of the Memtest I would be most gratefull.

Share this post


Link to post
Share on other sites

Hi.Thanks Gus.Does anyone have some understanding of Memtest that they could share with me please.I have never used it before and would appreciate knowing what I am looking for when I run it and get the results.Thanks in advance for any help.

Share this post


Link to post
Share on other sites