Game: Native HDR with the PsychoV35 tone mapper turns FSR 4 (and DLSS) off: the game's own upscale runs instead, jagged and oversharpened

MustardTiger commented

2026-11-13 15:44:13 +00:00

Contributor

Longshot version

nightly-64-000f19fb

Channel

Nightly

What kind of problem

Graphics (missing, black or wrong-coloured things, lighting, flicker)

What happened

Problem

With HDR on Native, HDR tone mapper on PsychoV35 and AMD FSR 4 Native AA as the upscaler, the picture becomes very oversharpened, even with sharpness slider at 0. Edges, Link's in particular, are jagged, and the whole image looks as if RCAS were turned far past its maximum. The Sharpness slider seems to have no effect.

Setting the tone mapper back to Vanilla brings FSR 4 back, and the picture looks normal again.

I first reported this on Hookshot before its repo went down. A similar report there covered DLSS / DLAA, with a PR that, if I remember correctly, was about the RGBA16F scene buffer and covered DLSS only, not FSR.

Why

FSR 4 isn't oversharpening, it's not running at all:

PsychoV35 (Hookshot #2481, ddb156df) makes the scene buffer RGBA16F instead of R11G11B10F. That PR says Vanilla keeps R11G11B10F "because the temporal upscalers only take that scene format".
The temporal chain only takes a B10G11R11 scene. temporal_note_scene_draw returns early for any other format (gpu/vk/vk_temporal.cpp:675), so no scene camera is recorded. Other checks also require B10G11R11 for the network's input and output (vk_temporal.cpp:829, :886, :919), for actor motion (vk_draw.cpp:6507) and for the reactive mask (vk_reactive.cpp:215).
With no camera, the chain falls back to OoT's own upscale network. Here that network runs at 2560x1440 → 2560x1440: no temporal anti-aliasing (hence the jaggies), FSR 4's RCAS not involved (hence the slider doing nothing), and the very sharp look.

The menu doesn't say the upscaler is switched off. The tone mapper's help text only describes highlights.

Where in the game

All areas

How often

Every time

Graphics card and driver version

RX 9070 XT, 26.10.2

CPU, RAM and operating system

Ryzen 7 9800X3D, 32GB DDR5, Windows 11

Changes from the defaults

Aspect ratio: 16:9 (monitor's) (default: 4:3)
Output resolution: 2560x1440 (native) (default: 2048x1152 (game's))
Upscaler: AMD FSR 4 (default: AMD FSR 4)
Render resolution: Native (FSR 4, 2560x1440) (default: Native (FSR 4, 2560x1440))
Frame pacing: On (default: Off)
AMD Anti-Lag 2: On (default: Off)
Fullscreen: On (default: Off)
Window scaling filter: Not needed (window = output) (default: Not needed (window = output))
HDR: Native (the game's) (default: Off)
HDR peak brightness: 700 nits (default: 1000 nits)
HDR tone mapper: PsychoV35 (default: Vanilla)
GPU device: 0: AMD Radeon RX 9070 XT (default: Auto)
VRAM budget: 11 GB (default: Auto)
FPS counter: Dev (default: Off)
Menu size: Small (default: Medium)
Game language: English (UK) (default: English (US))
Discord status: Off (default: On)
Controller in background: On (default: Off)
Mouse camera: Native (default: As the stick)
Invert mouse vertical: On (default: Off)
Camera speed: 125% (default: 100%)
Stick dead zone: 10% (default: Default (24%))
Button prompts: Xbox (default: Auto)
Switches set (the environment, longshot_env.txt; a value only when it is a number or on/off, and never for a name with TOKEN, KEY, ROOM, SECRET, PASS, SERVER or USER in it):
LONGSHOT_NO_UPDATE_CHECK=1

longshot_log.txt

longshot_log
longshot_log.1
report

Screenshots or video

No response

Before you send it

The problem is still there on the newest release or nightly.
I searched the open issues for it.
I'm not attaching game files, keys, the game's executable, its .bin caches or saves.

### Longshot version nightly-64-000f19fb ### Channel Nightly ### What kind of problem Graphics (missing, black or wrong-coloured things, lighting, flicker) ### What happened ### Problem With **HDR** on **Native**, **HDR tone mapper** on **PsychoV35** and **AMD FSR 4 Native AA** as the upscaler, the picture becomes very oversharpened, even with sharpness slider at 0. Edges, Link's in particular, are jagged, and the whole image looks as if RCAS were turned far past its maximum. The **Sharpness** slider seems to have no effect. Setting the tone mapper back to **Vanilla** brings FSR 4 back, and the picture looks normal again. I first reported this on Hookshot before its repo went down. A similar report there covered DLSS / DLAA, with a PR that, if I remember correctly, was about the RGBA16F scene buffer and covered DLSS only, not FSR. ### Why FSR 4 isn't oversharpening, it's not running at all: 1. PsychoV35 ([Hookshot #2481](https://github.com/NotRexed/Hookshot/pull/2481), `ddb156df`) makes the scene buffer **RGBA16F** instead of R11G11B10F. That PR says Vanilla keeps R11G11B10F *"because the temporal upscalers only take that scene format"*. 2. The temporal chain only takes a B10G11R11 scene. `temporal_note_scene_draw` returns early for any other format (`gpu/vk/vk_temporal.cpp:675`), so no scene camera is recorded. Other checks also require B10G11R11 for the network's input and output (`vk_temporal.cpp:829`, `:886`, `:919`), for actor motion (`vk_draw.cpp:6507`) and for the reactive mask (`vk_reactive.cpp:215`). 3. With no camera, the chain falls back to OoT's own upscale network. Here that network runs at 2560x1440 → 2560x1440: no temporal anti-aliasing (hence the jaggies), FSR 4's RCAS not involved (hence the slider doing nothing), and the very sharp look. The menu doesn't say the upscaler is switched off. The tone mapper's help text only describes highlights. ### Where in the game All areas ### How often Every time ### Graphics card and driver version RX 9070 XT, 26.10.2 ### CPU, RAM and operating system Ryzen 7 9800X3D, 32GB DDR5, Windows 11 ### Changes from the defaults Aspect ratio: 16:9 (monitor's) (default: 4:3) Output resolution: 2560x1440 (native) (default: 2048x1152 (game's)) Upscaler: AMD FSR 4 (default: AMD FSR 4) Render resolution: Native (FSR 4, 2560x1440) (default: Native (FSR 4, 2560x1440)) Frame pacing: On (default: Off) AMD Anti-Lag 2: On (default: Off) Fullscreen: On (default: Off) Window scaling filter: Not needed (window = output) (default: Not needed (window = output)) HDR: Native (the game's) (default: Off) HDR peak brightness: 700 nits (default: 1000 nits) HDR tone mapper: PsychoV35 (default: Vanilla) GPU device: 0: AMD Radeon RX 9070 XT (default: Auto) VRAM budget: 11 GB (default: Auto) FPS counter: Dev (default: Off) Menu size: Small (default: Medium) Game language: English (UK) (default: English (US)) Discord status: Off (default: On) Controller in background: On (default: Off) Mouse camera: Native (default: As the stick) Invert mouse vertical: On (default: Off) Camera speed: 125% (default: 100%) Stick dead zone: 10% (default: Default (24%)) Button prompts: Xbox (default: Auto) Switches set (the environment, longshot_env.txt; a value only when it is a number or on/off, and never for a name with TOKEN, KEY, ROOM, SECRET, PASS, SERVER or USER in it): LONGSHOT_NO_UPDATE_CHECK=1 ### longshot_log.txt [longshot_log](/attachments/7320bed9-fd87-43aa-a769-8a682b718c31) [longshot_log.1](/attachments/d8d41a73-5219-4023-a5d7-008ab8daf40d) [report](/attachments/a6a19447-9808-42f8-8575-da60e18cc208) ### Screenshots or video _No response_ ### Before you send it - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.

longshot_log.txt

265 KiB

longshot_log.1.txt

151 KiB

report.txt

3.3 KiB

MustardTiger added the

kind

bug

label

2026-11-13 15:44:13 +00:00

MustardTiger changed title from ~~Game:~~ to Game: Native HDR with the PsychoV35 tone mapper turns FSR 4 (and DLSS) off: the game's own upscale runs instead, jagged and oversharpened

2026-11-13 15:44:58 +00:00