====== ArmA 3 Terrain Builder ======

[[https://www.pmctactical.org/forum/viewforum.php?f=68|ArmA 3 Forum]], [[:arma3|ArmA 3]], [[arma3:config|ArmA 3 Config]], [[arma3:missions|ArmA 3 Missions]], [[arma3:modeling|ArmA 3 3D Modeling]], [[arma3:scripting|ArmA 3 Scripting]], [[arma3:terrain|ArmA 3 Terrain]], [[arma3:texturing|ArmA 3 Texturing]], [[arma3:tools|ArmA 3 Tools]]

[[arma3:terrain:terrain-builder|ArmA 3 Terrain Builder]], [[https://www.pmctactical.org/forum/viewtopic.php?f=70&t=23005|ArmA 3 Terrain Builder Support Forum]]


====== Heightmap Roughness ======

If your heightmap is extremely rough with huge elevation changes / mountains in short distances etc, then buldozer and binarize most likely will just freeze.

Buldozer will freeze or spend endless time on "**Extruding hills and valleys**" part and binarize just freezes on 25% CPU usage.

Do not create too crazy elevations, such terrains might look nice in some 3d preview like in [[:tools:l3dt|L3DT]] 3D mode etc, but they aren't usable in ArmA 3. The rough elevations might not look odd on terrain builder scene view heightmap shown, so to our experience there is no way to clearly tell from the heightmap 2D, you just have to learn that by experience and obviously if you see very rough mountains in like L3DT 3D view that is a sign.

If you suspect your buldozer / binarize freezing or endless processing is caused by this, make a temporary very **very** bland and smooth heightmap just to test it out.

**Binarize WRP Freeze Detection**

How binarize freeze can be detected from windows task manager:
  - At start it runs 25% CPU usage and memory usage increasing
  - Within about 30sec CPU usage drops and goes back up again with memory usage increasing

If this doesn't happen, it just stays 25% with constant memory; it has frozen.