AllocBlock:Full: Difference between revisions
Jump to navigation
Jump to search
(copyedit) |
SirYodaJedi (talk | contribs) |
||
| (12 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{gldsrc topicon}} | |||
{{update| | |||
* AllocBlock is the allocation of lightmaps (64 in first-party titles, 512 in {{sven}}). | |||
* AllocBlock errors are purely related to [[lightmap]] atlas generation. Lightmaps are always 16 [[luxel]]s per [[texel]], so the easiest way to use up AllocBlock is to have a lot of brushes with dense texture scales. | |||
* '''''AllocBlock is why {{gldsrc|4.1}} mappers use 1.0 texture scale by default.''''' | |||
}} | |||
==Description== | ==Description== | ||
While compiling or attempting to play it, your map has | While compiling or attempting to play it, your map has exceeded the maximum lightmap size. | ||
== | ==Solution== | ||
Reduce resolution and scale of used textures. Consider using [[Detail textures (GoldSrc)|Detail textures]] to increase the perceived quality of WAD textures, instead of using high-res WAD textures. | |||
: {{Important|Users whose GPUs have blocked the {{code|GL_ARB_multitexture}} extension (such as for {{pcgw|Half-Life#OpenGL_overbright_lighting|enabling overbright lighting}}) will not see detail textures.}} | |||
* | Additional optimization options include: | ||
* Use [[tool textures (GoldSrc)|NULL]] whenever a brush entity's face is completely obscured by a world brush or another entity. | |||
* | * After compiling CSG, BSP and VIS, use {{newbspguy|2}} to add the {{code|TEX_SPECIAL}} flag to faces which should be unlit (fullbright), then recompile RAD from within NewBSPGuy. | ||
* | * For brush entities which should be unlit, use [[VHLT]]'s {{code|zhlt_striprad}} KV to strip lightmaps from the entity after RAD is compiled. | ||
* Avoid rotating textures, as this also rotates the lightmap, causing more lightmap usage. | |||
== | == External links == | ||
* | * {{twhl|AllocBlock}} | ||
[[Category:Compile | [[Category:Compile errors]] | ||
Latest revision as of 19:12, 4 April 2025
This article or section needs to be updated to include current information regarding the subject because:
Remember to check for any notes left by the tagger at this article's talk page.
- AllocBlock is the allocation of lightmaps (64 in first-party titles, 512 in
). - AllocBlock errors are purely related to lightmap atlas generation. Lightmaps are always 16 luxels per texel, so the easiest way to use up AllocBlock is to have a lot of brushes with dense texture scales.
- AllocBlock is why
GoldSrc mappers use 1.0 texture scale by default.
Description
While compiling or attempting to play it, your map has exceeded the maximum lightmap size.
Solution
Reduce resolution and scale of used textures. Consider using Detail textures to increase the perceived quality of WAD textures, instead of using high-res WAD textures.
Important:Users whose GPUs have blocked the GL_ARB_multitexture extension (such as for 
enabling overbright lighting) will not see detail textures.
Additional optimization options include:
- Use NULL whenever a brush entity's face is completely obscured by a world brush or another entity.
- After compiling CSG, BSP and VIS, use newbspguy to add the TEX_SPECIAL flag to faces which should be unlit (fullbright), then recompile RAD from within NewBSPGuy.
- For brush entities which should be unlit, use VHLT's zhlt_striprad KV to strip lightmaps from the entity after RAD is compiled.
- Avoid rotating textures, as this also rotates the lightmap, causing more lightmap usage.
