g3d.dll......help ..!

[Kosta 122]

So do you think I could force these errors on a default FSX install if I used even more insanely high LOD_RADIUS values? It would be interesting to try anfd make one happen on my developemt PC where i can see what really happens. If I can get the eventual hang you got maybe I could sort that then.To determine what a program is doing when it hangs you really do need to use a debugger.RegardsPete

No, I don't think so. I wasn't able to no matter what I did - I had default FSX and I virtually tested 20-30 sceneries for high VAS behaviour. And only some responded with g3d.dll, those are the ones I've been testing.I only observed some sceneries do that, and I tried to find what differs those sceneries from the others, why don't all other sceneries crash. And only conclusion was overwhelmingly high number of textures.I tried using LOD 15.5, 16.5, even up to 20 with default FSX, and all it would do is OOM, standard issue though.I don't know what a debugger is, not a programmer unfortunately.

[CoolP 283]

First of all, I think Pete deserves another round of praises for his efforts. Same for combined ones of the guys like Word Not Allowed and others of course. However, I may ask the question if the nature of the beast was understood now or if we're 'just' seeing a fix for .. something. Sounds way harsher than it was meant. Don't read it the wrong (insulting) way, please.I read that Pete stumbled into the g3d errors some weeks ago, whereas before that everything was working for him for example. So how come that the system suddenly starts to develop the error and what's the actual cause of that behaviour change? Since it was fixed in the Word Not Allowed test scenarios (copyright!), maybe the answer is available. So, if it turns out that FSUIPC fixed it, maybe a small summary of the thread can be given.

[aljones 15]

Pete, my hat to you Sir it works ! With high settings with VAS around 3.4, still no crash in my test flight over PNW ********* FSUIPC4, Version 4.749c by Pete Dowson *********User Name=User Addr=FSUIPC4 Key is providedWideFS7 Key is providedRunning inside FSX on Windows 7Module base=61000000 63 System time = 29/11/2011 11:18:53 63 FLT UNC path = "AL-NVIDIA-PCFlight Simulator X Files" 406 Trying to connect to SimConnect Acc/SP2 Oct07 ... 406 FS UNC path = "D:Microsoft Flight Simulator X" 656 LogOptions=00000000 00000001 656 Wind smoothing fix is fully installed 656 G3D.DLL fix attempt installed ok 656 SimConnect_Open succeeded: waiting to check version okay 656 Trying to use SimConnect Acc/SP2 Oct07 3651 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 3651 Initialising SimConnect data requests now 3651 FSUIPC Menu entry added 3698 D:Microsoft Flight Simulator XFLIGHTSOTHERFLTSIM.FLT 3698 D:Microsoft Flight Simulator XSimObjectsAirplanesAircreation_582SLAircreation_582SL.AIR 40951 D:Microsoft Flight Simulator XSimObjectsAirplanesCarenado Centurion T210Carenado_T210.AIR 54382 C:UsersAl-nVidiaDocumentsFlight Simulator X FilesVFR Orcas I to Portland Intl.PLN 115223 C:UsersAl-nVidiaDocumentsFlight Simulator X FilesVFR Orcas I to Portland Intl.PLN 115223 Weather Mode now = Theme 115223 AL-NVIDIA-PCMicrosoftFSXPrevious flight.FLT 180431 System time = 29/11/2011 11:21:54, Simulator time = 11:18:58 (19:18Z) 180431 Aircraft="T210 CENTURION BLUE CLASSIC" 180946 Starting everything now ... 182178 Advanced Weather Interface Enabled 888473 **** G3D Bad pointer: 0x2455E453 888473 Last file="D:Microsoft Flight Simulator XMyTrafficAircraftF15MXmodelF15-Eagle" 888723 **** G3D Bad pointer: 0x2455E453 888723 Last file="D:Microsoft Flight Simulator XMyTrafficAircraftF15MXmodelF15-Eagle" 888847 **** G3D Bad pointer: 0x2455E453 888847 Last file="D:Microsoft Flight Simulator XMyTrafficAircraftF15MXmodelF15-Eagle" 1559667 **** G3D Bad pointer: 0x0A5E2E9B 1559667 Last file="D:Microsoft Flight Simulator XMyTrafficAircraftChall850MXmodelChallenger850" 2710440 **** G3D Bad pointer: 0x1B640FF1 2710440 Last file="D:Microsoft Flight Simulator XMyTrafficAircraftCRJ7MXmodel.WideFSXcrj700-wide" 2710845 **** G3D Bad pointer: 0x11DD2A6A 2710845 Last file="D:Microsoft Flight Simulator XMyTrafficAircraftCRJ7MXmodel.WideFSXcrj700-wide" 2710923 **** G3D Bad pointer: 0x11DD2A6A 2710923 Last file="D:Microsoft Flight Simulator XMyTrafficAircraftCRJ7MXmodel.WideFSXcrj700-wide" 2711610 **** G3D Bad pointer: 0x11DD2A6A 2711610 Last file="D:Microsoft Flight Simulator XMyTrafficAircraftCRJ7MXmodel.WideFSXcrj700-wide" 3025390 Sim stopped: average frame rate for last 2845 secs = 28.1 fps 3028931 C:UsersAl-nVidiaDocumentsFlight Simulator X FilesVFR Orcas I to Portland Intl.PLN 3064359 System time = 29/11/2011 12:09:58, Simulator time = 11:18:57 (19:18Z) 3064359 *** FSUIPC log file being closedAverage frame rate for running time of 2845 secs = 28.1 fpsG3D fix: Passes 112394, Null pointers 0, Bad pointers 8Memory managed: 1279 Allocs, 1279 Freed********* FSUIPC Log file closed ***********Alain from Montreal

