Thanks. I hope they work for you!Jim Young

Ryan,Don't you think that is a bit unfair? To suggest that it is ORBX's fault is disproved right in this thread by the numerous attested g3d.dll crashes when flying near large european payware addon airports. There are also testimonies of people having fixed their CTD problems while flying in ORBX sceneries, with me being one of them.

Is the base g3d issue caused by orbx? No I dont think so. But it is a huge factor with their sceneries... whether it's a faulty GUID, double scenery etc. Sure it happens with other sceneries but that simply proves it's an issue with scenery!Without Orbx, no CTD'sWith Orbx, CTD's. I'm not saying.... I'm just sayin'

Is the base g3d issue caused by orbx? No I dont think so. But it is a huge factor with their sceneries... whether it's a faulty GUID, double scenery etc. Sure it happens with other sceneries but that simply proves it's an issue with scenery!Without Orbx, no CTD'sWith Orbx, CTD's. I'm not saying.... I'm just sayin'

Not, the base of g3d.dll error is the usage of textures. Maybe a false usage, or too many textures. You can come to that conclusion when you compare airports from different developers.Some airports and ORBX apparently have this specific "usage" that brings up g3d.dll more easily than others.And one thing: no amount of tweaking is going to remove this error. Not that SmallPartRejectRadius, nor anything else... They are maybe going to lighten it, lower VAS usage so much that it doesn't crash in that moment. But it will in end, sometime. It's not a solution.

Take for instance FSDT, Flytampa, their sceneries look no less than Aerosoft's, and they are not crashing.

I have g3d.dll crash on FSDT Honolulu and VAS is only 1 Gb. I don't think it has to do with any particular scenery. Just trying to d otoo much and FSX is puking.scott s..

I have g3d.dll crash on FSDT Honolulu and VAS is only 1 Gb. I don't think it has to do with any particular scenery. Just trying to d otoo much and FSX is puking.scott s..

Did you install PHNL on a FSX without any other add-on, did you have ultimate traffic. please let me know.

This is what I just posted at Aerosoft :

• The last week I am trying to finish a flight from Amsterdam to Frankfurt with the 737NGX.Every time at the same place I am getting a CTD.I reinstalled Germany West 2010 , but no luck.To be sure it wasn't the 737NGX I have made 7 extra flights from Amsterdam to Paris CdG, Brussels , London Heathrow and London Luton.For the Netherlands, Belgium and the UK I am also using photoscenery.All flights where done around sunset.No issues or whatsover I encountered.Only when doing the flight to Franklfurt I am getting this issue.I reprogrammed the flight , but no luck.Attached are 2 screenshots :- one in spotplane view, where black squares are showing.- one form within the cockpit and no black squares are shown looking outside.What happens :about 10 miles before ETNN , coming from Schiphol and going heading 138, those black squares are starting to show.First I thought it was the transition from day to night textures, but after 5 minutes they were gone.Only the moment they are gone FSX crashes and a CTD appears.Framerate is locked at 25 and was 24.4.I know of several fellow Flightsimmer sgetting CTD's , G3D.dlll errors when flying over As and Orbx scenery and/or when using AES..At Avsim there is a Topic going on about the G3D.dlll errors.Also I used the MissingLibraryAlert=1 tweak in the fsx.cfg file and several "missing libraryXXXX" shows up.Is AS aware of this and if so , do they have a statement about this and , even better, a solution for this ?

Jim, I think I nailed it...earlier in the tread, someone mentionned FSDT addon manager for adding SmallPartRejectRadius to the cfg, which I used, I noticed this morning that it added way more than just one parameter so I deleted the cfg, let FSX rebuilt a new one and only added HIGHMEMFIX=1 and SmallPartRejectRadius=1, I went into the bios and changed my memory settings from1333 mhz to xmp and 1600 mhz, rebooted and tested, no more g3d.dll near KSEA with PNW !!!!Thanks for the tip again Jim, hope it will last.... Alain from Montreal

Jim, I think I nailed it...earlier in the tread, someone mentionned FSDT addon manager for adding SmallPartRejectRadius to the cfg, which I used, I noticed this morning that it added way more than just one parameter so I deleted the cfg, let FSX rebuilt a new one and only added HIGHMEMFIX=1 and SmallPartRejectRadius=1, I went into the bios and changed my memory settings from1333 mhz to xmp and 1600 mhz, rebooted and tested, no more g3d.dll near KSEA with PNW !!!!Thanks for the tip again Jim, hope it will last....Alain from Montreal

