r_forceAutoExposureMax

rend2

Needs review. The inventory/provenance evidence is recorded, but some behavior, options, or attribution still lacks a direct user-facing source.

Controls r_forceAutoExposureMax in the renderer module. Consult the cited behavior reads before relying on values not listed here.

At a glance

Field Value
Category Graphics & rendering
Feature family Auto exposure
Module renderer
Also registered in renderer
Renderer rd-rend2
Network scope client-only — Local to the client/UI/renderer.
Derivation code-trace
Confidence high
In-game xdocs No
In-game menu No
Default 1.0
Value type float
Restart No latch flag is registered.
Cheat protected Yes

Values

No discrete value list is enforced or documented in the inspected source.

Flags

Provenance

Origin: rend2

Dated project introductions

Authored dates come from the exact registration’s first content commit, PR dates identify when work was proposed to each project, and integration dates come from each first-parent mainline. A project merging first does not override earlier upstream authorship or submission.

Project Authored PR opened Integrated Commit Relationship
OpenJK 2013-10-08 2023-10-03 be28b4edd6c7 Shared integration commit
rend2 2013-10-08 2023-10-03 be28b4edd6c7 Ultimate origin
TaystJK 2023-10-03 2023-09-30 2023-10-03 86c0756385ef Other project appearance
jaPRO 2023-10-03 2023-10-03 86c0756385ef Other project appearance
NewJK / NewMod 2026-08-09 2026-08-09 686cbf9b649b Other project appearance

Later changes

These commits occur after the ultimate-origin introduction on TaystJK’s inherited first-parent lineage. Registration evidence is exact; behavior evidence requires a changed bound cvar reference or a changed registered command-handler hunk.

Date Change source Commit / subject Evidence Confidence
2025-04-15 rend2 c98ecf977bd3 · PR #217
Rend2 update (#217)
Changed registration, default, flags, module, renderer scope, handler, or gating. codemp/rd-rend2/tr_init.cpp medium

Evidence