Graphical glitches after editing the map

[Vercingetorix]

The map_heights.hgt is simply the heights of all the vertices. My understanding is the map is made up of tiles (I haven't really looked much into it but that's how most maps are). The dimension of the map is 255x156. Each tile subdivided you get 511x313 vertices. Hence the size of the map_heights.tga; 1 pixel per vertex. The hgt file takes all the info in desc_terrain and the map_heights.tga and turns it into an easy binary format. If however the hgt file is not needed I would guess it's just used for quicker loading purposes, and creating one would be unnessercery.

[tailkickusmaximus]

Heights is for the campaign maps
roughness is the visual representation of heights for the battlemaps

Do a test to see, level off roughness and shrink the distance between min and max in the descr_terrain.txt to something like between -1k to 1k.

Load up the map and you'll see that the campaign, now battle in an area that would have hilly or mountains in the campaign map and when the battle loads, you'll notice it's mostly flat.

You roughness should closely match your heights file, and each one is neede otherwise you can get CTDs and hangs when coming out of battlemodes.

This honestly does not rear it's head in the given campaign map, but really comes to light when creating a map from scratch.

The current 80 by 80 map I have works like a champ 100% of the time now once I realized that.