Great news Alain! I'm glad it worked for you too. Thanks for posting your results.Best regards,Jim

Did you install PHNL on a FSX without any other add-on, did you have ultimate traffic. please let me know.

I have many addons for the area including Hawaiian airports v1 and 2, megaX Hawaii Oahu, DillinghamX, Niihau and Kauai photosenery, Molokai Landclass, Hawaii_XG, etc. I use my own traffic.scott s..

I have many addons for the area including Hawaiian airports v1 and 2, megaX Hawaii Oahu, DillinghamX, Niihau and Kauai photosenery, Molokai Landclass, Hawaii_XG, etc. I use my own traffic.scott s..

please test without FSDT airport and report back or do the opposite please just uncheck in FSX library manager, you don't need to uninstall anyting.Thank youFabrizio

I have many addons for the area including Hawaiian airports v1 and 2, megaX Hawaii Oahu, DillinghamX, Niihau and Kauai photosenery, Molokai Landclass, Hawaii_XG, etc. I use my own traffic.scott s..

With these many things installed, there are too many things that can go wrong. You have to test without some parts or with only just one, trying to find which one is crashing.

I have many addons for the area including Hawaiian airports v1 and 2, megaX Hawaii Oahu, DillinghamX, Niihau and Kauai photosenery, Molokai Landclass, Hawaii_XG, etc. I use my own traffic.scott s..

I can tell you that I have MTX Oahu along with the freeware Niihau and Kauai photoscenery, I do not get any g3d crashes in Hawaii.From everything I have read in this thread if I were you the first thing I would eliminate is the FSDT scenery, if you do not get any crashes then add them back in one at a time and test.I do not know if it will help anyone with this issue, but I will say that I do not have any Aerosoft, FSDT or any other payware airports installed plus I do not have any of the Orbx products for the USA installed, I do not get any of these g3d crashes anywhere. I fly all over the USA and EU, down into the Caribbean along with hops in Africa and SA. I do have all of the Orbx Australia scenery installed, but I do not have any of the Orbx Australian payware airport scenery installed. I fly all over Australia and do not get any g3d crashes.From reading all of Word Not Allowed's posts I really think it is heavy hitting payware scenery, mainly airports, that is causing the sim to crash. Flying a plane like the PMGD MD11 / 737NGX or VRS FA18E just adds to the problem. I am not saying this is everyone's problem, but I do think it is a lot of people's problem.Hopefully my comments have not offended anyone since I do not share in your frustration.

It seems that I was able to solve my CTD's by changing some settings in XtremeFSX PC.In the program I added all extra backgroundprograms for core optimazation and that seemed to solve my issues.( Gamebooster 3, OC Guru for my graphics card, LINDA, AISmooth , 3D Real Cockpit Effect FSX and HAT-Track )First at my CTD area Core 0 was used for 40-50% , core 2 for 100% and core 3 and 4 for 70-80%.Now core 0 is used for 50-60% and the other cores 60-80%Also I set the Booster Option to more stability and the Blurries Eliminator to 15% instead of 30%.

Gerard, this is pretty much all useless info.It would be way more useful if you posted what that program did to change that. Otherwise without people having such extra programs, it's not possible to replicate. And I hardly believe it's magic - it must be some settings the program is programmed to do.

It seems that I was able to solve my CTD's by changing some settings in XtremeFSX PC.In the program I added all extra backgroundprograms for core optimazation and that seemed to solve my issues.( Gamebooster 3, OC Guru for my graphics card, LINDA, AISmooth , 3D Real Cockpit Effect FSX and HAT-Track )First at my CTD area Core 0 was used for 40-50% , core 2 for 100% and core 3 and 4 for 70-80%.Now core 0 is used for 50-60% and the other cores 60-80%Also I set the Booster Option to more stability and the Blurries Eliminator to 15% instead of 30%.

Coming from the manual : the specific add-on will be handled by Xtreme FSX PC program optimizing the cpu cores. To me it looks like setting the affinity for each add-on. I dont know if it is a fixed affinity or that it will be changed depending on core loads.The blurries eliminator changes the FIBER_FRAME_TIME_FRACTION , so I beleave that 15% would be 0.15.What the booster option does I really do not know. In the manual it is written that the bar is related with strangle of GPU and frames increase.