[Jean-Paul 167]

First of all, I think Pete deserves another round of praises for his efforts. Same for combined ones of the guys like Word Not Allowed and others of course.

[Kosta 122]

OK, LOWI flight is finished, VAS in the end 3.7 GB, successful landing. I was never able to achieve this previously.So, a bit more testing is needed to see if this really is the holy grail of g3d.dll fix, and we must be sure if it doesn't impact other functions - it would have to clear what it does.Btw. Pete, some feedback from the last flight which should have caused g3d.dll at least 3 times:********* FSUIPC4, Version 4.749c by Pete Dowson *********User Name="xxxxxxxxxxxxx"User Addr="xxxxxxxxxxxxx"FSUIPC4 Key is providedWideFS7 Key is providedRunning inside FSX on Windows 7Module base=61000000 62 System time = 29/11/2011 17:20:24 93 FLT UNC path = "SOUNDTRACKERHDD-D-StorageMy DocumentsFlight Simulator X Files" 109 Trying to connect to SimConnect Acc/SP2 Oct07 ... 109 FS UNC path = "SOUNDTRACKERHDD-E-FSXFSX" 280 LogOptions=00000000 00000001 296 Wind smoothing fix is fully installed 296 G3D.DLL fix attempt installed ok 296 SimConnect_Open succeeded: waiting to check version okay 296 Trying to use SimConnect Acc/SP2 Oct07 1341 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 1341 Initialising SimConnect data requests now 1341 FSUIPC Menu entry added 1357 SOUNDTRACKERHDD-D-Storagemy documentsflight simulator x filesDefault.FLT 1372 SOUNDTRACKERHDD-E-FSXFSXSimObjectsAirplanesC172Cessna172SP.AIR 46956 SOUNDTRACKERHDD-E-FSXFSXSimObjectsAirplanesPMDG 737-700NGX WLB737-700WL.AIR 64288 System time = 29/11/2011 17:21:28, Simulator time = 09:24:07 (08:24Z) 64303 Aircraft="Boeing 737-7Z9NGX Austrian Airlines Winglets" 122070 Starting everything now ... 130978 Advanced Weather Interface Enabled 186202 Sim stopped: average frame rate for last 56 secs = 31.2 fps 693190 Sim stopped: average frame rate for last 504 secs = 30.5 fps 740568 Sim stopped: average frame rate for last 28 secs = 24.2 fps 1374010 **** G3D Bad pointer: 0x1ACC2B39 1374010 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1374056 **** G3D Bad pointer: 0x28307FF3 1374056 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1394883 **** G3D Bad pointer: 0x7541B568 1394883 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1394883 **** G3D Bad pointer: 0x7541B568 1394883 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1394883 **** G3D Bad pointer: 0x7541B568 1394883 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1394914 **** G3D Bad pointer: 0x7541B568 1394914 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1394914 **** G3D Bad pointer: 0x7541B568 1394914 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1394914 **** G3D Bad pointer: 0x7541B568 1394914 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1394961 **** G3D Bad pointer: 0x7541B568 1394961 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1394961 **** G3D Bad pointer: 0x7541B568 1394961 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1394961 **** G3D Bad pointer: 0x7541B568 1394961 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395007 **** G3D Bad pointer: 0x7541B568 1395007 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395007 **** G3D Bad pointer: 0x7541B568 1395007 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395039 **** G3D Bad pointer: 0x7541B568 1395039 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395039 **** G3D Bad pointer: 0x7541B568 1395039 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395039 **** G3D Bad pointer: 0x7541B568 1395039 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395039 **** G3D Bad pointer: 0x7541B568 1395039 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395085 **** G3D Bad pointer: 0x7541B568 1395085 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395085 **** G3D Bad pointer: 0x7541B568 1395085 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395132 **** G3D Bad pointer: 0x7541B568 1395132 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395132 **** G3D Bad pointer: 0x7541B568 1395132 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395132 **** G3D Bad pointer: 0x7541B568 1395132 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395163 **** G3D Bad pointer: 0x7541B568 1395163 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395163 **** G3D Bad pointer: 0x7541B568 1395163 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395163 **** G3D Bad pointer: 0x7541B568 1395163 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395210 **** G3D Bad pointer: 0x7541B568 1395210 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395210 **** G3D Bad pointer: 0x7541B568 1395210 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395210 **** G3D Bad pointer: 0x7541B568 1395210 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395819 **** G3D Bad pointer: 0xC66FFBE3 1395819 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395819 **** G3D Bad pointer: 0xC66FFBE3 1395819 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395865 **** G3D Bad pointer: 0xC1210362 1395865 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395865 **** G3D Bad pointer: 0xC1210362 1395865 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395912 **** G3D Bad pointer: 0x0532766B 1395912 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395912 **** G3D Bad pointer: 0x0532766B 1395912 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395912 **** G3D Bad pointer: 0x0532766B 1395912 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395912 **** G3D Bad pointer: 0x0532766B 1395912 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395959 **** G3D Bad pointer: 0xBFFCBC49 1395959 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395959 **** G3D Bad pointer: 0xBFFCBC49 1395959 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395959 **** G3D Bad pointer: 0xBFFCBC49 1395959 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395990 **** G3D Bad pointer: 0xBFFFA881 1395990 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1395990 **** G3D Bad pointer: 0xBFFFA881 1395990 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1396037 **** G3D Bad pointer: 0xBFDB34B9 1396037 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1396037 **** G3D Bad pointer: 0xBFDB34B9 1396037 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1396037 **** G3D Bad pointer: 0xBFDB34B9 1396037 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1396333 **** G3D Bad pointer: 0x0C8EA213 1396333 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1396458 **** G3D Bad pointer: 0x1EF70FF3 1396458 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1396505 **** G3D Bad pointer: 0x22DE4F83 1396505 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1396505 **** G3D Bad pointer: 0x087D174B 1396505 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 1769847 **** G3D Bad pointer: 0x0FB83D9D 1769847 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2664294 **** G3D Bad pointer: 0x018B63AD 2664294 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2664746 **** G3D Bad pointer: 0x19A126ED 2664746 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2664778 **** G3D Bad pointer: 0x0E2D3C41 2664778 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2664856 **** G3D Bad pointer: 0x1D22693D 2664856 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2664887 **** G3D Bad pointer: 0x38595A79 2664887 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2664965 **** G3D Bad pointer: 0x0046ADBD 2664965 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2664965 **** G3D Bad pointer: 0x1B0DBF9D 2664965 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2665012 **** G3D Bad pointer: 0x193D29B5 2665012 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2665012 **** G3D Bad pointer: 0x1B0DBF9D 2665012 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2665043 **** G3D Bad pointer: 0x007EE865 2665043 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2665214 **** G3D Bad pointer: 0x09511FF5 2665214 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2665246 **** G3D Bad pointer: 0x00DF81A5 2665246 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2665495 **** G3D Bad pointer: 0x09003CBD 2665495 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2665589 **** G3D Bad pointer: 0x1DB117A5 2665589 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2665589 **** G3D Bad pointer: 0x08CA700E 2665589 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2665589 **** G3D Bad pointer: 0x0908B2FD 2665589 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2666088 **** G3D Bad pointer: 0x07F18478 2666088 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2666431 **** G3D Bad pointer: 0x36194A1B 2666431 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2666478 **** G3D Bad pointer: 0x2BF0FAC9 2666478 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2666509 **** G3D Bad pointer: 0x1CE8D375 2666509 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2666665 **** G3D Bad pointer: 0x09511FF5 2666665 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2666806 **** G3D Bad pointer: 0x0B60E63B 2666806 Last file="E:FSXSimObjectsAirplanesPMDG 737-700NGX WLmodelPMDG_737_700WL" 2780811 Sim stopped: average frame rate for last 2036 secs = 31.3 fps

