Ortho4xp Do not Flatten option

[STUART_H]

When using the 'Do Not Flatten' option in the Global Config, for specific airports, instead of using Patches, is there a way to smooth the changes in altitude on airports (runways and aprons), or does it depend on the mesh being used.  I have been using alpilotx HDMesh v3 or v4, but was wondering whether it would be better to use XP11 default scenery mesh when creating a tile for an airport? 

 Also whether adjusting curv_tool or min_angle parameters might help?

Thanks for any advice.

Stuart

[soaring_penguin]

Ortho4xp creates its own mesh from .hgt files that you can download from various sources on the web (see Elevation_Data subdir). You decide the resolution (curv_tol in Build Base Mesh). 

On top of this mesh, it drapes the photoreal textures. They are cut in smal triangels, lower curv_tol means higher complexity, but smaller triangles and more work for the renderer (in our case, X-Plane). This number will have high impact in mountains and you could end up using all your memory.

One would only use HD Mesh to create what is on top with the overlay option: autogen, roads, rails, tension lines and so on (in the base mesh, as well as in HDMesh, all this info is in the one mesh file).

So Ortho4XP does not use the elevation data from this mesh.

[STUART_H]

So from what your saying, perhaps in a tile with generally less mountains, e.g. Barcelona or Nice, it may be worth losing the curv_tool from say 3 to 1.5? Would that help with the sharp runway and apron elevation changes?

Stuart

[soaring_penguin]

On 16-1-2018 at 9:01 PM, STUART_H said:

So from what your saying, perhaps in a tile with generally less mountains, e.g. Barcelona or Nice, it may be worth losing the curv_tool from say 3 to 1.5?

Yes. Ortho4XP dynamically adjusts the number of triangles used, as it only needs the contours, it drapes the photo textures on top of it, there is no landclass definition needed.

I can not answer the question about the elevation changes, but better (higher) definition in the mesh should suit most airports better. But if you use flatten for the airport, then it will not follow the mesh contours and cliffs are the result. 

[STUART_H]

On 16/01/2018 at 7:12 PM, jh71 said:

Ortho4xp creates its own mesh from .hgt files that you can download from various sources on the web (see Elevation_Data subdir). You decide the resolution (curv_tol in Build Base Mesh). 

On top of this mesh, it drapes the photoreal textures. They are cut in smal triangels, lower curv_tol means higher complexity, but smaller triangles and more work for the renderer (in our case, X-Plane). This number will have high impact in mountains and you could end up using all your memory.

One would only use HD Mesh to create what is on top with the overlay option: autogen, roads, rails, tension lines and so on (in the base mesh, as well as in HDMesh, all this info is in the one mesh file).

 

Re your comment above re Alpilotx HD Mesh. If Ortho4xp is using it's own mesh when one creates the Base Mesh in Ortho4xp and one should only use these HD Mesh files to create the Ortho4xp Overlay, do these HD Mesh files actually need to reside in the Custom Scenery folder of XP11 and be loaded or could they reside elsewhere outside of XP?

little confused as, to what mesh is actually being used when using Ortho4xp, since Alpilotx HD Mesh is above the Ortho4xp folders in the Custom Scenery does it take precedence over the Ortho4xp created mesh?

Cheers,

Stuart

[soaring_penguin]

It is best to reference direct to the master: 

https://forums.x-plane.org/index.php?/forums/topic/105580-global-scenery-for-x-plane/&tab=comments#comment-1043765

at any time,only one mesh is loaded. If the HD mesh is above your orthos in the ini file then you should not see the imagery.