Repository navigation
Releases
WrongGPU 0.6.5 — Experimental
WrongGPU 0.6.5
Download WrongGPU-0.6.5.zip from the release page and extract it, then run WrongGPU-0.6.5.exe (see Quick start).
WrongGPU 0.6.5 adds Model L and Model K, two more super-resolution models you can choose per game, and brings
the fixes planned for 0.6.1 (0.6.1 was not released; everything in it is in 0.6.5). Model M stays the default. If you use 0.6.0, update
your games with the launcher (each game's page offers Update).
Still a work in progress. WrongGPU is still being worked on, and 0.6.5 is a pre-release. In some games or scenes
you may still see visual bugs, such as artifacts or flicker. If you do, we'd like to hear about it: on the game's page
in the launcher, click Collect logs, and send the zip it makes to us in the #bug-reports channel of the
WrongGPU Discord server or in an issue on GitHub, together with a short description of what you saw (the game, the
scene, your settings) and a screenshot. Every report helps us fix it.
What's new in 0.6.5 (since 0.6.0)
Model L (new)
- A new model, off by default and still under test. Model L is a larger super-resolution model than Model M:
it has a full-resolution encoder and decoder and its own reconstruction step. Model M stays the default for every
game; Model L is a choice you make per game. - Converted on your PC. Like Model M, Model L's data is converted once on your PC from a DLSS model file
(nvngx_dlss.dll) of version 310.5 or newer from any game or app you have installed; WrongGPU never downloads or
ships it. Convert it once from a command prompt in WrongGPU's folder:WrongGPU.exe model convert --preset=L. - Choosing it. For one game:
WrongGPU.exe set "<the game's .exe>" model=L(model=Mgoes back). In OptiScaler's
menu it is the upscaler WrongGPU Model L, next to WrongGPU Model M. - Runs on Direct3D 12 inside the game's own command list, like Model M: no AMD HIP runtime needed.
- GPU time. In Cyberpunk 2077 at 1080p Quality (1280x720 upscaled to 1920x1080) on a Radeon RX 9070 XT, standing
still at the same spot, measured in the same sitting: the model's GPU time per frame (all of its kernels) is
2.67 ms with Model L and 1.17 ms with Model M
(clean/l/records/cp2077-model-l-timing-2026-11-16.json
has the record).
Model K (new)
- Another model, off by default and still under test. Model K is a different super-resolution network from
Model M, with its own implementation in WrongGPU. Model M stays the default for every game; Model K is a choice you
make per game. - Converted on your PC. Like the other models, Model K's data is converted once on your PC from a DLSS model file
(nvngx_dlss.dll) of one of your games; WrongGPU never downloads or ships it. From a command prompt in WrongGPU's
folder:WrongGPU.exe model convert --preset=K. - Choosing it. For one game:
WrongGPU.exe set "<the game's .exe>" model=K(model=Mgoes back). In OptiScaler's
menu it is the upscaler WrongGPU Model K. - Runs on Direct3D 12 inside the game's own command list, like Model M: no AMD HIP runtime needed. Tested in
Cyberpunk 2077 at 1080p Quality. - GPU time. In Cyberpunk 2077 at 1080p Quality (1280x720 upscaled to 1920x1080) on a Radeon RX 9070 XT, standing
still at the same spot, measured one right after the other: the model's GPU time per frame (all of its kernels) is
1.03 ms with Model K and 1.17 ms with Model M
(clean/k/records/cp2077-model-k-timing-2026-11-15.json
has the record). - Optional faster approximation (
k_approx), off by default. With nothing set, Model K runs its exact path. Adding
k_approx=a1,a2to theruntime_optionsline of the game'swronggpu.iniselects close approximations of two
stages: the input stage's logarithm, exponent and divisions (a1) and the output stage's divisions (a2). Model K,
1440p Quality, WrongGPU's test harness (direct route) on a Radeon RX 9070 XT: the frame takes 1.37 ms with
k_approx=a1,a2and 1.58 ms on the exact path of the same build. The output differs slightly from the exact path;
compared with the exact path and with reference images it was rated very, very close on both test sets (a Cyberpunk
2077 sequence and a thin-line scene), with no drift over time. Frames with a render size above 0.68x the output (for
example DLAA) or a jitter outside +-0.5 keep the exact input stage even witha1(one log line). It runs only on
WrongGPU's native Direct3D 12 route (the in-game route); where it can't be used, Model K is refused at start and the
game keeps its own upscaler. - If you used Preset K with an older WrongGPU, the launcher no longer asks to switch that game to Model M when it
updates it: the game stays on Model K.
Faster kernels, same output
- Model L: its Swin stage takes 7.0 µs less per frame and its decoder stage 2.5 µs less at 1440p Quality (1707x960
upscaled to 2560x1440); at 1080p Quality (1280x720 upscaled to 1920x1080) they take 2.5 µs and 1.0 µs less. The
output does not change. - Model M: its final (post) stage takes 2.5 µs less per frame at 1440p Quality and 1.5 µs less at 1080p Quality.
The output does not change. - Measured on a Radeon RX 9070 XT in our offline benchmark, which runs frames back to back (five rounds, the median
difference per stage); in a game the saving per frame can differ.
Fixed
- Ray Reconstruction: video memory no longer grows while Ray Reconstruction is available but switched off. In
0.6.0, a game that sends its Ray Reconstruction inputs every frame (Cyberpunk 2077 does, from its main menu on) made
the plugin keep a copy of each frame's inputs that was never freed while no Ray Reconstruction was running, until the
PC ran out of video memory. The copies are now freed as soon as the GPU is done with them (#8). - Ray Reconstruction plugin: no more crash with an older Microsoft C++ runtime.
WrongGPU-RR.asiwas the only part
of WrongGPU built against the shared C++ runtime, and with an oldermsvcp140.dll(an old Visual C++ redistributable,
or a Proton prefix) the game aborted at start or froze shortly after. The plugin now carries its own runtime, like the
rest of WrongGPU, and needs nomsvcp140.dll(#9). - Model M under Proton: one of WrongGPU's small helper shaders used a keyword that Wine's shader compiler rejects,
so Model M could not start under Proton. The keyword is gone (it was not needed). Model M under Proton also needs a fix
in vkd3d-proton's shader translator; see Discussion #10 for the state of that (#7). We have not tested Model M under
Proton ourselves. - Model M's driver check at start is stricter: it now tells apart drivers or translation layers that lay out the
matrix data differently, instead of passing them (#14). - Collect logs from a game's uninstaller (Apps & features, Modify) no longer reports valid model data as
invalid: it says the data is not verified there and points to Collect logs in the launcher (#24). - Uninstall, Update, Repair and the move out of a wrong folder never discard your files. When a file can't go back
as it was, because you or another program changed it after the install, it stays where it is and WrongGPU's copy of
what was there before is kept in aWrongGPU-originalsfolder. The result says "partly restored" and where the copy
is. Awronggpu.iniyou edited by hand stays after an uninstall (it used to be deleted while the message said it was
left in place) (#70, #73). - The launcher works next to your own OptiScaler setup: it recognises another OptiScaler install and its plugins,
asks before it moves anything aside, and moves only the files you agreed to, checked by their contents (#23). - Ray Reconstruction: GPU memory is released safely when a game ends Ray Reconstruction. The plugin now keeps an
instance's memory until the GPU has finished its last frame, instead of freeing it at once (#63). - Ray Reconstruction stays off when another Ray Reconstruction plugin is already active. It switches itself off
only when the other plugin is positively identified, and says so inwronggpu-rr.log. A different plugin it cannot
identify keeps WrongGPU's on;rr_other_plugin = yieldin the plugin's settings keeps WrongGPU's off (#22). - Ray Reconstruction under Proton: the thread that prepares Ray Reconstruction's GPU code now has a large enough
stack for vkd3d-proton's shader translator, and a pipeline that fails to build is logged (#149).
Also changed
- The launcher reads the developer-only HIP runtime setting only in test builds, so a setting left on a PC can't
change what a release installs (#25).
Thanks
Thanks to j0nsh1n for the reports and the analysis behind #7, #8 and #9, for the Linux write-up in
Discussion #10, and for the Ray Reconstruction fix under Proton (#149, #196).
Quick start
- Install. Run WrongGPU-0.6.5.exe from the zip. Its first-run check looks at your PC, then offers Install
for this user (the default; afterwards it is WrongGPU in the Start menu) or Run portable, and then shows
your games. Open a game and click Install (the launcher gets OptiScaler for it the first time). The game's page
then shows a checklist, Turn it on in the game, with the next two steps. Borderlands 4 needs one Engine.ini
setting for Ray Reconstruction: the launcher asks about it right after the install. Already on 0.6.0? Start the new
launcher; your games show Update. - Choose the upscaler in the game. Start the game and choose DLSS as the upscaler in its graphics settings (FSR
or XeSS also work). With TAA or upscaling off, the game never asks for an ...
WrongGPU 0.6.0 — Experimental
WrongGPU 0.6.0
Download WrongGPU-0.6.0.zip from the release page and extract it, then run WrongGPU-0.6.0.exe (see Quick start).
WrongGPU 0.6.0 is the first public release since 0.4.5, and it changes how you use WrongGPU: a launcher replaces
the setup wizard, the launcher gets OptiScaler for you, Model M no longer needs an AMD HIP runtime, and
WrongGPU now does Ray Reconstruction too. It includes everything from the 0.5.x early-access builds.
Still a work in progress. WrongGPU is still being worked on, and 0.6.0 is a pre-release. In some games or scenes
you may still see visual bugs, such as artifacts or flicker. If you do, we'd like to hear about it: on the game's page
in the launcher, click Collect logs, and send the zip it makes to us in the #bug-reports channel of the
WrongGPU Discord server, together with a short description of what you saw (the game, the scene, your settings)
and a screenshot. Every report helps us fix it.
Quick start
- Install. Run WrongGPU-0.6.0.exe from the zip. Its first-run check looks at your PC, then offers Install
for this user (the default; afterwards it is WrongGPU in the Start menu) or Run portable, and then shows
your games. Open a game and click Install
(the launcher gets OptiScaler for it the first time). The game's page then shows a checklist, Turn it on in the
game, with the next two steps. Borderlands 4 needs one Engine.ini setting for Ray Reconstruction (so did
Hogwarts Legacy before its November 2026 update): the launcher asks about it right after the install. - Choose the upscaler in the game. Start the game and choose DLSS as the upscaler in its graphics settings (FSR
or XeSS also work). With TAA or upscaling off, the game never asks for an upscaler and WrongGPU stays idle. For a game
WrongGPU runs in without OptiScaler, the game's page tells you which upscaler to pick. - See it running. OptiScaler's FPS overlay shows which upscaler runs. To turn it on, use the checklist's Turn
on the FPS overlay button, or the game's page: OptiScaler → FPS overlay → On → Apply. Settings take effect the
next time the game starts, so turn it on before you start the game (or quit, Apply, and start it again).- With the WrongGPU edition of OptiScaler (the launcher downloads it), the overlay shows DLSS → WrongGPU Model M
while Model M upscales, or DLSS → WrongGPU RR and its mode while Ray Reconstruction runs. With another
OptiScaler it shows AMD FSR there, so check Last run instead. - In a game WrongGPU runs in without OptiScaler there is no FPS overlay. WrongGPU's own overlay in the game's corner
says Model M while it runs. - After you quit, the game's page shows the run under Last run: Model M, or Ray Reconstruction where it did the
upscaling.
- With the WrongGPU edition of OptiScaler (the launcher downloads it), the overlay shows DLSS → WrongGPU Model M
- Undo. On the game's page, More → Uninstall WrongGPU puts the game's own files back exactly as they were.
What's new in 0.6.0 (since 0.4.5)
The WrongGPU launcher replaces the setup wizard
In 0.4.5 you closed the game, ran WrongGPU-Setup and picked your game. Now there is one window, the WrongGPU launcher, for
all your games:
- Finds your games: it reads your Steam, Epic and GOG libraries and shows every game it finds as a tile in its
Library, with the art from your own Steam cache (nothing is downloaded or shipped for it). Add game takes a game
from anywhere else, Rescan looks again. - Shows what each game can do: can install, installed, update or repair, your own OptiScaler, another mod, an older
install, refused (for example games with anti-cheat, which are never supported), or running. - One click per game: Install, Update, Repair, Roll back (to the version before the last update) and Uninstall,
and an optional Play button. - A settings page per game with an Apply bar: WrongGPU on or off, what it runs on (Auto, Direct3D 12 or HIP), the
output filter, pre-exposure, sparkle guard, OptiScaler's FPS overlay and OptiScaler's own options, and for Ray
Reconstruction games its on/off switch and quality (see below). - Last run: what the game used the last time it ran (Model M, Direct3D 12 or HIP, Ray Reconstruction and its
cost), and Collect logs in one click for a bug report. - A first-run check of Windows, your graphics card, the Direct3D 12 path and the model data, then your choice:
Install for this user (a Start menu entry and one entry in Apps & features; the launcher uninstalls itself from
there) or Run portable. - Picks up your earlier installs: games you set up with the 0.5.x setup are taken over, keep their settings, and
are updated by the launcher (we tested this). Games set up with 0.4.x use the same install record and should be
taken over the same way, but we haven't tested that yet. - Works next to other tools: ReShade, Special K, ASI loaders, your own OptiScaler and similar mods are found and
kept, or moved aside with a backup only when you agree. A game with another upscaler mod gets a clear message, and
WrongGPU leaves that game alone. Older WrongGPU files without an install record (for example from a 0.4.x direct
install in an Unreal Engine game's plugin folder) are found and can be cleaned up with your OK. - Borderlands 4 and Hogwarts Legacy: "Fix it for me". Their Ray Reconstruction needs one engine setting, and
Borderlands 4 removes it on every start. After you install WrongGPU into either game, the launcher asks: Fix it
for me adds the setting (and makes Borderlands 4's file read-only so the game keeps it), Show me how opens the
game's page with the steps, the line to copy and a check that the file has it, Not now asks again next time. The
game's page (Engine.ini setting: WrongGPU or Myself) changes it at any time. Uninstalling WrongGPU undoes the fix.
The game's own Ray Reconstruction option may look greyed out or off; that's expected, the setting turns it on.
OptiScaler's overlay shows DLSS → WrongGPU RR and Last run shows Ray Reconstruction when it's working.
On Hogwarts Legacy since the game's November 2026 update, WrongGPU's Ray Reconstruction isn't available yet (see
Tested games), so the launcher doesn't ask there.
Chosen before the game's first start, the setting is added once the game has made its settings folder: start the game
once, then open the launcher (the game's page says "Will be added after you start the game once" until then). A game
installed in a protected folder (such as Program Files) never gets a permission prompt you didn't click for: its page
says "Waiting for the game's first start", then "Ready to add" (the Library lists the game under Needs attention
then, and the launcher says so once when it opens), and Fix it now adds the setting after Windows asks. - The whole launcher works with the keyboard and with screen readers: every control has a name for them. (An update
check is coming in a later version.)
No more hunting for OptiScaler
In 0.4.5 you had to download OptiScaler yourself and point the setup at it. Now the launcher downloads the WrongGPU
edition of OptiScaler itself the first time it needs it (OptiScaler with the plugin interface WrongGPU's Ray
Reconstruction uses; GPL, its own release page:
https://github.com/phantoslayer21/OptiScaler/releases/tag/wronggpu-edition-20261102.1), checks it against the size and
SHA-256 built into the launcher, refuses a download that doesn't match, and keeps it for every game. Nothing of
OptiScaler is inside WrongGPU's download. Offline, you can choose an OptiScaler download yourself (Settings); games
whose Ray Reconstruction needs the WrongGPU edition then get Model M only until the download works.
- In OptiScaler's menu, WrongGPU is an upscaler of its own (WrongGPU, version WrongGPU Model M), and the
launcher selects it for you. OptiScaler's overlay shows "DLSS → WrongGPU Model M", or "DLSS → WrongGPU RR" and the
mode while Ray Reconstruction runs. AMD's FSR stays available under OptiScaler's own FSR entries.
No AMD HIP runtime needed any more
In 0.4.5 Model M ran on HIP and needed a working AMD HIP runtime. Now, on the Radeon RX 9070 / RX 9060 series, Model M
runs on Direct3D 12 inside the game's own command list: it reads the game's textures and writes its output
directly, with no HIP. That now covers every mode up to native resolution (DLAA), including Ultra Quality and every
ratio between Quality and native. Measured on an RX 9070 XT with the 0.6.0 runtime (GPU time of WrongGPU's work per
frame, as its timing log reports it), on a synthetic benchmark:
| Mode | 1080p output | 1440p output |
|---|---|---|
| Quality | about 1.3 ms | about 2.2 ms |
| Ultra Quality | about 1.6 ms | about 2.8 ms |
| Native resolution (DLAA) | about 2.4 ms | about 4.3 ms |
In a real game it can be a little lower: in Cyberpunk 2077 at Quality we measured about 1.2 ms at 1080p and about 1.8 ms
at 1440p.
HIP is only used for the optional sparkle guard (and for frame capture in bug reports). Frames the network can't use
(for example a render size larger than the output) go to AMD's FSR, which stays available next to WrongGPU.
Ray Reconstruction (new)
- In games that use DLSS Ray Reconstruction (path tracing or ray tracing), WrongGPU now denoises and upscales the
ray-traced image with its own network, on Radeon RX 9000 cards. Tested: Cyberpunk 2077, RESIDENT EVIL requiem
(experimental), Borderlands 4 (with the one setting above), Hogwarts Legacy (up to the game's November 2026 update;
see Tested games) and Marvel's Spider-Man 2 (experimental, see below). - How to turn it on: install WrongGPU into the game with the launcher, then choose DLSS Ray R...
WrongGPU 0.4.5 — Experimental
Download WrongGPU-0.4.5.zip below and extract it. Close the game, run WrongGPU-Setup-0.4.5.exe, select your game and follow the installer. Download OptiScaler separately and supply its archive or folder. A working AMD HIP runtime and a compatible locally owned DLSS file are required.
WrongGPU 0.4.5
Model M on Radeon RX 9070 / 9070 XT. This release is about stability: it fixes the freezes, the memory growth and two crashes reported since 0.4.1. It also changes how WrongGPU is installed: OptiScaler is now required.
OptiScaler is now required
Earlier versions could also replace a game's own FSR 3 DLL ("direct" installation). That route is gone. WrongGPU now always runs as OptiScaler's FSR library, which works in more games and no longer touches the game's FSR files.
- The installer asks for your OptiScaler download (release archive, folder or
OptiScaler.dll). Silent installs need/OPTISCALER=<path>;/DIRECTFSRno longer exists. - Updating from a direct install: run the new installer on the same game. It first puts the game's original FSR DLLs back, then installs the OptiScaler route. Your
wronggpu.iniis kept. - The download no longer contains
ffx_fsr3_x64.dllandffx_fsr3upscaler_x64.dll.
Fixes
- Whole-PC freezes followed by a crash. 0.4.0 and 0.4.1 waited for each frame's inputs with an experimental method that had only been proven in Cyberpunk 2077. 0.4.5 uses the standard method in every game. Cost: about 0.07 ms per frame in Cyberpunk; no measurable change in Hogwarts Legacy.
- Video memory growing every time the upscaler restarts (changing quality mode, resolution, or switching upscalers). Each restart kept about 400 MB. In Hogwarts Legacy nine mode switches used to take the game from 3.9 GB to 7.5 GB; it now settles at 4.9 GB and stays there.
- Crash at the first upscaled frame in games whose command lists are taken over by the AMD driver's fast path (The Witcher 3 report; also seen in 007 First Light and Crimson Desert). WrongGPU now follows those lists; Model M runs in The Witcher 3. If a list still cannot be followed safely, that game is upscaled by AMD FSR instead of crashing.
- Frame spikes in games that re-create the upscaler while you play (The Witcher 3 with dynamic resolution re-creates it at every resolution step). Each re-create took WrongGPU about 120 ms. A destroyed upscaler is now kept warm for three seconds and handed to the next create with the same settings: about 0.1 ms. It holds about 0.8 GB of video memory during those three seconds only.
- A single inconsistent frame no longer ends Model M. During a resolution change a game can send one frame whose sizes do not fit its textures; 0.4.1 then handed the game to AMD FSR until the next restart of the upscaler. Such a frame now gets a plain upscaled frame and Model M carries on; only 30 such frames in a row fall back for good.
- Motion vectors at output resolution (Hogwarts Legacy with DLSS inputs) are now used at full resolution, as the original does, instead of being reduced to render resolution first. No cost in frame time; about 28 MB more video memory at 1440p (63 MB at 4K) in such games only.
motion_outres=pointinruntime_optionsbrings the earlier behaviour back. - Installer picked a DirectX tool as the game when the game ships the DirectX Agility SDK in a subfolder (The Witcher 3:
D3D12StateObjectCompiler.exe) and installed next to it. Fixed. - Installer: updating over an install whose WrongGPU files had been replaced by hand (for example with hotfix DLLs) could remove the game's saved original FSR DLL and then refuse to install. Such files are now recognised as WrongGPU's; the game's original is always kept and restored. Updating a WrongGPU + OptiScaler install no longer asks about "another mod".
Changes
- Output filter. The last step of the pipeline now uses the original filter's weights, which the installer reads from your own
nvngx_dlss.dlltogether with the model. On the reference sequence this brings the result closer to native DLSS (48.4 dB to 54.5 dB) at no cost in frame time. In games the picture is about 10 % softer in the very finest detail and slightly steadier; the earlier look is available withoutput_filter=analyticinruntime_options(wronggpu.ini). If your DLSS file's filter is not known to this version, the earlier filter is used and the installer says so. - Pre-exposure is handled as in 0.4.1. (A rule closer to our reading of the original was tried in the 0.4.5 test builds; with Hogwarts Legacy's very small pre-exposure it made hair and other dithered detail noisy. It remains available as
pre_exposure=original.) - In OptiScaler's upscaler list the entry is now named
3.1.5 WrongGPU (Model M)(OptiScaler reads a version number from the name).
Not in this release
- Preset K is not included yet.
- Sparkle guard: present as an unlisted experimental option, off.
Tested
Installed with this installer and running Model M on an RX 9070 XT: Hogwarts Legacy, Borderlands 4 (updated from a 0.4.x direct install), Cyberpunk 2077 (validated) and The Witcher 3 Remastered, all through OptiScaler 0.9.5.4. Earlier 0.4.5 test builds also ran Control, Crimson Desert and Ratchet & Clank: Rift Apart. Every game other than Cyberpunk 2077 is experimental.
Known issues
- The plain frame WrongGPU shows the first time it meets a new command list of the AMD driver's fast path (The Witcher 3, 007 First Light) is still there: a handful of single frames per session, mostly at start-up.
- OptiScaler's FPS header may still show an FSR version for WrongGPU.
- RX 9060 XT: code is included but has not been tested on hardware.
- A rarely used fallback path for sharing memory with the game still keeps memory when the upscaler restarts; the log warns when it is in use.
- With upscaler inputs that carry no depth (for example Hogwarts Legacy set to XeSS inputs) WrongGPU cannot run and the game is upscaled by AMD FSR without a message on screen; the log says so. Use DLSS or FSR inputs.
- 007 First Light crashes about a second after start when OptiScaler uses WrongGPU as its FSR library (also with WrongGPU set to hand every frame to AMD FSR, and also with the earlier 0.4.5 test builds that ran it). With OptiScaler's own built-in FSR it runs. Being investigated; 007 First Light is not supported in this release.
- Games with anti-cheat are not supported.
Requirements
Radeon RX 9070 / 9070 XT, a current AMD Adrenalin driver, Windows 10/11 64-bit, and a game (or any installed game) with nvngx_dlss.dll 310.5 or newer for the model data. OptiScaler is supplied separately; WrongGPU does not include or download it. No NVIDIA code or model data is in this download.
Archive SHA-256
8b78aab35ac1f8da939b8aff4a6f21adebb3b4e1101a98a2dee2ab5a27a2d898
WrongGPU 0.4.1 — Experimental
Most of the focus of 0.4.1 is making the mod easier to use and getting it working in more games. More games, less bugs.
I never released 0.4.0 on GitHub, so everything from that is included here too. Preset K isn't in this one yet.
OptiScaler is the default from now on. WrongGPU just adds Model M as another option in the menu, so you can switch between it and FSR 4.1.1 the same way you're already used to.
Other changes
- Fixed the black dots/arc around the sun in Cyberpunk.
- Fixed the startup stalls in Crimson Desert. The ground shimmer isn't fixed yet.
- Added RX 9060 XT support. I don't have one myself, so more testing is needed, especially on the 8 GB card.
- Includes the runtime performance work since 0.3.1 and several fixes for crashes with OptiScaler and AMD's upscaler.
- Fixed an issue where cleanup from an old install could delete files from a new one.
- Improved the installer's support logs. Collect logs gives you a ZIP you can send with a bug report. It doesn't upload anything itself.
Installing
Download WrongGPU-0.4.1-Sun-Fix.zip below and extract it. Close the game, run WrongGPU-Setup-0.4.1.exe, select your game and follow the installer.
You'll need to download OptiScaler separately and give the installer its folder or archive. You also need the AMD HIP runtime and a compatible nvngx_dlss.dll 310.5 or newer from a game you own. NVIDIA's DLL and model weights aren't included.
Still experimental, so let me know if you run into anything. Include your game, GPU, driver and settings, and grab the logs from the installer. Check the ZIP before posting it since it can contain local file paths.
Some OptiScaler versions show an older FSR version number even with WrongGPU selected. Check the selected upscaler in the menu.
Personal, non-commercial use. Licence and third-party notices are in the ZIP.
SHA-256
WrongGPU-0.4.1-Sun-Fix.zip:
e14e7e6ac9a722a7d7727ca83f2bf813c4faf3523cc5bf39c5abed6c0addcf90
WrongGPU 0.3.1 — Experimental
Experimental Model M neural upscaling through AMD FSR for Radeon RX 9070 / RX 9070 XT in DirectX 12 games.
Download and install
- Download WrongGPU-0.3.1.zip from the assets below and extract it.
- Close the game, run WrongGPU-Setup-0.3.1.exe, select your game, and click Install.
- Select AMD FSR 3 or newer and a quality mode in the game.
- Check that the WrongGPU overlay shows Model M active.
Insert hides/shows the overlay and restores the full panel for 10 seconds. Home switches between WrongGPU and AMD FSR.
New in 0.3.1
- Model M is enabled by default on a fresh installation.
- Fixed the HIP startup failure observed in Borderlands 4 with stale ROCm settings or a broken compiler cache.
- Background model startup, with AMD FSR covering initialization.
- Reduced logging overhead: per-frame logging is off by default and log writes run in the background.
- Faster reconstruction/output filtering. Representative synthetic post/filter tests measured roughly 9% improvement at 1440p Quality and 8% at 4K Performance. Gains vary by mode; these are stage timings, not overall FPS gains.
- Overlay toggle fix and a small output rounding correction.
Requirements
- 64-bit Windows 10 or 11.
- RX 9070 or RX 9070 XT. RX 9060-series cards are not supported in this version.
- AMD Adrenalin drivers and a working AMD HIP runtime. The installer checks the runtime; the Windows HIP SDK may be needed if it is unavailable.
- A DirectX 12 game with AMD FSR 3+, without anti-cheat.
- A locally available nvngx_dlss.dll 310.5+ that you are entitled to use. The installer searches your games and converts the model locally. NVIDIA's DLL and model data are not bundled; do not share converted model files.
Known limitations
- Tested in Cyberpunk 2077 and Borderlands 4. Other games are experimental; use Collect logs when reporting issues.
- Borderlands 4 flickering at 4K Performance is still under investigation.
- In Cyberpunk select AMD FSR 3. Its FSR 2.1 and FSR 4 options bypass WrongGPU. Its bundled DLSS 310.1 is too old for conversion, so supply a compatible file from another game.
- Neural inference has a significant frame cost; AMD FSR 4 remains faster in the recorded comparisons.
Uninstall and licence
Uninstall through Windows Settings → Apps → Installed apps → WrongGPU - . The original game files are restored from backup. Shared model data is retained while another WrongGPU installation needs it.
Personal, non-commercial use under LICENSE.txt. AMD's required licence notice is included.
Checksums
ZIP SHA-256:
2e3027f37e3de39f38fa731bde2ee8fce7b4ae27d524ebdcdd9f188f88f20a59
The attached WrongGPU-0.3.1.zip.sha256 verifies the archive. SHA256SUMS.txt inside the ZIP verifies the unpacked files.