arma3:tools:terrain-processor
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
arma3:tools:terrain-processor [2024/08/04 21:37] – text moved to ... snakeman | arma3:tools:terrain-processor [2024/08/04 21:50] (current) – text moved to ... snakeman | ||
---|---|---|---|
Line 48: | Line 48: | ||
====== Object Placement Statistics ====== | ====== Object Placement Statistics ====== | ||
- | This is nice reference read of how many objects some configs place and how long time it takes to import these to terrain | + | Text moved to [[arma3:terrain:terrain-processor:object-placement-statistics|ArmA 3 Terrain |
- | + | ||
- | Task: Area Random | + | |
- | + | ||
- | Trees 12, probability 100%, minimal distance 5m. | + | |
- | + | ||
- | **Polygon size about 20km x 20km**, just slightly below that size but otherwise square area. | + | |
- | + | ||
- | ^ Hectare Density ^ Objects Placed ^ | + | |
- | | 1 | 41,000 | | + | |
- | | 10 | 413,000 | | + | |
- | | 20 | 827,000 | | + | |
- | | 30 | 1,240,000 | | + | |
- | | 40 | 1,654,000 | | + | |
- | | 50 | 2,068,000 | | + | |
- | | 60 | 2,481,000 | | + | |
- | | 70 | 2,895,000 | | + | |
- | | 80 | 3,308,000 | | + | |
- | | 90 | 3,722,000 | | + | |
- | | 100 | 4,136,000 | | + | |
- | | 110 | 4,549,000 | | + | |
- | | 120 | 4,963,000 | | + | |
- | | 130 | 5,376,000 | | + | |
- | | 140 | 5,790,000 | | + | |
- | | 150 | 6,204,000 | | + | |
- | + | ||
- | Terrain | + | |
- | + | ||
- | **Polygon size about 40km x 40km**, everything else the same as above. | + | |
- | + | ||
- | ^ Hectare Density ^ Objects Placed ^ | + | |
- | | 1 | 167,000 | | + | |
- | | 10 | 1,674,000 | | + | |
- | | 20 | 3,348,000 | | + | |
- | | 30 | 5,023,000 | | + | |
- | | 40 | 6,697,000 | | + | |
- | | 45 | 7,535,000 | | + | |
- | + | ||
- | Terrain builder imports 7,5 million object LBT file in 37 minutes. | + | |
- | + | ||
- | **Polygon size about 81km x 81km**, everything else the same as above. | + | |
- | + | ||
- | ^ Hectare Density ^ Objects Placed ^ | + | |
- | | 1 | 670,000 | | + | |
- | | 5 | 2,681,000 | | + | |
- | | 9 | 6,033,000 | | + | |
- | | 10 | 6,704,000 | | + | |
- | + | ||
- | Terrain builder imports 6,7 million object LBT file in 32 minutes. | + | |
====== Multiple Tasks ====== | ====== Multiple Tasks ====== | ||
- | **2019-12-25** | + | Text moved to [[arma3: |
- | + | ||
- | HOWTO place trees, bushes and rocks with different " | + | |
- | + | ||
- | TPP files don't have to have single task with everything spammed into one set, for example you can have task for trees at 85 density and then you have task for bushes for 30 density and finally task for rocks at 10 density, all these in the one TPP file which also checks road cleaning etc. | + | |
- | + | ||
- | It might be easier to get bushes and rocks right if they are probability 100 and the density controls how dense they are placed. | + | |
- | + | ||
- | Every different object type you put into single task limits the tasks flexibility. | + | |
- | + | ||
- | No matter how many tasks you have in one TPP, only one LBT file is exported / saved. | + | |
- | + | ||
- | One example is to first place trees, then bushes, then rocks and last run a road and other shape cleanup | + | |
arma3/tools/terrain-processor.1722807466.txt.gz · Last modified: 2024/08/04 21:37 by snakeman