• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    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.

Terrain mesh on US-Mexico border

Messages
496
Country
us-missouri
What do you do when your terrain mesh data only covers the United States, and Mexico becomes a gigantic hole with million-foot spikes at the border? USGS data does not include Mexico or Canada.
Capture.JPG


Above is the San Diego, Calif. region. In the lower-right corner should be Mexico. TMFViewer shows elevation in purple areas as -575. What can I put in my INF file so P3D's default scenery shows through, and my terrain mesh BGLs don't punch a hole in Mexico?
Code:
[Source]
Type=GeoTIFF
Layer=Elevation
NullValue = 0,0,0
SourceDir="."
SourceFile="n33w118.tif"
PixelIsPoint=0
ulxMap=-118.000555555555
ulyMap=33.0005555555552
xDim=9.25925925258432E-05
yDim=9.25925925258432E-05

[Destination]
DestDir="."
DestBaseFileName="n33w118"
FractionBits=3
LOD=4,12
 

Attachments

  • 1607115990708.jpeg
    1607115990708.jpeg
    72 KB · Views: 93
Last edited:

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,882
Country
netherlands
Hi,

What is the no data value in your source data? You need to configure that in the inf file, so that the sim now there is no data in certain areas.
 
Messages
496
Country
us-missouri
Hi,

What is the no data value in your source data? You need to configure that in the inf file, so that the sim now there is no data in certain areas.
Hello Arno, The purple areas from the TMFViewer image show up as "no data" when I examine the USGS source GeoTIFF file in QGIS. Black areas from QGIS (seen below) become white "0" elevations in TMFViewer. The white "no data" to the south and west of the black boundary becomes the purple -575.

Capture.JPG


EDIT: Something from the P3D SDK's entry on Null Value just made sense to me:
"Sample value for each channel indicating that there is no data in the current pixel. For imagery sources use a comma-separated list: red,green,blue,[,land/water[,blend]]. For all other sources use a single value."

I was thinking that since my source data was an image, then "NullVallue=0,0,0" was the way to go. But once I caught the bit about land/water blends, they might be meaning imagery files.

I tried resampling with "NullValue=255,255,255" which gave me basically the same result, but with the occasional strip of pixels along the boundary where "0" becomes "no data" that appear to look like a thin wall of Legos over a kilometer high.
 
Last edited:

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,882
Country
netherlands
You would have to set the null value to -575 in this case. The elevation data has only one channel, so one value is enough.
 
Messages
496
Country
us-missouri
You would have to set the null value to -575 in this case. The elevation data has only one channel, so one value is enough.
That made my "0" ocean elevations also -575. Elevation data gets crazy on the last American pixel before the border: Wild swings from around +1000 to -1000 elevations. Still looking into this... I'm glad I flew close enough to the border to notice this. I didn't get close enough to Mexico to notice before, and I was just about to officially release the scenery.
 
Top