Render-path comparison: no confirmed repair
Read-only evidence review, 17 September 2026. Forward alone and Forward with the HDRP managed native-render-pass flag disabled both reproduced NVIDIA TDRs. Do not promote either combination to a production default. The earlier short pass establishes bounded coverage on a different course, not stability of the Alps transition workload.
All three runs used the same Windows-ForwardCandidate-20260916 player, Unity 6000.3.24f1, build GUID 863b7c4dc60d4b53971aa9bc445b51e2, Assembly-CSharp SHA-256 F59282E74FDA8C1F2DD5B814C49B5D5718EA8D105D40AC43CFA4A48366F2E767: visible 1920x1080 D3D11, RTX 4060 Laptop GPU, High quality, threaded rendering, SRP Batcher enabled, isolation None, full scenery/effects, weather seed 707000.
| Run | Effective path | Coverage and outcome |
|---|---|---|
| 000929 | Forward; native flag on | Passed Blackpine continuous race: 137.700 race seconds, lap 1→2 at 71.653 seconds, finished, no driver events. |
| 001303 | Forward; native flag on | Failed after 63.846 seconds from launcher start, during Alps-03 safe-reset driving. NVIDIA TDR; 1/20 visits completed. |
| 001952 | Forward; native flag off | Failed after 328.403 seconds from launcher start, during the eleventh visit's Alps-02 countdown. NVIDIA TDR; 10/20 visits completed. Requested duration was 600 seconds. |
For 001952, the only rendering diagnostic flags were -rampageForwardRendering -rampageNoNativeRenderPasses; there was no direct-rendering, SRP-disable or minimal-effects flag. The player log confirms HDRP graph True → False. All 200 recorder samples have the Forward camera override; all 199 available effective observations are Forward, with exactly one HDRP graph and hdrpGraphNativeRenderPasses=false. The initial pre-render sample has unavailable camera mode and zero graphs. All 200 samples are finite, with zero captured Unity log errors.
The first nvlddmkm events 14/153 occurred at 00:25:20.853759 CEST (2026-09-16T22:25:20.853759Z), including UCodeReset TDR. Subsequent events record resetting, NV_UFLUSH_FB_FLUSH timeouts (0x2, 0x3), PF FLR recovery, and reset/restart at 00:25:29.308/29.326. Sample 199 is 17.042 ms after the first event: Alps-02, countdown, race time 0, gates 0/90, frame 10987, 10942 main-camera callbacks, last callback age 1.004 seconds; Rain intensity 0.228, effective Forward and graph flag false. No finish or lap transition is required for this failure.
The final sample at 00:25:31.435 has callback age 10.551 seconds. The QA report records Normal camera rendering stalled for ten seconds; loggedErrors=0 describes captured Unity messages and does not erase this caught QA exception. A clean-exit record follows at 00:25:31.472. Both the report and finalized invocation confirm production profiles unchanged and QA files restored; these cleanup successes do not make the rendering test pass.
Recorded adapter peaks: 2622/8188 MiB, 73°C, 72.39 W, 97% utilization. Last adapter sample: 2284 MiB, 70°C, 52.63 W. System memory retained at least 42.899 GiB available; peak commit 25.172 GiB, player private memory 2.509 GiB. Unity QA counters peaked at 80.637 MiB managed, 518.374 MiB allocated and 646.906 MiB reserved. These sampled counters show no capacity exhaustion; they cannot identify the failing GPU command or exclude an unobserved transient. Sources: GPU telemetry, system memory, QA report.
The longer time before failure is insufficient evidence of improvement from a single run. A Deferred-plus-native-off comparison has not been established by these three runs. CPU graph observations confirm the managed flag, not native backend render-pass execution.