Willhelm
commented
in reference to scenery pack
100426on January 31, 2024 12:46 AM
Julian Admin January 29, 2024 2:19 AM
Use of large 'lib/airport/ground/terrain/' polygons should be avoided. Airport boundary will create plausible terrain at airport following a future Global scenery mesh cut.
I tried it without 'lib/airport/ground/terrain/' assets, but airport boundary do not create plausible terrain at all. I´m using grass_lawn_tracks_1(2,3,5).pol which are available LR assets. I can remove problematic polygons, but then scenery will look weird. These new assets practicaly allows developers to recreate grass airport terrains according ESRI ortho, so I do not fully understand why we can not use them. Is there any article concerning mentioned "future Global scenery mesh cut" which would help me understand why my sceneries using grass_lawn_tracks_ polygones can not be approved for XP12 global airports improvement? Thanks
You must be logged in to participate in the discussion
Julian Admin January 29, 2024 2:19 AM Use of large 'lib/airport/ground/terrain/' polygons should be avoided. Airport boundary will create plausible terrain at airport following a future Global scenery mesh cut.
I tried it without 'lib/airport/ground/terrain/' assets, but airport boundary do not create plausible terrain at all. I´m using grass_lawn_tracks_1(2,3,5).pol which are available LR assets. I can remove problematic polygons, but then scenery will look weird. These new assets practicaly allows developers to recreate grass airport terrains according ESRI ortho, so I do not fully understand why we can not use them. Is there any article concerning mentioned "future Global scenery mesh cut" which would help me understand why my sceneries using grass_lawn_tracks_ polygones can not be approved for XP12 global airports improvement? Thanks