Remove gamma slider; keep HDR brightness

Wayland/XWayland discards window gamma ramps, so mat_monitorgamma could not
work on the development setup. Drop the slider, config key and readback.
Keep the in-engine HDR tonemap brightness and document that Fullbright turns
tonemapping off.

1 files changed, 10 insertions, 12 deletions

diff --git a/CONTEXT.md b/CONTEXT.md
index e0af84a..5c91b5c 100644
--- a/CONTEXT.md
+++ b/CONTEXT.md
@@ -21,7 +21,7 @@ covers ESP, aimbot, triggerbot and silent aim.
   - `HL2H_NO_SERVER=1` — disable server-side health reads.
 - Config: `$XDG_CONFIG_HOME/hl2hake/config`, falling back to
   `~/.config/hl2hake/config`. Plain INI, saved on every change. New sections:
-  `[view]` (camera FOV, viewmodel FOV, gamma x10) and `[movement]`
+  `[view]` (camera FOV, viewmodel FOV, HDR brightness) and `[movement]`
   (crouch-jump, edge jump).
 
 ## Runtime architecture
@@ -237,19 +237,17 @@ vocabulary / decisions.
   client netvar every tick. The camera slider is 40..140 (stock 75) and the
   viewmodel slider 20..120 (stock 54); 0 is not allowed (old configs with 0
   migrate to the stock value).
-- `viewmodel_fov` and `mat_monitorgamma` are client cvars; applied through
-  `ClientCmd` when their slider changes. Gamma is stored as x10
-  (`[view] gamma=22` = 2.2) and the slider stops at 26 because the engine
-  clamps `mat_monitorgamma` at 2.6. The value is read back through
-  `ICvar::FindVar` on the next tick (ClientCmd is queued) and logged. The
-  engine does apply the ramp (`SDL_SetWindowGammaRamp` was called with
-  changing midpoints), but a Wayland/XWayland compositor discards it, so on
-  this setup the slider has no visible effect.
+- `viewmodel_fov` is a client cvar, applied through `ClientCmd` when its
+  slider changes.
 - `HDR brightness` (`[view] tonemap`, x10, 0 = automatic) sets
   `mat_force_tonemap_scale`. This is in-engine tonemapping for HDR maps and
-  does not depend on the window system applying a gamma ramp; 10 = 1.0.
-  Both live in the always-on `Camera / display` card
-  (`[view] fov/vmfov/gamma/tonemap`).
+  does not depend on the window system; 10 = 1.0. It has no visible effect
+  while Fullbright is on (fullbright bypasses tonemapping).
+- `mat_monitorgamma` was tried and removed: the engine applies the ramp (SDL
+  receives changing midpoints), but Wayland/XWayland compositors discard
+  window gamma ramps, so the slider did nothing on the development setup.
+- Both controls live in the always-on `Camera / display` card
+  (`[view] fov/vmfov/tonemap`).
 
 ## Map transitions