[Pete Dowson 558]

However, I may ask the question if the nature of the beast was understood now or if we're 'just' seeing a fix for .. something.

There's really no fix without having the FSX source code, debugging the issue properly, and correcting the code. Hopefully Lockheed-Martin will be doing this for Prepar3D.

I read that Pete stumbled into the g3d errors some weeks ago

No. I've been reading this thread since it started, and feeling a bit sorry for folks, but i haven't had any such crash since i got my new PC some 6 months ago, until Monday (yesterday) when i got one in a place I use for regular testing and have never had such a problem before. I have no idea what changed, but something did -- presumably something else I've installed recently.

So, if it turns out that FSUIPC fixed it, maybe a small summary of the thread can be given.

It can't "fix" it. All I'm trying to do is to stop the symptom being a crash. The symptom may then be something else, like a graphics glitch, or, as I've said before, it may propagate into other areas. Because if it is really memory corruption as it looks, then it's anyone's guess as to what happens next -- like the hange Word Not Allowed mentioned. I don't like those either, so if i can trap them i'll try to force avoiding action there too.All I want to try to do is allow the flight to continue. This is by trapping the error when it occurs and trying to force FS to ignore it and carry on (albeit with a report in the Log so at least you know it occurred). This has always been my philosophy with my programs. I cannot abide crashes, they are horrible. i don't have quite so much hatred for errors as long as you can recover and carry on. With my software i report those in the Logs and fix them. I don't think I can really fix FSX.RegardsPete

