s2 Frame Generation Issues in Latest Build: Driver FG Crashes & In-Game FG Input Lag/UI Artifacts (RTX 40-Series)

I would like to report a critical regression regarding Frame Generation (FG) after the latest update. The newly introduced in-game Frame Generation is causing several severe performance issues, and it completely breaks compatibility with driver-level Frame Generation (which previously worked flawlessly).

Below are the detailed descriptions of the issues:

1. Driver-Level FG Causes Instant Crash on Launch

• Issue: Enabling driver-level Frame Generation now causes the game to crash immediately during the initial launch phase (fails to boot entirely, process terminates instantly).

• Notes: Previously, driver-level FG provided a much smoother experience. Now, even if the in-game FG is toggled OFF, having the driver-level FG active prevents the game from opening.

2. In-Game FG:  Input Lag & Alt-Tab Pacing Disaster

• Issue: The native in-game Frame Generation introduces noticeably higher perceptible input lag compared to standard rendering.

• The Alt-Tab Bug: More severely, whenever I Alt-Tab out of the game and switch back, it triggers a massive, severe input delay that lasts for a substantial period before recovering. Multiple community members have confirmed this exact behavior—the frame pacing and input response become completely desynced upon re-entering focus.

3. In-Game FG: UI Artifacts & Glitches

• Issue: Certain UI elements glitch out severely when in-game FG is enabled.

• Reproduction: This is most prominent on the map name display text right after matchmaking into a match. The text shimmers, distorts, and exhibits heavy motion artifacts, indicating that the FG's optical flow analysis is inaccurately processing 2D UI overlays.