[FSX-Steam edition crashes in TERRAIN.DLL]

I think most of us who have experienced the 00059BE8 crash got it after several hours of continuous flight, rather than early on. I saved the flight plan where it happened to me, and will re-fly it to see if I get it again at the same place.

[FSX-Steam edition crashes in TERRAIN.DLL]

I’ve now seen three crash reports with exactly the same crash address, so I’m hopeful that my fix might help. Just not sure of the consequences of letting the sim try to carry on – it might just result in a different crash later on...

Make that four reports. I just looked back at the log in the Windows event viewer for a terrain.dll crash I had several days ago 4 hours into a planned 9-hour flight. The offset was indeed 00059BE8.

I'll definitely try the latest (Version 2) patch, although I won't have a chance to try another long-duration flight before this weekend.

I have only experienced the one terrain.dll crash to date - most of my subsequent FSX-SE flights have been 2 hours or less.

[FSUIPC 3.51 & Winds]

I think I like the option you've put in the .ini file of 3.5.1.1. So hopefully you'll go with that.

Well, I will for now. But there's a problem to solve still. With that set to its default "No", the wind at the aircraft as measured by the ASI is 180 degrees out. That must mean something. That is the 'bug' I set out to fix in the first place, and I've had to allow it back.

You can only really see this measurement easily on the ground, because when flying the larger TAS and complex vectors mask what is going on, and particularly makes it difficult to relate the instrument readings directly. More experiments, in scientific conditions, are going to be needed to get to the bottom of it.

Ah Ha! This answers a question which has puzzled me since the release of FS2004... i.e. the fact that when one taxis into the wind with the FS parameters displayed on screen via Shift-Z, the displayed ground speed increases, and decreases when taxiing with a tailwind. Exactly the opposite of what one would expect.

Thanks for the insight...

Jim Barrett