diff options
| author | salmonik <salmonik@tuta.io> | 2026-11-04 21:35:44 +0100 |
|---|---|---|
| committer | salmonik <salmonik@tuta.io> | 2026-11-04 21:35:44 +0100 |
| commit | c35fc21f345ac9ecf9017115c4481a1147d05206 (patch) | |
| tree | 6907a027a097aec5af994b5bdcb20dddce6e984a /src/gui.cpp | |
| parent | Chams: make Fullbright a white-hot additive glow (diff) | |
| download | hl2h-c35fc21f345ac9ecf9017115c4481a1147d05206.tar.gz hl2h-c35fc21f345ac9ecf9017115c4481a1147d05206.zip | |
Chams: real additive material, addref cached materials
Testing on :99 showed ADDITIVE on debugtranslucentsinglecolor did nothing and
alpha lost the colour, because that VMT has no $translucent and the engine
bound an unreferenced material. Use debug/debugtranslucentmodelhulls (VMT has
$additive 1 + $color) for Additive/Fullbright, and addref every preloaded
material so the engine stops warning "bad reference count 0" and applies
$color/ColorModulate. Verified: Solid is flat blue, Additive is a translucent
coloured glow, Fullbright is a white additive glow, White is opaque white.
Also drop the viewmodel additive base (the solid material is opaque, so it
made an opaque blob) and never call FindMaterial inside DrawModelExecute.
Document that the alpha control is stored but has no effect until a custom
$translucent model VMT is added.
Diffstat (limited to 'src/gui.cpp')
0 files changed, 0 insertions, 0 deletions
