Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
NoNewMessages said:http://www.sim-outhouse.com/sohforu...5-Ranger-Creek?p=286731&viewfull=1#post286731"
November 8th, 2009, 08:34 #23
NoNewMessages
Guest
"Originally Posted by Crusader
The plateau I refered to . I'm going to continue to adjust my mesh settings within FSX but if it is a Addon Mesh problem there is probably nothing I can do to correct it . I've actually gotten use to it . LOL The surrounding terrain is beautiful . (Just don't bother the bears!). Maybe someone using FSG Mesh Vers2 can take a few pics and see what they end up with .Rich"
Disclaimer: I develop and market products that contain addon mesh, but my comments are not intended to be of a marketing nature.
No adjusting of mesh settings will affect what you are seeing and I'll try to explain in as few words as possible. Default terrain around airports is at 1km resolution. For the metrically challenged, that's about 3/4 of a mile between data points. That's why there are no plateaus around default airports. Addon mesh, even of the same resolution as the default CONUS 38m, will override this 1km area and introduce visual anomolies.
An incorrectly placed airport or one that is at an incorrect elevation will only worsen the plateau effect that addon mesh can cause. Probably 80% of the airports are incorrectly positioned or elevated. One "solution" offered is to cut holes into a product to let the default 1km mesh show through, but this only works when an airport is at it's proper place and elevation. Thus for about, oh say 80% of the default airports, this will not work.
If Ed needs some addon mesh to work with, I'll be happy to obligize with some links.
As a customer of one vendor's product, I was disappointed that so many of the fields I would fly to were never "fixed". I know why that is and why that offered opportunity.
I believe I have parsed my words very carefully, but I do want to say the more informed the customer can be the better their decisons. There is more I *could* say, but I will leave it at Buyer Beware when it comes to addon mesh products."
GaryGB said:http://www.sim-outhouse.com/sohforu...5-Ranger-Creek?p=288040&viewfull=1#post288040
November 10th, 2009, 06:31 #33
GaryGB
Members +
Posts 221
Hi Olaf:
I just looked at the Raimondo Taburet add-on "10m_mesh.bgl" for FSX in the [Taburet Ranger Creek install path]\Scenery folder via FSX SDK TMF Viewer.
That file does NOT contribute any terrain data to Ranger Creek for an approximately LOD 11 sized area surrounding that location due to a "mesh cut-out" as described by "LCSims" above.
Thus one might conclude based on the info you provided above, that rendered terrain "anomalies" seen at Ranger Creek on your FSX configuration are likely the result of elevation data provided by your higher "10 Meter" (9.6 M) internal resolution FSG V2 add-on terrain mesh.
But more likely, FSG V2 mesh is depicting the "real world" terrain morphology accurately ...compared to what FSX default mesh can provide there.
On your FSX configuration, when Ranger Creek is rendered by FSX with the FSG mesh loaded, it apparently still retains the existing "real world" terrain morphology, and has NOT yet been "modified" in the FSG V2 release to "cut a hole out" around that airport; so the local terrain morphology seen is due to FSG's mesh (which is based on higher 10 Meter resolution source data).
The Taburet mesh provides NO terrain elevation data any closer than 1-1/2 LOD 13 quads to any side of the airport (the size of its "cut-out"); so the local terrain seen is the FSX default (which is based on lower 38 meter resolution source data).
[EDITED]
It is also apparent that the "10m_mesh.bgl" Taburet "cut-out" has allowed FSX to fall back to rendering terrain mesh elevation at a FSX LOD-2 level in the "dem0101.bgl" file, as we do see the following change in elevations between coordinates (aligned) along Ed's RWY Positions, logged via FSUIPC at FSX-rendered "ground" level: :iidea:
https://www.fsdeveloper.com/forum/threads/flattens.425495/post-632829
26 Mar 2013 #18
Hi Darren,
if you load the file ADE_FTX_ENG_EGBG_CVX.bgl, in \ORBX\FTX_EU\FTX_EU_ENG_05_SCENERY\scenery, into TMFViewer.exe, you can inspect our version of the sloped flattens at EGBG. These were manually placed in ADE, along with similar ones for more than 180 airports in FTX ENG. In other words, it may be tedious to place sloped flattens in this manner but it's not hard once you have figured out a workflow.
When I place sloped flattens (I didn't make those for FTX ENG and actually prefer SBuilderX) I turn off all autogen, slew around the airport along the surface to check how far out each sloped flatten polygon should reach, and use TCalcX to read out the local altitude for each polygon vertex. Other people use other approaches meaning you just figure out what works best for you.
The alternative approach is to use Global Mapper or similar GIS tools to blend you main airport flatten (platform) into your terrain mesh file, which is actually the approach ACES used for many of the default airports. The drawback is that you don't have fine control over the gradient of the surrounding slopes unless you go really fancy/complex and use more than a single fixed blending distance.
Cheers, Holger
Please tell me the details of this process. I have studied how to solve the FMMI airport problem for a long time, but still have not got an effective solution. How to use the old version of FMMI, please tell me in detail.Hello Gary,
Thank you very much for all these explanations.
I tried different things like the lowest mesh resolution but it didn 't work. It softened the hills but it was still a very strange sight.
I tried to use fsx's dem0704.bgl but same result.
I finally solved the problem by using an old free fmmi scenery and when using the lowest mesh resolution it works.
For those interested you can find this scenery here : https://www.avsimrus.com/f/fs2004-sceneries-44/antananarivo-2007-14605.html
View attachment 48630
Thank you very much for your reply, but I still don't know the details of the solution you described.The first thing you need to do is to exclude the default flatten Then, change the airport altitude to 1384.465 metres.
Finally create a new flatten at 1384.465 metres.
First of all, thank you very much for your reply. When I changed apx60380.bgl to apx60380.off and loaded the old version of FMMI airport in the order you mentioned, but after the restart, I did not find FMMI airport in P3DV4's select airport. You know how to solve this? or can you directly share the whole FMMI airport you have installed?Hello Ces8687
Here is how i did it :
Renamed APX60380 to .off in scenery/704/scenery
Put FMMI2007 somewhere and load it in the scenery.cfg in the following order:
1-FMMI mesh
2-FMMI airport
3-FMMI terrain
4-FMMI objects
( I use the freeware "Lorby Prepar3D V4 Addon Organizer" to manage my scenery in P3Dv4 http://www.lorby-si.com/downloads.html )
Also you have to turn off Mesh resolution in P3Dv4 (i think it is 325m) when flying to FMMI to get rid of the spikes.
I don't remember if the Madagascar mesh comes with the FMMI2007 package but just in case I will attach it there
https://drive.google.com/file/d/1KcPqRL-txPIdZrDL3i6jMZB4WyZ_-6rb/view
Thank you very much for your help, I can already take off and land FMMI normally.