Beware: X-Plane 10.4 = CFIT??

[asad112]

So, my I-3 attempt this evening came to an abrupt end:
https://www.youtube.com/watch?v=gjyq281LzIc

I have since learned I am not the only one having an issue, but still can't find any resolution. I submitted the bug to X-Plane, but any ideas? I am running typical scenery for SOCAL with HD Mesh. I was not having this issue on 10.3.

[Marcus Becker]

Interesting. I upgraded to 10.4 and use HD mesh and don't have that problem. I've been satisfied with the update so far.

[asad112]

Are you checking or unchecking "runways follow terrain contours"?

[davidspreckeriii]

Runway follows contour should always be unchecked if on PE. As for this, it was reported as a bug a long time earlier during the beta. I've not followed it, nor am I seeing it with my system (look up dasudea on twitch as system is on profile). I believe the reports tied it to hd mesh v3 or v2... I'll look up the original news I saw on this and get you more information once home.

[asad112]

Right, I guess until I figure out a way around this bug I can't really use PE then. I have tried every way possible, but I can't seem to get the scenery to display correctly without that option checked. I appreciate the help.

[theluckyone17]

I had that problem a while ago; wasn't related to 10.40 at all. I diagnosed it by removing all of my custom scenery into a "X-Plane 10\Disabled Scenery" folder, then used a "Split Half" diagnostic technique (http://www.peachpit.com/articles/articl ... 8&seqNum=3) to find the problematic scenery. Took a few afternoons to narrow it down.

For me, the problem ended up being KEDW. Not sure who's version it is, but it threw a fit on my system. Try disabling it, and see if it solves the issue. If not, use that split half technique to find out what airport is causing the problem. Sure, it takes time... but it's worth it in the end.

[Lumberhax]

I had that problem a while ago; wasn't related to 10.40 at all. I diagnosed it by removing all of my custom scenery into a "X-Plane 10\Disabled Scenery" folder, then used a "Split Half" diagnostic technique (http://www.peachpit.com/articles/articl ... 8&seqNum=3) to find the problematic scenery. Took a few afternoons to narrow it down.

For me, the problem ended up being KEDW. Not sure who's version it is, but it threw a fit on my system. Try disabling it, and see if it solves the issue. If not, use that split half technique to find out what airport is causing the problem. Sure, it takes time... but it's worth it in the end.

I second this. i just spent about 4 hours ripping my scenery aprart and starting and stopping X-plane god knows how many times but i tracked my problem down to a scenery called edwards afb

[asad112]

Thanks a lot Lumber! It does appear as if edwards afb was the culprit for me as well. Just really weird how there was no issue until I updated to 10.4. Thanks again!

[Keith Smith]

Great jobs, guys, glad you found the cause.

[flyingdrill]

Yes, it was Edwards AFB causing exactly the same problem for me. I can't thank you guys enough. Saved me hours of aggravation. Just a few lines of code screwed up all that area....... wow!