• 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.

All Forest Polygons are not created equal.

Mac

Messages
92
Country
ca-britishcolumbia
Finally got that damn tan/brown off the airport. Took me 5 hours to track down the problem.:mad::banghead:

It was something I never expected.:confused:

The LandClassPoly_Evergreen_Tree_Crop tag was the culpert. Also LandClassPoly_Deciduous_Tree_Crop would cause the same problem.

This really seemed strange to me as both of these couldn't be greener:rolleyes: .

I had the former tag in both EZ-Landclass and in a FSX KLM polygon close to the airport. I had to remove and replace both of those tags before the airport changed back to green.

Is there someplace to look up all the tags to see if they are wet or dry?

That damn airport is more trouble than it is worth, considering it hasn't even been there for 14 years. You would think the MS team would trigger to that after all this time.:censored:
 
Is there someplace to look up all the tags to see if they are wet or dry?

Not that I know of. Trial-and-error is the only foolproof method.

Like I said you could always get rid of the background polygon entirely, and instead just flatten everything and clear all of the autogen off.

Then it's a non-issue whether it's tan or green. Some people don't like this though because the ground textures are not designed to be viewed up-close. That's probably 99% of the reason why MS chooses to use the grass texture for the airport backgrounds.

And also keep in mind that some of the LC types produce airport backgrounds that are green in the spring and summer, and brown in the autumn and winter. Actually this is caused by the season bgl file that governs the area.
 
Not that I know of. Trial-and-error is the only foolproof method.

Like I said you could always get rid of the background polygon entirely, and instead just flatten everything and clear all of the autogen off.

Somewhat confused about getting rid of background polygon, as it didn't seem to do anything.

I will have to try the tag Airport_Backgrounds_Flatten_ExcludeAutogen using FSX_KML at an airport away from the current project and see if I get some differences.

As the tag, Airport_Backgrounds_Flatten_ExcludeAutogen, excludes autogen, I assume that terrain polygons, buildings and trees are all autogen. I thought it was just buildings and trees that were autogen.
 
Somewhat confused about getting rid of background polygon, as it didn't seem to do anything.

In GoogleEarth, draw a polygon over the approx boundaries of the stock scenery's airport background.

Tag it with Exclude_Airport_Backgrounds_Flatten_MaskClassMap_ExcludeAutogen.

This will kill off the stock aircraft background polygon.

If you are not sure what the boundaries of the stock polygon are, load the cvxxxxx.bgl file into TMFViewer to see.

After excluding the stock airport background, you will be left with stock runways, taxiways, scenery objects, etc.

I will have to try the tag Airport_Backgrounds_Flatten_ExcludeAutogen using FSX_KML at an airport away from the current project and see if I get some differences.

As the tag, Airport_Backgrounds_Flatten_ExcludeAutogen, excludes autogen, I assume that terrain polygons, buildings and trees are all autogen. I thought it was just buildings and trees that were autogen.

Airport_Backgrounds_Flatten_ExcludeAutogen essentially chops down all the trees and demolishes all of the buildings that are autogen.

Terrain polygons are not autogen and the above tag won't do anything to them.

You must use Exclude_Airport_Backgrounds_MaskClassMap_Flatten_ExcludeAutogen to remove stock airport background polys.

Not all trees and not all buildings are autogen. It seems the "park" type of landclass polygon has trees attached (limited testing only) and of course there are some buildings that are not autogen either.
 
Thanks for the explanation.
I am slowly learning. Hopefully I'll stop running into these snags.
Thanks again.
 
Is there someplace to look up all the tags to see if they are wet or dry?

I searched the web but doesn't seem to be any thumbnails of FSX textures. Surely though someone has done it, maybe AVSIM library?

On a related note I did find a web site that has thumbnails of all FSX scenery objects (ie the SceneryObject_LibraryObject tags in fsx kml)

http://lc0277.nerim.net/sceneobjects/
 
Good finds fellows.:D

If I live long enough I might start to get the hang of this, at least enough not to be asking so many stupid questions.:scratchch

My problem is I have a really hard time with manuals. Seems I have to learn hands on, which can be very frustrating.:(
 
90% of this I have no understanding of. But I can understand loading his test scenery and flying or slewing over the land class samples that he's laid out.

I just use the Excel spreadsheet because it has links to screenshots of all the landclass types. Its very handy and doesnt take a lot of time to load or anything.
 
Back
Top