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

SplitGrid question

Messages
15
Country
southafrica
I am new here and have a question regarding the use of SplitGrid | AGN | * versus SplitGrid | 0.25 | *.

I am creating autogen for an area exactly 1x1 degree in size. Three spatial datasets are used. Street data from OSM, buildings from OSM and vegetation data sourced elsewhere. The three datasets have been clipped to the 1x1 degree area using QGIS. The street data is used to create light poles along residential roads using the example provided in the manual. The spatial data is used without applying any reprojection. The area for which autogen is generated is rural with a few small towns.

Using SplitGrid | AGN | * the result is as expected (except that most residential streets do not show lamp poles/lights - only some do - not clear why) and autogen vegetation, houses and light poles are placed/aligned correctly. Some 3298 autogen files are created. Except for the fact that most residential streets do not show light poles, I am satisfied with the result and want to repeat the script on some 15 more 1x1 degree areas.

To make the number of autogen files more manageable, I changed SplitGrid | AGN | * to SplitGrid | 0.25;0.25 | *. I should emphasise that this is the only change made to the configuration file. This reduces the number of autogen files to to a more manageable number - 11 (5 grid cells have no data).

Testing the result in FSX showed the following:
  1. Autogen vegetation does not show up where it is supposed to. There seems to be an offset of about 7 to 10 km.
  2. Houses are also offset by about 7 to 10 km and there are a lot of floating houses.
  3. Houses will appear and then suddenly disappear in the landscape.
  4. Light poles/lights are only showing up for one street in one of the town that falls in this area.
The script was initailly ran through the latest available stable version of scenProc. Subsequently it was also ran through the latest development release to see if that resoves the issue. Unfortuanletly it does not.

What am I missing/doing wrong?

Any assistance will be appreciated.
 
Hi,

You can't reduce the number of autogen files, as each AGN file covers exactly a LOD13 tile. That is the way the terrain engine has been designed. So when making AGN files you always need to use AGN as size in the SplitGrid step.
 
Arno, thank you for the reply and I will follow your advice.

I must admit I am a bit confused. What is the purpose then of some of the SplitGrid examples given on page 106 of the latest manual, for example SplitGrid | 0.2 | * ? Does this apply to scenery other than AGN?

Thank you for clarifying.
 
Hi,

When you make scenery BGL output instead of AGN or when you make cultivation for AF2 it can be useful to use a different grid size. But for AGN you should always use the AGN value.
 
Back
Top