Does not answer the question why the thread was locked. Seems like head in the sand to me. But it was ok for some regular Orbx forum users to say that FSUIPC might be the cause. Absurd really.

Not only that, it wasn't like Tomaz was out to get Orbx... look at the products he purchased! I've only got two sceneries (one I won), and one aircraft. Apparently I would have lesser say in the forums... bleh

If Pete fixed it, then it's time to celebrate! Drinks are on me.

Thanks Bill! Pepsi Please!

Nice message from Orbx to me: [#1001] Your account has been temporarily suspended. This suspension is due to end on 30 December 2011 - 08:25 PM.So, people, be careful what you say about Orbx on the internet!

Yeah sorry I'm dragging the party down lol... I'll take a root beer.So far no G3D related ctd's... I'll keep testing :)

Nice message from Orbx to me: [#1001] Your account has been temporarily suspended. This suspension is due to end on 30 December 2011 - 08:25 PM.So, people, be careful what you say about Orbx on the internet!

I'm not worried but I thought they already banned you... I guess you should just keep the details to your self maybe?

I also think ORBX should just acknowledge... nothing ever bad came from acknowledging errors. The error is in the scenery - though one must say that it must not be ORBXs fault directly. They are simply unaware, or not knowledgable enough (don't take this as an insult please) to find what's wrong. There should be developers from FT, AS, FSDT, ORBX working together to see what they are doing differently, what is the difference between files, and why do some sceneries cause crashes and others don't. It's man-made and must be possible to fix inside the scenery.

What??? Did we not just go through a 23 page thread where it was determined that these crashes are caused by corruption in memory? I thought it was basically determined that any complex scenery can cause this, and didn't we all see the "last file loaded" reports indicating that the problem is with loading AI traffic models? What the h*ll is Orbx supposed to acknowledge?And yes, I would consider a statement like "This should be the happiest day for your company since your sceneries are plagued with g3d CTD's" a bit accusatory, if not very abrasive given the circumstances.Jim

OK so it was worded poorly. English language barrier maybe? Bad day? It happens. I still feel it's not moral to ban the guy... at least give a warning or something.

Hey guys, let's just cool it for awhile.Why tarnish such a great event in recent FSX history as the fixing of one of the greatest FSX curses? No side fight is worth ruining the reward of planning and executing a flight plan without worrying about another G3D.dll CTD! Let's voluntarily let this thread die a natural and speedy death.Kind regards,

Just to add my 2 cents worth:I've been purposely running 1 of my FSX development test systems with a very low powered 512 MB VRAM PCI-E add-in video card.I cannot personally recall ever experiencing a G3D.DLL error, and I almost never use any AI traffic. BUT....Despite an otherwise fairly optimized system setup and implementing selected FSX.CFG file tweaks (such as HIGHMEMFIX=1 etc.), when flying GA "bush" type aircraft in ORBX FTX PNW scenery for greater than about 15 minutes, I would incur black textures on part or all of my aircraft, followed later by similar intermittent texture losses on static scenery objects and/or Multi-Player aircraft.After installing the FSUIPC updated base package and latest FSUIPC DLL file today, the "texture loss" problem has not shown up on today's 45 minute Multi-Player flight, and the FTX terrain textures appear to be rendering with greater speed and sharpness. Many thanks to Pete Dowson for this workaround... and for all his other generous contributions to the FS Community over the years ! Regards,GaryGB

What??? Did we not just go through a 23 page thread where it was determined that these crashes are caused by corruption in memory? I thought it was basically determined that any complex scenery can cause this, and didn't we all see the "last file loaded" reports indicating that the problem is with loading AI traffic models? What the h*ll is Orbx supposed to acknowledge?

I think this my exit-point here. I don't want to stir up things any more. Yes, memory corruption, no it was not AI traffic model (only), those only indicated what FSX loaded last. It can also be a model of the aircraft you are flying. The question remains still why do ORBX and those specific sceneries cause the memory corruption, and some other sceneries do not.I'm outta here, nothing else to say what I haven't said any more.

Nice message from Orbx to me: [#1001] Your account has been temporarily suspended. This suspension is due to end on 30 December 2011 - 08:25 PM.So, people, be careful what you say about Orbx on the internet!

Don't worry about it! That is just Orbx-speak for Merry Christmas.

What??? Did we not just go through a 23 page thread where it was determined that these crashes are caused by corruption in memory? I thought it was basically determined that any complex scenery can cause this, and didn't we all see the "last file loaded" reports indicating that the problem is with loading AI traffic models? What the h*ll is Orbx supposed to acknowledge?And yes, I would consider a statement like "This should be the happiest day for your company since your sceneries are plagued with g3d CTD's" a bit accusatory, if not very abrasive given the circumstances.Jim

I agree.Now, the OP got a chance to bring his hurt feelings over to another forum and continue the discussion like he always wanted, everyone had a chance to get in a little dig at ORBX for being elitist in their attitude sometimes, and the technical issue we've been talking about from the start has been squashed by Pete Dowson.I think this thread should have been locked 2 pages ago.

Not sure what there is to own up to about the problem. Seattle is a known problem area and it always has been. Microsoft included some shoddily made scenery objects that disappear if you turn Scenery Density down a notch.Besides that Orbx has acknowledged that missing GUID's cause g3d errors. So there was a public thread made to find GUID's and internal development to catch them. There's still development going on to make sure every airport is clear of missing objects. Currently beta testing includes turning the flag on in the fsx.cfg and making sure there are no missing objects or textures.Beyond that I don't know what about Orbx scenery could cause a g3d except for the unfortunate coincidence of Seattle being a bad area. We use PR's, models, placement files, ADE files, all the same files everyone else does.Also for anyone looking to see the real cause of g3d errors... do a fresh install of FSX and turn on the flag for error messages and fly around Seattle. There's some nasty errors that come up.

Besides that Orbx has acknowledged that missing GUID's cause g3d errors.

They may have acknowledged that, but it hasn't been proven.

Hi TomazThis is totally NOT unusual for Orbx in my experience. I expect I will end up in the same boat after writting this but frankly I dont much care any more. They obviously have no stomach for anyone that says anything even mildly negative about their products.I only posted a message the other day here about an issue I had with the company that was all about attitude in the end and got swamped by Orbx groupies telling me it was my problem because I dared to bring up a fault in their Australian scenery which I can prove exists. Its their attitude towards their customers in the end that stinks, not mine.I have in the past and continue to admit that their scenery vastly improves the Australian landscape but does it mean its perfect? Of course not.Dont worry, I too have been plagued with g3d errors around YBBN in particular but never went far down that path because I knew what I would get.... its your system, not our fault we dont ever get a problem blah blah blah etc etc...probably then followed by a ban.This is a fault in leadership in my opinion Tomaz, these guys make quite good scenery but its by no means perfect. g3d errors are quite common when flying over the area and that just fact. They can sugar or for that matter vinegar coat it all they like.Perhaps JV and others should stick to making and improving their scenery and get someone to front the public with better people skills.RegardsBarra

They may have acknowledged that, but it hasn't been proven.

Ah but it has been proven as a contributing factor. That was the purpose of the Orbx Libraries patch. Internal and public testing showed that g3d errors can be caused by missing objects or textures.It's not the only cause but it's one of the most strongly identified causes. Besides the missing objects I simply don't know what else can be said. We don't do anything that heavily differs from other developers. Seattle is a poor performance area, it's been that way for years, of course an intensive addon will increase that problem.