Totally agree with you. Im really enjoying learning about it and making my own airports. Actually now i spent 80% of the time on WED and 20% on XP. 😀

Ben, Carrotroot.
Thanks. I’ll do another research later, for now i’ll focus on another airport that i found and the terrain is almost exactly like it is in RL.
Thanks guys.

Roberto, please move this to the x-plane-scenery yahoo mailing list or one of the forums.

Thanks!
Ben

Meshtool and vertex tool will not work with v10 scenery. Please ask your question on an appropriate forum.

carrotroot,

Thanks for the answer, still i have the problem.

1) I haven’t said it is a bug. But its something making hard to build more accurate airports. Even if they are not going to look realistic but only based on the real airports, the terrain should look similar at least.

2) Indeed, haven’t tried it before, but doesn’t help because there is no objects or forests on the way.

3) I spend days searching for the answer. Haven’t found a solution on Avsim and neither on XP.org. There are some topics regarding terrain but for now looks like there is no easy fix.
My problem is that the object doesn’t follow the terrain inclination in degrees, so the object is “sitting” on a flat ground, but actually the terrain is not flat.
After reading a lot of it and searching for the answer i understood that XP checks the objects 3 informations, lat, long and heading, and a 4 fourth info that is the MSL when you set it. I used it, it was not working because it is not an .obj file, but an .agp file (Med_Orange_Hangar.agp). And since im looking forward to send the airports to Robin, i can only use the objects that are already in Wed’s library.
There is 2 solutions i have found for the terrain, mesh tool and vertex tool.
Both are not easy to use (for me), i even got the .”hgt” file to use the mesh tool, but i had to change a much bigger part of the terrain and i was only looking to fix a small area around the airport. So for both tools i have 2 problems (i believe)
1 – Not easy to use (im no dev)
2 – I don’t think i can send the terrain to Robin

So as you can see i did an extensive search on the subject. In this particular airport the solution would be to flatten the terrain or to have a 5th information for the object, so lat, long, heading, msl, inclination. But i guess this 5th information is not used probably because would make the scenery heavier for the CPU.

Anyway thanks.
Im looking for another airports for now while there isn’t an easy terrain tool.

Jim, thanks for the help.
I tried, but still it doesn’t fix it. There is actually nothing around the airport except a single road. Still, the problem is with the terrain itself, not the objects. I tried creating an “airport boundary” and also an exclusion zone, the airport boundary works, but only if i uncheck in rendering options the “runway follow terrain contours” feature, but this is something i don’t want to.
I think the only way for me to fix it, will be in the future with an easier to use mesh tool.
Thanks

1) This is not a bug – and if it was, use the bug report link at the top of this page. Not the comment section.

2) Exclusions will not help

3) Please ask your question on one of the many forums dedicated to this stuff, such as avsim, x-plane org, or x-pilot (just to name a few). There are tools which will fix this, you just have to do some research … it’s not hard, google is your friend.

Yeah, you can easily create your own sceneries using WED, I’ve made 1 airport and I’m currently creating my second one… It may take you some time, and some practice, but in the end, it will worth! 🙂

Roberto, try outlining your airports with an exclusion zone and see if that fixes your problems.

Cheers,
Jim

I’m not so sure that is necessary. I have the latest download of the C172 and the SASL version still indicates as Piet said. Yet the aircraft functions properly. Carenado must simply have a different internal version number, or, the number itself hasn’t been updated.

Either way, Piet should just enjoy his C172.