"Ada improved"
Please visit the PCGH community thread first:
👉 https://extreme.pcgameshardware.de/forums/nv-uv.3601/
Incremental update on top of v0.93 Cantor. Three behavioral bug fixes plus the first round of actual hardware verification for the Ada write path. Ada support remains flagged as experimental. "Improved" refers to the write path and the UI, not to blanket verification across all 40-series chips.
Supported hardware: RTX 50 series (5070, 5070 Ti, 5080, 5090, 5060 Ti), plus experimental support for RTX 40 series (Ada). AD104 (4070 / 4070 Super / 4070 Ti) has now been verified in hardware. AD102 (4090) and AD103 (4080 / 4080 Super / 4070 Ti Super) remain unverified and depend on tester feedback.
⚠ Before you install
If you are upgrading from v0.93, your existing Afterburner profiles, slot layout and settings are unaffected. v0.94 is an in-place drop-in.
On the first start the existing nv-uv_game_replay_adjustments.json is detected as the old schema and cleared once (log: "Old adjustment format detected, discarded"). This is expected, not an error. Crash histories rebuild per profile from the next run onward, no manual action needed.
Same precautions as v0.93 still apply: remove per-slot locks on AB profiles before the first apply, and disable "Start with Windows" in Afterburner during UV experimentation so a boot-time UV crash doesn't re-apply automatically.
📚 Docs updated for v0.94
Guides (DE + EN) live at https://christianp403-spec.github.io/nv-uv-docs/ and have been updated with the new sections.
🚀 What's new in v0.94
Ada write path verified (AD104)
The native Ada curve encoder has been verified on a KFA2 RTX 4070 Ti (AD104) across multiple testing sessions. Apply, Scanner, Game Replay and UV-Pilot all run end-to-end on AD104 now. Preset values (frequency and voltage) are still community-sourced for all Ada chips and depend on per-card binning, so the experimental tag stays. AD102 and AD103 testers especially welcome: send me your AB .cfg and nv-uv.log via the PCGH subforum or Discord and I'll use them to move your chip variant to verified.
Game Replay: per-profile crash history
Previously, Game Replay stored its downstep history per game only. That caused a subtle bug. If the Performance preset crashed twice on a specific game and you later added a Custom profile for the same game, UV-Pilot would load your Custom profile and silently layer the old Performance downstep on top of it. So the Custom frequency was lowered by roughly 50 MHz even though it had nothing to do with the earlier crashes. Starting with v0.94, crash history is tracked per (game, profile) pair. Every preset (Eco / Balanced / Performance / Max) and every user-defined Custom profile has its own independent history. Manual applies without UV-Pilot context don't persist: a live downstep still happens on a crash, but nothing is written to JSON, since there's no profile identifier to match on the next session.
UV-Pilot: foreground window takes priority
Reported by a user: with Chrome open in the background and a supported game launched, UV-Pilot stayed locked on the Chrome-Eco profile until Chrome was fully closed, even while the game window was in focus. Cause was in the scan path: it iterated over an unordered process set, locked on the first match, and then skipped further detection. Any second game starting afterwards never got picked up.
v0.94 prioritizes the process owning the foreground window. It switches cleanly in both directions: game focused turns into Performance, Alt-Tab to Chrome turns into Eco, Alt-Tab back to Performance. If the foreground process is not a known game in the DB (Explorer, DWM, etc.), the current lock is retained, so alt-tabbing to the desktop never kills a gaming lock.
Ada UI: Blackwell-only controls hidden
On Ada cards the three checkboxes Boost Override, V-Step Fix and Idle Optimization are now hidden in both the main and Mini view. All three are Blackwell-specific compensations (XOC-card boost tier, point-before-flatten fix, fantasy-frequency encoding) and have no behavioral effect on the Ada write path. Showing them on Ada was creating confusion.