[CoolP 283]

Lets see what the next days bring in regard to the 'fix', Pete. More reports may come in. But I think Word Not Allowed's reports already show a vast improvement and your philosophy (again) proved to be a very good one I think. Thanks for your efforts again.I've already bought your software some years back. For good reason.

[Pete Dowson 558]

Btw. Pete, some feedback from the last flight which should have caused g3d.dll at least 3 times:

How do you get a G3D crash three times -- surely the first one finishes your flight?I see there's a lot of bad pointer logging. Maybe i should make that optional -- though probably not, because it is a serious issue after all and probably shouldn't be hidden at all.Pete

[CoolP 283]

So the pointer doesn't show a corrupted file by design (livery or model or something), but just that it was processed last and somehow got corrupted in the memory handling? Sorry for asking somehow stupid.

[Pete Dowson 558]

No, I don't think so. I wasn't able to no matter what I did - I had default FSX and I virtually tested 20-30 sceneries for high VAS behaviour. And only some responded with g3d.dll, those are the ones I've been testing.I only observed some sceneries do that, and I tried to find what differs those sceneries from the others, why don't all other sceneries crash. And only conclusion was overwhelmingly high number of textures.I tried using LOD 15.5, 16.5, even up to 20 with default FSX, and all it would do is OOM, standard issue though

This does very strongly imply that the code in FSX isn't so much flawed as very sensitive to the files it reads being exactly the way it expects them to be. Theoretically there should be no difference in the nature of the files it reads in its default installation to those it must read in a well-enhanced installation. There should certainly be enough quantity with all sliders up and a very high LOD setting for it to use all of its memory -- OOM as you saw -- and therefore be in the same potential corruption scenario.So, it sounds like some scenery or aircraft (or both) designers have either taken some liberties with the data capabilities, stretching them beyond or outside the specifications, or the folks who wrote the specifications for the SDKs, and maybe built some of the tools therein, made some incorrect assumptions (or mistakes) compared to the actual programmers who wrote the code.Such things do happen when the jobs relating to the same functions are shared or even belong to different teams, as was quite likely. it wasn't a small department.One potentially useful thing to consider doing would be to write a program which would read and check all the BGL and MDL files (and others of that ilk?) and report any which stray from the 'rules'. The problem with this is the interpretation of those rules, and there we are stuck. All the available definitions with sufficient detail have been produced by folks outside MS, by reverse engineering. And there lies the rub.Pete

