Your GPU Isn’t the Problem Anymore, Game Devs Are!

Key technological ideas & how they changed dev pressure

• Upscaling (DLSS/FSR/TSR) Early adoption of DLSS raised fears that developers would stop optimizing (or engines would “lean” on upscalers). As DLSS quality improved, people lessened pushback because upscaling artifacts became harder to notice—looking closer to native resolution.

• Frame generation (Frame Gen / Multi-Frame Gen) The “next step” is AI-interpolated frames inserted between real rendered frames to boost perceived FPS (e.g., “double” or more).

  • Main tradeoff: input latency increases, because mouse/keyboard inputs correspond to the real rendered frames, not the interpolated ones.

• Further scaling of Frame Gen Mentions progression from 2x to 3x/4x, and claims newer multi-frame gen modes can reach up to ~6x.

---

Main argument: “Lazy optimization” concern may be coming true again

• The speaker argues that while upscaling reduced visibility of performance compromises, frame generation can shift performance responsibility to the player.
• Concern: developers may design games expecting players to enable these features to reach playable rates, even if the game’s real render performance is poor.

---

Review / test focus: “Kraken Express” game performance breakdown (UE5 / Unreal Engine)

• The speaker reviews and benchmarks performance in an indie title described as a Minecraft + survival/world-building style game, using heavy, hands-on testing as evidence.

Clarifications / context from comments

• Claims the game is not part of Palworld (though Palworld helped distribute it).
• States the developer is Kraken Express, located in Uzbekistan.
• Mentions the speaker has ~116 hours total:
  • Most recent start: beginning of the month
  • Level: 13
  • XP sources: quests/discovery, not primarily combat or farming

What the speaker claims is causing poor performance

• Player-built areas are the main culprit, especially:
  • Piece-by-piece construction, which renders many individual parts/entities
  • Fire / torch / campfire-like effects that dramatically reduce FPS
  • Rendering inefficiencies such as blocks that have multiple sides rendered individually
• They contrast this with:
  • Pre-built town sections, compiled as fewer entities/assets (rendered as a single optimized entity), which performs better

Benchmark details (stated setup)

• GPU: RTX 5090 (the speaker calls it “best of the best”)
• Resolution/tech:
  • Testing in 4K using TSR at 100% scaling
  • Meaning: effectively native resolution, with no DLSS/FSR upscaling
• Performance impressions:
  • Around ~91 FPS in an open/overcast ocean view (high settings)
  • Turning around or approaching denser areas: ~68 FPS
  • Switching to 1440p: modest improvement to around ~102 FPS
  • Entering build interiors with torches/fire: drops sharply to high 50s FPS
  • Extreme pirate port case:
    • ~38 FPS at native 4K on high
    • Lowering to low gains only about +12–13 FPS (modest visual change)
  • Large, fire-heavy structures (tavern):
    • Remain around 30s–40s, even on lower settings

How upscaling/frame gen changes results (and the speaker’s interpretation)

• Switching from 4K native-ish to upscaled/rescaled increases FPS (example: ~30s to ~50s).
• Using DLSS Balanced still doesn’t restore strong performance (example: mid-50s).
• The “fix” the speaker criticizes is enabling Frame Gen:
  • With 2x frame generation, FPS reportedly rises dramatically (example: ~87 FPS)
  • But the speaker emphasizes the cost is input latency/jello/smoothing artifacts, and potentially worse behavior on lower-end GPUs.
• The speaker stresses that base render FPS still matters for responsiveness:
  • Even if frame gen looks smooth, latency is tied to the original real-rendered frames.

“It breaks on lower-end GPUs” (example includes RTX 4070)

• Demonstration on RTX 4070 FE:
  • At 1440p with DLSS Balanced, FPS drops to about ~29–30 FPS in dense areas
  • Changing settings to “quality/low/performance” moves FPS somewhat, but still remains non-playable for the dense town scenario
• Speaker’s argument about intended expectation:
  • DLSS + Frame Gen together to reach anything like playability

Reported multiplayer/instability claim

• Others report computer crashes when visiting the speaker’s city, implying extreme performance/VRAM/memory stress.

---

How this ties to the “your GPU isn’t the problem anymore” thesis

• The speaker’s conclusion: modern hardware plus AI features can mask performance issues, but:
  • Games may still be poorly optimized, especially for complex user-built geometry/effects
  • Frame Gen is a concession, not a true fix—because of latency and artifacts, especially problematic on lower-end GPUs
• They question whether some UE build workflows make certain player-build designs hard to optimize without pre-compilation/asset baking.

---

Requested future research / questions posed by the speaker

• Asks which other titles heavily rely on Frame Gen to become playable, especially other Unreal Engine games.
  • Mentions rumors like Resident Evil Requiem, but states uncertainty.

---

Main speakers/sources

• Primary speaker/tester: “Jay” (narrator of the subtitles; discusses their own benchmarks and gameplay hours)
• Developer/source mentioned: Kraken Express
• Game mentioned/context: an indie survival/world-building title showcased as using Unreal Engine 5 (UE5)
• Referenced tech vendors/terms: NVIDIA (DLSS/Reflex), AMD (FSR), Intel (TSR mentioned), NVIDIA drivers/tools indirectly