A modder-built tool is doing something CD Projekt Red and Nvidia haven’t officially shipped: running DLSS 5 inside The Witcher 3: Wild Hunt — Remastered. The result, according to testing reported by Wccftech, is a sharper, more detailed Geralt of Rivia, along with a frame rate hit that runs as high as 30% on Nvidia’s flagship GPU.
There is no official DLSS 5 support in the Remastered edition of the 2015 role-playing game. What’s circulating instead is an injection method built around ShortFuse’s DLSS 5 Tool, a community utility that forces Nvidia’s newest neural rendering pipeline into games that were never built for it. The trade CD Projekt Red never signed off on: noticeably better faces, paid for in frames.
What DLSS 5 Actually Changes: 3D-Guided Neural Rendering
DLSS 5 is not simply the next number after DLSS 4. Where earlier versions of Nvidia’s upscaling stack focused on reconstructing resolution and generating extra frames, DLSS 5 is described as 3D-Guided Neural Rendering, a technique that feeds the AI model geometric and material data from the game engine itself, rather than just pixels on screen. Nvidia’s own DLSS technology page lays out that generational shift from resolution upscaling toward full neural rendering. That distinction matters for why a 2015 game retrofitted with the tech behaves differently than a native DLSS 5 title would.
In practice, that means the renderer isn’t just guessing what a face should look like from flat image data. It’s working with the underlying 3D information the game engine already tracks, then using a neural network to fill in surface detail, lighting response, and material texture that the original 2015 character models never had budget for. It’s a heavier computational ask than prior DLSS generations, which is part of why the performance conversation around this mod looks different from a typical upscaler comparison like DLSS vs FSR.
Inside ShortFuse’s DLSS 5 Tool: How the Injection Works
ShortFuse’s DLSS 5 Tool sits in a growing category of injector utilities that hook into a game’s rendering pipeline and swap in Nvidia’s neural components without developer involvement. It’s the same general approach that’s let modders bring DLSS 5 to other unsupported titles over the past several weeks, following a pattern this site has tracked since DLSS 5 files first began leaking out of early builds this fall. Shattered.io covered an earlier wave of that activity when DLSS 5 mods reached RTX 20 through RTX 40-series cards, well outside Nvidia’s intended Blackwell-only rollout.
The Witcher 3 case is notable because it targets a specific, well-known character model rather than a generic scene. Geralt has been rendered, re-rendered, and picked apart by players since the original 2015 launch, and the Remastered edition already drew scrutiny for how much (or how little) its character models had actually changed. Injecting neural rendering onto that face is the kind of before-and-after comparison that spreads fast on its own.
The Geralt Facelift: What Players Are Actually Seeing
According to the report, the injected renderer adds visible surface detail to Geralt’s face, along with broader improvements to skin texture, hair, and how materials catch local light. It’s the kind of change that reads clearly in side-by-side screenshots even to players who don’t normally track rendering tech. That’s precisely why it’s spreading through PC gaming circles faster than most DLSS mod stories, which tend to stay contained to enthusiast hardware forums.
None of this is officially sanctioned. There’s no patch note from CD Projekt Red mentioning DLSS 5, and Nvidia hasn’t listed The Witcher 3 Remastered among any confirmed DLSS 5 partner titles. Every visual improvement being reported is a side effect of a third-party tool overriding the game’s rendering path, not a feature CD Projekt Red built or tested.
The Performance Cost: 26-30% Lost With Path Tracing On
The upgrade isn’t free. With path tracing enabled, Wccftech’s testing put the performance cost at roughly 26% to 30% on a GeForce RTX 5090, Nvidia’s current flagship consumer GPU and one of the few cards with enough headroom to run path-traced Witcher 3 at a playable frame rate in the first place. On a card that already costs thousands of dollars and still struggles to hold high frame rates with path tracing maxed out, losing nearly a third of performance is a real trade-off, not a rounding error.
The scale of that hit puts it in context against other GPU pricing pressure this year. Shattered.io reported the RTX 5090 vanishing from US retail shelves entirely, with resale prices climbing past $9,500 as AI compute demand competes with gamers for the same silicon. Losing 30% of a $9,500 card’s frame rate to a face upgrade is a very different calculation than losing 30% on a $500 GPU.
Frame Time Breakdown: 20ms vs 28.6ms on the RTX 5090
The clearest picture comes from a specific test run cited in the report. With DLSS 5 injection off, the RTX 5090 held 50 FPS at a 20.0 millisecond frame time. Switching DLSS 5 on dropped that to 35 FPS, with frame time climbing to 28.6 milliseconds, a roughly 30% performance hit in that particular scene and settings combination. Frame time is the more honest metric here: it’s the actual rendering budget consumed per frame, and an 8.6 millisecond jump is substantial when the entire frame budget at 60 FPS is only 16.6 milliseconds.
| Test Configuration | Frame Rate | Frame Time | Performance Change |
|---|---|---|---|
| DLSS 5 injection off (path tracing, RTX 5090) | 50 FPS | 20.0 ms | Baseline |
| DLSS 5 injection on (path tracing, RTX 5090) | 35 FPS | 28.6 ms | ~30% lower |
| Neural Rendering cost, full 4K (Lecram’s mod estimate) | N/A | +8.7 ms | Added render overhead |
| Neural Rendering cost, half resolution | N/A | Reduced by 3.2 ms vs. full 4K | Lower image quality trade-off |
| Reported range across tested scenes | N/A | N/A | 26% to 30% lower |
That last row matters as a caveat: the 26-30% figure is a reported range across the specific scenes and settings Wccftech tested, on one specific card. It is not a universal number that will hold across every GPU, resolution, and area of the game, and neither CD Projekt Red nor Nvidia has published an official benchmark to compare it against.
The HDR Problem: Toned-Down Highlights and Color Shift
Performance isn’t the only trade-off. The report notes that the injected renderer can tone down highlights and introduce a slight color shift, an issue that becomes more noticeable on an HDR display. That’s a meaningful catch for anyone running a modern HDR monitor or TV, where the whole point of the higher dynamic range is to preserve punchy highlights and accurate color reproduction. A neural rendering pass tuned primarily for standard dynamic range output can visibly undercut what an HDR panel is supposed to deliver.
This is a common growing pain for injector-based mods generally: they’re built against whatever pipeline the modder can reverse-engineer, not the full range of display configurations Nvidia would test in an official release. Bugs like a color shift on HDR panels tend to get identified and patched over time in actively maintained community tools, but there’s no guarantee of a fix timeline the way there would be with a Nvidia-backed driver update.
Lecram’s Mod and the 8.7ms Neural Rendering Tax at 4K
A separate implementation, built by a modder known as Lecram, offers a more granular look at where the performance cost actually comes from. That mod’s estimate puts Neural Rendering’s overhead at approximately 8.7 milliseconds when running at full 4K resolution. Put another way: nearly a full extra frame’s worth of render time (at 120 FPS, one frame is 8.3 milliseconds) gets consumed just running the neural rendering pass itself, before accounting for everything else the game already needs to render.
That figure lines up reasonably well with the 20.0ms-to-28.6ms jump reported in the path-traced RTX 5090 test, an 8.6 millisecond increase. Two different testers, two different measurement approaches, landing on a similar overhead number is a useful cross-check, even though neither figure should be treated as a fixed constant across every hardware and settings combination.
Cutting Resolution to Claw Back Frame Time
Lecram’s testing also found a workaround, of sorts. Halving the Neural Rendering resolution reportedly reduced rendering time by 3.2 milliseconds, at the cost of reduced image quality. That’s roughly a third of the total neural rendering overhead clawed back, in exchange for a visibly softer version of the facial and material detail the whole mod exists to add.
It’s the same resolution-versus-quality trade-off PC gamers already navigate constantly with upscaling settings, ray tracing presets, and shadow resolution sliders. What’s different here is that there’s no in-game menu for it. Anyone wanting the lower-overhead version has to configure it manually through the injector tool itself, which puts this squarely in enthusiast-only territory for now rather than something a mainstream player would casually toggle.
Official Update vs Unofficial Mod: What Sept. 29 Actually Shipped
The timing here is easy to conflate but worth separating clearly. CD Projekt Red’s own Remastered update, which Shattered.io covered when The Witcher 3 Remastered hit Switch 2 on September 29, brought official path tracing, DLSS 4.5 Ray Reconstruction, and Dynamic Multi Frame Generation to the PC version, with Nvidia claiming multi frame generation gains up to 6x on RTX 50-series cards in ideal conditions. None of that official update includes DLSS 5.
The DLSS 5 injection story is a separate, unofficial track running in parallel, built by modders using tools like ShortFuse’s DLSS 5 Tool on top of whatever the official update already shipped. The two are easy to mix up because they landed around the same week and touch the same game, but one is a supported, tested feature from CD Projekt Red and Nvidia, and the other is a community hack with no warranty and no official benchmark to verify it against.
| Feature | Official Sept. 29 Update | Unofficial DLSS 5 Injection |
|---|---|---|
| Backed by | CD Projekt Red, Nvidia | Community tool (ShortFuse’s DLSS 5 Tool) |
| Core technology | DLSS 4.5 Ray Reconstruction, Dynamic Multi Frame Generation | DLSS 5 3D-Guided Neural Rendering |
| Nvidia’s claimed RTX 5090 4K result | Up to 385 FPS (Ultra+ path traced, per Nvidia’s marketing figures) | 35 FPS with path tracing plus neural rendering (independent test) |
| Known display issues | None reported | HDR highlight and color shift reported |
| Support status | Official, patched by developer | Unofficial, unsupported, install at own risk |
Note that Nvidia’s 385 FPS figure and the independent 35 FPS path-traced result in that table are not measuring the same thing. Nvidia’s number reflects its own official Dynamic Multi Frame Generation pipeline under marketing-optimized conditions; the 35 FPS figure reflects a specific test scene with path tracing plus the unofficial neural rendering injection running on top. They shouldn’t be read as a direct one-to-one comparison, just as two very different performance stories playing out on the same card in the same week.
Why Nvidia and CD Projekt Red Haven’t Touched This
Neither Nvidia nor CD Projekt Red has commented on the DLSS 5 injection specifically. That silence is fairly typical for early-stage mod activity built around leaked or pre-release technology: companies tend to stay quiet until a tool either becomes disruptive enough to require a statement, or a security or stability issue forces their hand. Notebookcheck has reported separately that official DLSS 5 access is currently limited to RTX 50-series GPUs and GeForce NOW, which lines up with why modders are working around the restriction rather than waiting for Nvidia to widen access on its own timeline. Nvidia’s own GeForce news hub has not published anything acknowledging the mod as of this writing.
There’s also a practical reason CD Projekt Red is unlikely to rush an official statement: the studio just shipped a major Remastered update days ago and is still supporting a wide hardware matrix across PC, Switch 2, and Steam Deck. Validating an unofficial injection tool on top of that isn’t a small ask, and there’s no indication it’s anywhere near their current priority list.
Historical Context: How DLSS Got to Version 5
Nvidia’s upscaling technology has moved fast since its 2018 debut. Early DLSS versions focused narrowly on reconstructing a higher-resolution image from a lower-resolution render. Later generations added temporal accumulation, frame generation, and eventually multi-frame generation, each version pushing more of the rendering workload onto AI inference rather than traditional rasterization or ray tracing. DLSS 5’s 3D-Guided Neural Rendering approach is the furthest step yet in that direction, feeding the model scene geometry directly instead of just finished frames.
That trajectory also explains why modders are so eager to force DLSS 5 into older titles the moment any piece of it leaks. Each generational jump has historically delivered a visible quality or performance leap, and PC gaming’s modding community has a long track record of not waiting for official rollout schedules, this site tracked a similar pattern with independent DLSS 5 stress testing on the RTX 5090 that landed the day before Nvidia’s own official launch window.
Market Impact: What This Means for Modders, Nvidia, and RTX 50 Sales
For Nvidia, unofficial mods like this one are a mixed bag commercially. On one hand, community tools showing off DLSS 5’s visual upside in a beloved game like The Witcher 3 generate exactly the kind of organic buzz that reinforces the case for buying into the RTX 50 series, particularly the RTX 5090, which remains the card with enough horsepower to absorb a 30% hit and stay playable. On the other hand, every unofficial implementation that ships with visible bugs, like the HDR color shift reported here, risks being mistaken by less technical players for an official Nvidia feature falling short.
For the modding community, this is another data point in a fast-moving pattern that outlets like Tom’s Hardware have tracked closely all year: DLSS 5 components have been leaking and getting reverse-engineered into unsupported games and unsupported GPU generations for weeks now. Tools like ShortFuse’s DLSS 5 Tool are effectively racing ahead of Nvidia’s own rollout schedule, which typically starts with a narrow set of RTX 50-series partner titles before expanding. That gap between what’s technically possible and what Nvidia has officially sanctioned is where most of this year’s DLSS 5 mod stories, including this one, keep originating.
Competitive Comparison: DLSS 5 Injection vs Official Path Tracing Tools
Compared with CD Projekt Red’s own official path tracing and DLSS 4.5 Ray Reconstruction stack, the unofficial DLSS 5 injection is solving a narrower problem. The official update targets overall lighting fidelity and frame rate at scale, with Nvidia citing multi frame generation gains up to 6x on RTX 50-series cards under its own test conditions. The community injection is laser-focused on one thing: character facial and material detail, delivered at a real, measured performance cost rather than a marketing multiplier.
That narrower scope is actually part of why the DLSS 5 injection story is getting attention. It isn’t promising a free performance upgrade the way frame generation marketing sometimes implies; it’s an explicit quality-for-frame-rate trade that players can see and measure themselves, using tools that are already public. That transparency, even around an unofficial hack, tends to build more trust in enthusiast circles than a vendor’s own best-case benchmark slide.
What Comes Next: 5 Predictions for DLSS 5 Modding
- Expect ShortFuse’s tool and similar injectors to spread to other character-driven RPGs with dated facial models, following the same pattern that pulled DLSS 5 into The Witcher 3.
- The HDR highlight and color shift issue is likely to get patched by the modding community within weeks, since it’s a well-understood category of bug rather than a fundamental limitation of the technique.
- Nvidia will likely stay publicly silent on unofficial injections unless one causes a stability or security problem serious enough to force a statement.
- Performance costs on the RTX 5090 should narrow somewhat as injector tools mature and the resolution-scaling workaround Lecram identified gets built into more implementations by default.
- CD Projekt Red is unlikely to add official DLSS 5 support to The Witcher 3 Remastered in the near term, given the studio just finished a major update cycle across PC, Switch 2, and Steam Deck.
Frequently Asked Questions
Is DLSS 5 officially supported in The Witcher 3 Remastered?
No. There is no official DLSS 5 implementation in The Witcher 3: Wild Hunt — Remastered. The reported integration uses an external, community-built tool, not a feature shipped by CD Projekt Red or Nvidia.
What tool is being used to inject DLSS 5 into the game?
Reports identify ShortFuse’s DLSS 5 Tool as one of the tools used for the injection. A separate implementation from a modder known as Lecram has also been used to test Neural Rendering overhead specifically.
How much performance does the DLSS 5 injection cost?
With path tracing enabled, testing on a GeForce RTX 5090 reported a performance cost of roughly 26% to 30%. In one specific test, frame rate dropped from 50 FPS to 35 FPS, with frame time rising from 20.0 milliseconds to 28.6 milliseconds.
Does the DLSS 5 mod cause any visual problems?
Yes. The injection can tone down highlights and introduce a slight color shift, which is reported to be particularly noticeable on HDR displays.
Is this the same as the official September 29 Witcher 3 Remastered update?
No. The official update added path tracing, DLSS 4.5 Ray Reconstruction, and Dynamic Multi Frame Generation, but it does not include DLSS 5. The DLSS 5 injection is a separate, unofficial modification running independently of that patch.
Which GPUs can run the DLSS 5 injection?
The reported testing was done on a GeForce RTX 5090. Broader compatibility across other RTX generations has not been confirmed for this specific Witcher 3 implementation.
Can I reduce the performance cost of the DLSS 5 injection?
Lecram’s mod found that halving the Neural Rendering resolution reduced rendering time by 3.2 milliseconds, though at the cost of reduced image quality. There’s no in-game setting for this; it has to be configured through the injector tool.
Is it safe to install unofficial DLSS 5 injection tools?
These are unofficial, unsupported community tools with no warranty from CD Projekt Red or Nvidia. Players should weigh the visual upside against the performance cost, potential HDR color issues, and the general risk of installing third-party rendering injectors on any save file or system they care about.
