Hi,
I'm trying to work out the best implementation for a terrain height map. I currently have a choice between "one big" height map or "one per tile quad". Advantages/Disadvantages as I see it are;
"One Big" => consistent height sampling irrespective of quad scale. Single state switch covering all terrain quads (assuming the Scale World matrix neccessary to map the individual quads UV sample coords doesn't in itself cause a state switch). Disadvantages; cannot increase height resolution for more detailed quads without introducing an extra "noise" heightmap. Limited world size based on max texture size for heightmap.
"One Per Tile Quad" => can scale height map based on tile resolution - more detailed heights for more detailed quads. Lots of state switching (at least one per tile rendered as they have a unique heightmap per tile). Inconsistent height sampling where detail levels change at skirts - neccessitates "welding" height values from the parent tile to the child quads at heighmap writing time to prevent ripping. World detail and size unlimited by texture sizes.
What approach is generally favoured for large landscapes ? I'm just trying to prevent going off down the wrong rabbit hole.
Thanks
Phillip
