Here it is:********* FSUIPC4, Version 4.749a by Pete Dowson *********

Aha. The 'a' version, which was deleted a while back, was found not to work. it was the first experiment. Only the c and d versions work, but c is also now withdrawn.Pete

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!!

You see what you started??

Well, I just completed my "test flight" and, 24 days and more than 400 posts since my first post on this subject, I have finally managed to complete a flight to EBBR...!!!!! WOW...that's fantastic...!Pete, this is my FSUIPC log after this flight...********* FSUIPC4, Version 4.749d by Pete Dowson *********User Name=xxxxUser Addr=xxxxFSUIPC4 Key is providedWideFS7 Key is providedRunning inside FSX on Windows 7Module base=61000000 1326 System time = 29/11/2011 23:36:01 1326 FLT UNC path = xxxx 1778 Trying to connect to SimConnect Acc/SP2 Oct07 ... 1778 FS UNC path = xxxx 1965 LogOptions=00000000 00000001 1965 Wind smoothing fix is fully installed 1965 G3D.DLL fix attempt installed ok 1965 SimConnect_Open succeeded: waiting to check version okay 1965 Trying to use SimConnect Acc/SP2 Oct07 3744 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 3744 Initialising SimConnect data requests now 3744 FSUIPC Menu entry added 3759 xxxxMicrosoft Flight Simulator XFLIGHTSOTHERFLTSIM.FLT 3759 xxxxMicrosoft Flight Simulator XSimObjectsAirplanesAircreation_582SLAircreation_582SL.AIR 8096 Weather Mode now = Global 32744 xxxxMicrosoft Flight Simulator XSimObjectsAirplanesPMDG 737-800NGX WLB737-800WL.AIR 64927 System time = 29/11/2011 23:37:05, Simulator time = 09:36:04 (07:36Z) 64927 Aircraft="PMDG 737-800NGX PMDG House Winglets" 137218 Weather Mode now = Theme 137358 Weather Mode now = Global 137655 Starting everything now ... 141056 Advanced Weather Interface Enabled 146110 Weather Mode now = Theme 146266 Weather Mode now = Global 3791853 *** G3D bad pointer trapped and crash prevented *** 3950116 *** G3D bad pointer trapped and crash prevented *** 4693212 Sim stopped: average frame rate for last 4556 secs = 27.1 fps 4697876 xxxxUsersxxxxAppDataRoamingMicrosoftFSXVolo precedente.FLT 4714241 System time = 30/11/2011 00:54:34, Simulator time = 10:51:59 (08:51Z) 4714241 *** FSUIPC log file being closedAverage frame rate for running time of 4560 secs = 27.1 fpsG3D fix: Passes 160989, Null pointers 0, Bad pointers 76, Separate instances 76Memory managed: 4109 Allocs, 4109 Freed********* FSUIPC Log file closed ***********The lines above show that this fix can prevent crashes. Guys, maybe this fix cannot prevent all crashes and maybe we really need some "beta testing period" before we can say we are out of this issue, but certainly this is a giant step forward...!Pete, thank you very much indeed, and thank you also to Word Not Allowed and all the others who made extensive testing on this subject on the last three weeks (and also before..!!). Regards

And thank you for starting the thread Jackson.

My consistent CTD was KPDX to KSEA via LACEE with PNW active. Consistent failure to complete - until today. Thanks to all for the positive work on this. Successfully completed tonight with McPhat paint on PMDG 747 and ASE running, nearly all sliders to the right with A/G at Very Dense. The work by Pete is a significant contribution to extending the life of FSX and allowing IFR ops in PNW and other regions (I have also had CTDs in Europe with the sceneries mentioned in the thread). Thank you Pete!

That does the trick. All my difficult crash points have become entirely crash free so far. Congratulations Pete!Kind regards,

FWIW I checked through my logs and my g3d.dll crash (version 61472) is always as 63581, which seems like a different area then you guys are seeing? Also my failure mode is a little different, I am mostly crashing during the initial situation load, normally between 90%-94% and it happens about 4 of 5 tries for a given time/start position. Only once after getting a good situation load did I get g3d fault in flight (about 15 min into the flight).I have recently been tweaking the airports in the area, and AFAICT my g3d crashes started after installing a lot of AI flight plans. The aircraft are all fs9 installed into fsx and I went through the textures and updated as needed so the diffuse ones are DXT3 with alpha set and with mips.scott s..

Could this also help prevent g3d.dll crash for FS9? i get this crash whenever flying into the KPDX add-on area.

Thanks a million Pete, I successfully completed Al's KORS > KPDX flight (well the rediculous landing fees at KPDX dictated a landing at Troutdale instead, but...). Works very well, really appreciate your efforts on this :)Jim

Wow. It's like an brand new holiday has just been invented. A hundred huzzahs for Pete!

Pete should get a dozen of FlightSim Oscars for his lifework

Pete, this is my FSUIPC log after this flight... 3791853 *** G3D bad pointer trapped and crash prevented *** 3950116 *** G3D bad pointer trapped and crash prevented ***...G3D fix: Passes 160989, Null pointers 0, Bad pointers 76, Separate instances 76

Ah, I spot a silly little bug, but only in my Logging. The "separate instances" above should be 2. The 76 refers to how many times the (probably) same, or at least related, corrupted pointers had to be "fixed" (avoided in fact).It's of no real consequence as you can count the *** G3D lines, but I'll fix it here ready for the next interim update, or 4.75, whichever comes next.RegardsPete

Awesome Pete as this has plagued FSX of late. I actually stopped using it.As posted above, can you do the same "trick" for the FS9 version of FSUIPC?I will nominate you for PM here.

FWIW I checked through my logs and my g3d.dll crash (version 61472) is always as 63581, which seems like a different area then you guys are seeing? Also my failure mode is a little different, I am mostly crashing during the initial situation load, normally between 90%-94% and it happens about 4 of 5 tries for a given time/start position. Only once after getting a good situation load did I get g3d fault in flight (about 15 min into the flight).

Yes, that's a different matter altogether, and does sound like corrupt data someplace in your files rather than the overload situation which appears to cause the one I worked on. Is yours also an access violation error (0xC0000005 error code)? It looks like it crashes when trying to access a floating point value from an incoming data set -- one of the files it needs to read appears corrupted or probably truncated.You might be able to identify it by installing ProcMon from www.sysinternals.com, and running it whilst starting FSX. It will log all sorts of things -- best set the Filter to include operation "CreateFile" and nothing else, with Process name including "FSX" -- i.e. add those two filter lines in the Filter dialogue. When FSX crashes see what the last file was.RegardsPete