yyc12345/stb
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

clarify what "largest memory usage" case of vheight is

Browse Source
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
stb_voxel_render.h
View File

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