PilotEdge Forums

Just updated to 10.40 and you guys saved me hours of work trying to understand why many of my airports were in a valley. Problem was edwards afb

Thanks

Removing Edwards corrected the 'San Andreas' problem for me as well. THANK YOU for posting this!

Runways follow terrain contours unchecked.

Have a look at Yucca Valley (L22) - even after the Edwards AFB correction. It looks like a ski slope. I have the HD Mesh v2. Maybe that's it, but it was no problem in 10.36. Does anybody else have this problem, or do I need to go digging alone?

Also (against Ben Supnik's and my better judgment), I installed El Capitan on the iMac. Very nice, but not for X-Plane. The well reported SASL issue is a real nuisance. They'll fix it, but it may be a wait - as it's Apple that is in the frame, rather than the XP developers......

From reading of blogs and such I was under the impression that this is why scenery priority was added. IE as a way to positively control the exact order things are loaded. Is there a solution hiding here?

http://www.x-plane.com/?article=changin ... x-plane-10

http://www.x-plane.com/?article=priorit ... nery-packs

http://developer.x-plane.com/2014/09/pr ... ion-zones/

http://forums.x-plane.org/index.php?showtopic=89011

My .ini file looks to be in the proper order. This is not as much of a problem as the SASL crash in El Capitan. Not visiting L22 is hardly going to mess up my day However, if I find any "important" airfields badly affected, I shall try and narrow down the cause by the half/half method - when I've got a lot of time on my hands!

It's my understanding that problem lies within the apt.data and from what I read if the code is 00.000.00 or something to that effect it creates a taxi way that spans the earth and if you have runways follow terrain off it makes everything level with that taxi way. At least that's my understanding anyway. So it's not so much the priority loading as it is the scenery developers need to pay close attention to the apt.data as we have all seen the effect it has on 10.40

Thanks, Lumberhax. So, now we have to search to find offending data in all those apt.dat files in our custom scenery. Or hope that the developers have seen what happens, and adjust things for us. 10.36 works well. Roll back?