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

EcoRegions

This is all wonderful. and great progress... I can't wait to see the results. Unfortunately I have no knowledge about how you do this and therefore I cannot be helpful in that area.
 

rhumbaflappy

Administrator
Staff member
Resource contributor
Problems concerning EcoRegions and Biomes:

Asobo should allow the extension of types for EcoRegions. Right now these are hard-coded types.

Asobo should allow Biomes to be local to the package. The Simple_Biome example shows the problem. Assigning the EcoRegion (Alps) to the biomes changes that assignment worldwide, so you get huge cacti instead of conifers everywhere that EcoRegion is used.
 
Problems concerning EcoRegions and Biomes:

Asobo should allow the extension of types for EcoRegions. Right now these are hard-coded types.

Asobo should allow Biomes to be local to the package. The Simple_Biome example shows the problem. Assigning the EcoRegion (Alps) to the biomes changes that assignment worldwide, so you get huge cacti instead of conifers everywhere that EcoRegion is used.
Are you trying to assign the EcoRegion (Alps) to the biomes in the xml file 10-asobo_biomes.xml ?
 

rhumbaflappy

Administrator
Staff member
Resource contributor
No. Any changes made to the biome files will change the sim world-wide. Whether it is 10-asobo_biomes.xml, or 30-mycompany-biomes.xml, or anything else, the assigned EcoRegions are altered worldwide.
 

rhumbaflappy

Administrator
Staff member
Resource contributor
The packages should be placed in the Community folder like any other package. The EcoRegion polys will use the default biomes, unless the biome package is added. The polys just re-arrange the default ecoregions to conform to the placement of the EcoRegion_2017 locations.

That said, I think each EcoRegion should probably have it's own specific biome... but I think there are there are 843 regions.
 

Kelvin Richardson

Resource contributor
Problems concerning EcoRegions and Biomes:

Asobo should allow the extension of types for EcoRegions. Right now these are hard-coded types.

Asobo should allow Biomes to be local to the package. The Simple_Biome example shows the problem. Assigning the EcoRegion (Alps) to the biomes changes that assignment worldwide, so you get huge cacti instead of conifers everywhere that EcoRegion is used.

I am interested in the work you are doing and I also agree that the types should be extended, maybe you could offer your findings to Asobo?
 
Top