clarify what "largest memory usage" case of vheight is

This commit is contained in:
Sean Barrett 2015-04-11 01:13:46 -07:00
parent 3629a60ec3
commit 75f69ce5ed
1 changed files with 4 additions and 4 deletions

View File

@ -1019,10 +1019,10 @@ enum
//
// The four vertex heights can come from several places. The simplest
// encoding is to just use the 'vheight' parameter which stores four
// explicit vertex heights for every block. This allows total indepdence,
// but at the cost of the most memory usage. Encode this with
// STBVOX_MAKE_VHEIGHT(vh_sw, vh_se, vh_nw, vh_ne). These coordinates
// are absolute, not affected by block rotations.
// explicit vertex heights for every block. This allows total independence,
// but at the cost of the largest memory usage, 1 byte per 3D block.
// Encode this with STBVOX_MAKE_VHEIGHT(vh_sw, vh_se, vh_nw, vh_ne).
// These coordinates are absolute, not affected by block rotations.
//
// An alternative if you just want to encode some very specific block
// types, not all the possibilities--say you just want half-height slopes,