So the pointer doesn't show a corrupted file by design (livery or model or something), but just that it was processed last and somehow got corrupted in the memory handling? Sorry for asking somehow stupid.

The bad pointer logged is definitely a bad pointer, but it isn't related to anything useful. In fact it turned out not to be useful information at all. I just hoped.The file logged is the last file used bt the routines which are calling the function which is (otherwise) crashing. FSUIPC locates it on the stack by using stack analysis. I would assume that the function crashing is using data from that file, but that doesn't mean the file itself it corrupted, only that the memory structure it is contained within is corrupt.So again, it really doesn't turn out to be terribly useful information. Again I just hoped.Maybe I should just log the fact that a G3D.DLL crash has just been averted, and leave it at that.Pete

[CoolP 283]

Maybe I should just log the fact that a G3D.DLL crash has just been averted, and leave it at that.

Seriously, if you would add a donate button next to that report, I would use it if it has just prevented my flight ending 5nm out of the threshold. Could be that some other folks will act the same way.As said, if the reports in the next days show that your fix prevents those things from happening and letting people ending their flights, you deserve some, Pete. Avsim lifetime achievement award, you already have that one.

[Pete Dowson 558]

Seriously, if you would add a donate button next to that report, I would use it if it has just prevented my flight ending 5nm out of the threshold. Could be that some other folks will act the same way.

Well, I could have made it a Registered User facility only. But sales are generally good inany case, so I'm not complaining. Maybe more folks will install it as a result of this and may then decide it is worth purchasing.RegardsPete

[CoolP 283]

Very good attitude IMHO.

[Kosta 122]

How do you get a G3D crash three times -- surely the first one finishes your flight?

No, I didn't get G3D crash per se. I passed the airports which are "supposed" to cause the crash. And it's kinda visible from the LOG, as you can divide timing of the error into 3 separate time-parts.I was flying from EGKK to LOWI, that brings me past EBBR and EDDF, both airports that cause g3d.dll crash when flying over them. EBBR was always causing the error, and EDDF only with relatively high VAS usage. LOWI was by default always crashing, especially with NGX or higher LOD than 4.5.But now I had everything activated, I made sure I was looking at the airport as I was passing them, I saw them fully load and still I was able to make a fully successful land into LOWI.

[Kosta 122]

This does very strongly imply that the code in FSX isn't so much flawed as very sensitive to the files it reads being exactly the way it expects them to be. Theoretically there should be no difference in the nature of the files it reads in its default installation to those it must read in a well-enhanced installation. There should certainly be enough quantity with all sliders up and a very high LOD setting for it to use all of its memory -- OOM as you saw -- and therefore be in the same potential corruption scenario.So, it sounds like some scenery or aircraft (or both) designers have either taken some liberties with the data capabilities, stretching them beyond or outside the specifications, or the folks who wrote the specifications for the SDKs, and maybe built some of the tools therein, made some incorrect assumptions (or mistakes) compared to the actual programmers who wrote the code.Such things do happen when the jobs relating to the same functions are shared or even belong to different teams, as was quite likely. it wasn't a small department.One potentially useful thing to consider doing would be to write a program which would read and check all the BGL and MDL files (and others of that ilk?) and report any which stray from the 'rules'. The problem with this is the interpretation of those rules, and there we are stuck. All the available definitions with sufficient detail have been produced by folks outside MS, by reverse engineering. And there lies the rub.

OK, I think you are right about this one, the error might be anywhere. But, how come that other developers are successfully creating sceneries which don't crash. There must be something behind it, and I hardly doubt it's the SDK.I'm very much positive that the FSX itself is not faulty, but as you said, sensitive. And if you notice, the sceneries that are reportedly almost never crashing are also mostly best performing (not to name some).