Post
by dmitriys » Fri Aug 08, 2014 7:33 am
I talked to FS Global support and they have replied that is't because OMDB has his own mesh conflicts with FSGU.
-
Hello!
I understand you concern.
However, I fear, I can not be of any help. Disabling the mesh area of Dubai will also disable large other areas as our BGLs cover large areas. Furthermore you will see ugly borders when you overfly the border of default with FSG mesh.
We do not support this. If we would, people would disable all areas, which makes it questionably why have a mesh.
No, the approach must be: correct the "false" product and not revert the correct product back to false. The FSG mesh always is correct. In other words: in 99,99% of cases which are presented to us under the option "wrong mesh" it turns out the airport is missplaced or some
other data is wrong.
We preach since 1998, that add-on designers must not build on ground they do not own.
I own the ground, when I make my own micromesh in HIGH LOD resolution (regardless of resolution of source data). This ensures, that the add-on micromesh supercedes the lower LOD default (here = FSGU) mesh. They have not done it, so our mesh seemes to supercede theirs. Our mesh does not have high LOD numbers. Any Add-on dev can find them out using TMF viewer and program his LOD a number higher to make sure it covers ours.
So, if Fly Tampa has a mesh in DUB area, they should recompile it using LOD 12 or so. It will then supercede ours and all should be fine. If they don't have a mesh, but built on FSX default mesh, they must create one.
We always encourage add-on developers to contact us for testing and cooperation.
Unfortunately only very few do.
Cheers!
Stefan Schaefer
.you can delete our Dubai mesh which is the file add-on sceney /flytampa-dubai/scenery/dubai-mesh.bgl. that way you will only be running their global mesh.