New Blood CEO slams Nvidia DLSS 5: “Who asked for this?”

Nvidia unveiled DLSS 5 at its GTC event, slated for release this fall on RTX 50-series GPUs; indie developers including New Blood CEO David Oshry and Dusk creator David Szymanski publicly criticized it as generative‑AI overreach and urged boycotts. The backlash highlights concerns DLSS 5 could erode game clarity and become effectively 'non‑optional,' creating reputational risk and potential adoption friction for Nvidia among developers and some consumers, but no immediate financial impact or quantified market effects were reported.

Analysis

Developer outrage at an alleged overreach of Nvidia’s DLSS 5 is a reputational flicker with asymmetric downstream effects: social-driven pushback can slow adoption in indie/AA ecosystems that punch above their weight in influencing player sentiment, even while AAA and cloud partners continue to roll forward. The key mechanism is “soft mandatory” feature creep — as engines and studios architect around an upscale/generative path, opting out becomes progressively more costly, creating platform lock-in rather than pure consumer choice.

Second-order winners would be competitors and vendors that can credibly sell native performance or simpler, explainable upscaling (AMD, Intel marketing teams, and OEMs pitching higher-clock hardware at the same price point); losers are small studios and middleware players forced to choose between degraded UX or extra dev cycles. Memory and fab-level demand is unlikely to move materially from a software controversy, but GPU upgrade cadence could elongate if consumers push back and OEMs delay premium-priced refreshes.

Risk calendarization: expect headline-driven volatility over days surrounding product launch and GTC follow-ups, a medium-term (3–12 month) test when engines decide to integrate or block the SDK, and a long-tailed (12–36 month) regulatory/IP risk if generative-image provenance issues surface. Reversal paths include major AAA publishers and Unreal/Unity endorsing DLSS 5 quickly (rapid adoption), or AMD/Intel shipping a clearer, open alternative that removes the “forced” tradeoff between clarity and performance.

Actionable monitoring: quantify developer sentiment (public pledge counts, engine plugin downloads, GitHub + Discord chatter), track SDK integration in top 20 engines/publishers within 6 months, and watch OEM pricing on next-gen SKUs — a sustained >5% price cut from OEMs to sell native performance would be a clear market signal that Oshry’s preferred outcome is happening.

Key Decisions for Investors

• Tactical core position — NVDA (6–12 month): Maintain a constructive core exposure to NVDA given structural ML/data-center moat, but size the position with event protection: overweight but hedge with a 60–90 day put spread (sell 1 nearer-OTM put / buy 1 further-OTM put) sized to cap first-order PR drawdowns to ~2–4% of portfolio. Rationale: long-term upside retained while short-term social/launch risk is contained.
• Event-driven volatility play — NVDA (30–90 day): Buy short-dated put spreads around the DLSS 5 consumer launch windows or next earnings (cheap directional tail hedge). Risk/reward: pay small debit for limited downside protection against a headline-driven 8–15% drawdown; profit if sentiment-driven repricing occurs.
• Relative-value pair — Long AMD / Short NVDA (3–12 month, equal notional): Small-sized pair (2–4% net delta) to express a re-rating if developers and OEMs lean back toward native performance or open alternatives. Stop-loss if NVDA outperforms by >12% over 2 months; target 1.5–2x upside on AMD leg if adoption narrative shifts.
• Convexity in alternatives — Long Unity (U) or engine-integrator exposure (6–12 month): Small long position in engine/platform vendors that can gate or delay DLSS 5 integrations (monitor plugin adoption); these names benefit if multi-studio pushback stalls Nvidia’s software-led path. Use 3–6 month call spreads if implied vol is reasonable to get convex upside with capped cost.