2369640 *** G3D bad pointer trapped and crash prevented ***G3D fix: Passes 72913, Null pointers 0, Bad pointers 1, Separate instances 1My first landing and shut-down at Orbx YBBN in a year. Amazing.Hella blurry because I overflew the field at 1200' doing 260kts before I swung around to catch ILS1 - but hey, exercised....

As posted above, can you do the same "trick" for the FS9 version of FSUIPC?

Sorry, probably not. Surely the same sort of thing doesn't happen on good old reliable FS9? Pete

I must say some great work there Pete, I can now fly heavy's with my favourite LOD settings :) 6343609 *** G3D bad pointer trapped and crash prevented *** 6346105 *** G3D bad pointer trapped and crash prevented *** 7034569 *** G3D bad pointer trapped and crash prevented ***You are a star and im glad i brought fsuipc ages ago :)

Testing FSX now with these new modules with PNW and scenery complexity and autogen at extremely dense, water on highest and LOD 7.5, normally get a crash just south of OLM VOR heading towards Portland or coming back up approaching KSEA. If this works I'll be the happiest guy around as I've struggled so much with this crash, lost so many sleepless nights trying to 'fix' it earlier this yr. Lowering LOD certainly helps as previously stated but the ground textures look rubbish and lose focus too near the aircraft.Pete so far you are a true genius and deserve all the praise the community can give you, whilst the errors perhaps are still there you appear to have prevented them from crashing which at the end of the day is all that matters. Should we start spreading the news onto other forums like ORBX or leave it a few days to beta test?Thanks again

Sorry, probably not. Surely the same sort of thing doesn't happen on good old reliable FS9? Pete

I'm afraid it does Pete which is why developers like ORBX walked away from their commitment of 'fixing' their scenery as they claimed it wasnt causing the crashes. G3D.dll crashes have been around for yrs even before FSX. Scenery per se perhaps doesnt cause it but as you rightfully found out its how FSX and our hardware manage the extra load beyond that of default, and ACES intended use of scenery that seems to trigger it.

I'm afraid it does Pete which is why developers like ORBX walked away from their commitment of 'fixing' their scenery as they claimed it wasnt causing the crashes. G3D.dll crashes have been around for yrs even before FSX. Scenery per se perhaps doesnt cause it but as you rightfully found out its how FSX and our hardware manage the extra load beyond that of default, and ACES intended use of scenery that seems to trigger it.

Before Pete's fix, I couldn't complete a flight in ORBX PNW from KORS to KPDX (read my earlier posts in these treads) but at low/medium settings, with a clean cfg except HIGHMEMFIX, LOD at 4.5 with a VAS that had to be under 2.8; I understand your point that we asked a lot of the game now with new hardware except, Microsoft put those sliders in the game, if the hardware follows, I cannot see why one developper can't make sure his product will work at those max settings when others can, I do not mind lowering some settings to get the FPS I'm comfortable flying with, NOT to prevent the game from crashing because of an addon repeatably, at the same location, everytime....Don't get me wrong I'm not trowing stones at ORBX (I do not own Aerosoft's Europe airports involved) I enjoy (and own 99% of) their work a whole lot, I'm sure they are looking into this in the background and maybe it is not fixable but only crash avoidable thanks to Pete, I just hope all developpers will take note and "reliability" of addons will increase because of this.PS Word Not Allowed : I am now able to complete my test flight at a VAS of over 3.8 and no crash !Alain from Montreal

I'd like to thank Jackson-OP, Kostas for keeping this thread alive, and Pete for somehow finding a solution to this annoying problem. Today is a great day and FSX will never be the same thanks to Pete Dowson. You deserve an award.

I'm afraid it does Pete which is why developers like ORBX walked away from their commitment of 'fixing' their scenery as they claimed it wasnt causing the crashes. G3D.dll crashes have been around for yrs even before FSX.

Hmm. I've not used FS9 since FSX came out. But if you have details of the crashes (I need module, offset and error code), I can look to see if it's the same thing. If it isn't i'm afraid I really can't spend time on it. It'd be a whole new ball game.RegardsPete

Pete,Thank you!

I've stopped using FSX for about 5 months now as I was plagued with these crashes, I've only enjoyed NGX for a month or so before I've got so frustrated and never fired up my FSX machine again. I was actually on a verge of investing in P3D and was doing a serious research to make the switch. Well, I'm going back to FSX tonight to test things, I'm sure they've been fixed. This is simply amazing. Thank you very much Pete!To ORBX, you've obviously didn't try hard enough to fix this, what a shame.

Hmm. I've not used FS9 since FSX came out. But if you have details of the crashes (I need module, offset and error code), I can look to see if it's the same thing. If it isn't i'm afraid I really can't spend time on it. It'd be a whole new ball game.RegardsPete

Pete I dont use FS9 anymore but ORBX argued in another very long G3D thread that as the issue has been around in previous versions or FS and prior to any FTX scenery then they as a developer were not responsible. Of course it also happened in other regions if there is a lot of addon scenery but PNW became infamous for generating it. I nearly binned FSX after spending £1200 on a new cpu and gpu only to be plaqued with the crash in ORBX areas. Thanks to your great work you have saved the day and frustrations of many. Pity it wasnt sooner as I might have not pulled out all my hair

Having been ill recently, I've been missing many threads. I've now read through this thread in it's entirety.I know it's all getting a bit 'old hat', but I feel I too must add my thanks and gratitude to Pete for, yet again, contibuting such a major improvement to FSX and the FS community.There are many such 'unsung heros' of our community, Pete being right up there. It falls to the rest of us mere mortals to ensure they do not stay 'unsung'.Thank you also to the rest of those participating in this thread (and others like it).@ Stephen Re "I am beginning to feel even more of the idiot than I usually am! Not the brightest bulb in the world, that's for sure!!"Let's not forget the HUUUUGE amount of work YOU have done, and the help you supply in the hardware threads.

To ORBX, you've obviously didn't try hard enough to fix this, what a shame.

Maybe they did try but lacked the expertise and wealth of knowledge that Pete has !

I agree, thanks to the OP, Word Not Allowed and everyone else who participated in this thread. I know personally speaking high VAS seemed to help trigger the G3D error in areas I normally get it, lowering settings especially autogen and LOD seemed to help though I wasnt pleased with the visual results, seemed silly having fantastic scenery and not being able to appreciate it by lowered settings. I was getting errors at or before 3.5gb VAS seen it today in tests up at 3.7 and still running, pushed it to the max earlier and got a OOM error...great I thought as this is controllable at least and we know when and why it happens.I suggest a couple of days testing by everyone who has seen this alieviate their problems then make this baby public beyond avsim's general forum. Pete deserves all the credit he can get for this great achievement.

Just going to chime in here and say as a registered FSUIPC user for the past 10 years or so, its a program I could not live without. Just the control assignments and calibration options alone are worth the price of admission. Add in all the other 'fix' options (wind smoothing etc) and now this crash 'fix', it really is a gem of an addon.For all you guys who have just purchased as a 'thanks' to Pete.....enjoy all the benefits that FSUIPC provides. You will wonder how you managed without it!Thanks Pete!