Native HDR mode looks washed out / grey on LG OLED G5 (Windows, RTX 5080), while Tone Mapping mode looks fine #2162

Closed
opened 2026-11-11 05:20:41 +00:00 by alucard567 · 2 comments
alucard567 commented 2026-11-11 05:20:41 +00:00 (Migrated from github.com)

Hookshot version

hookshot v2.1.0 (source 633eb435)

What kind of problem

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

What happened

When HDR is set to Native (the game's), the whole picture looks washed out: greyish, low contrast, as if watching HDR video on an SDR display. I assumed Native would give the best picture since it passes the game's own HDR output through, but it looks clearly wrong (screenshot 1).

Switching HDR to Tone Mapping mode fixes it right away: colours and contrast look normal. Windows HDR is on, and HDR works fine in other games on this display, so this seems specific to Hookshot's Native HDR path.

Is this expected, or is something going wrong with how the game's HDR output is presented in Native mode? Happy to test a different setting or build if that helps.

Where in the game

The Legend of Zelda: Tears of the Kingdom — Hyrule Castle Town, walking in through the main gate.

How often

Every time

Graphics card and driver version

NVIDIA GeForce RTX 5080 (Vulkan driver 0x9b438000 as reported in the log)

CPU, RAM and operating system

CPU model not shown in the log; 64 GB RAM; Windows

Changes from the defaults

From the Graphics menu (screenshot 2):

  • Quality preset: Custom
  • Fullscreen: On
  • Frame generation: Off; Frame pacing: On
  • HDR: Native (the game's)
  • HDR paper white: 200 nits; HDR peak brightness: 1000 nits
  • Game frame rate cap: 60 (the console's)
  • NVIDIA Reflex: On
  • Output resolution: 3840x2160
  • Upscaler: NVIDIA DLSS

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

Attached: hookshot_log.1.txt (full log of the session).

Log lines that stood out to me:

[hos host] vk: HDR: an HDR10 surface (format 64), paper white 200 nits, peak 2000 nits
[hos sead::MainThread] vi: QueryDisplayHdrStatus -> SDR
[hos sead::MainThread] vi: QueryDisplayHdrStatus -> HDR10 (the game's native HDR)
[hos Presentation Thread] nvn: window of 3 textures (3 active), 3840x2160 format 0x3d
[hos sead::MainThread] vi: QueryDisplayHdrStatus -> SDR
[hos Presentation Thread] nvn: window of 3 textures (3 active), 3840x2160 format 0x25

During the session the game's HDR status flips SDR -> HDR10 -> SDR, and the window format flips between 0x25 (RGBA8) and 0x3d (RGB10A2) along with it. Possibly related to #2038 (Native HDR flicker where one window image stays RGBA8), but in my case the picture is constantly washed out rather than flickering.

hookshot_log.1.txt

Screenshots or video

Screenshot 1 (gameplay): washed-out picture with Native HDR.
Screenshot 2 (settings): Graphics menu showing HDR set to Native.

1 2

Before you send it

  • I'm on the newest release, or the problem is still there on it.
  • I searched the open issues for this problem.
  • I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.
### Hookshot version hookshot v2.1.0 (source 633eb435) ### What kind of problem Graphics (missing, black or wrong-coloured things, lighting, flicker) ### What happened When HDR is set to **Native (the game's)**, the whole picture looks washed out: greyish, low contrast, as if watching HDR video on an SDR display. I assumed Native would give the best picture since it passes the game's own HDR output through, but it looks clearly wrong (screenshot 1). Switching HDR to **Tone Mapping** mode fixes it right away: colours and contrast look normal. Windows HDR is on, and HDR works fine in other games on this display, so this seems specific to Hookshot's Native HDR path. Is this expected, or is something going wrong with how the game's HDR output is presented in Native mode? Happy to test a different setting or build if that helps. ### Where in the game The Legend of Zelda: Tears of the Kingdom — Hyrule Castle Town, walking in through the main gate. ### How often Every time ### Graphics card and driver version NVIDIA GeForce RTX 5080 (Vulkan driver 0x9b438000 as reported in the log) ### CPU, RAM and operating system CPU model not shown in the log; 64 GB RAM; Windows ### Changes from the defaults From the Graphics menu (screenshot 2): - Quality preset: Custom - Fullscreen: On - Frame generation: Off; Frame pacing: On - HDR: Native (the game's) - HDR paper white: 200 nits; HDR peak brightness: 1000 nits - Game frame rate cap: 60 (the console's) - NVIDIA Reflex: On - Output resolution: 3840x2160 - Upscaler: NVIDIA DLSS ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt Attached: hookshot_log.1.txt (full log of the session). Log lines that stood out to me: [hos host] vk: HDR: an HDR10 surface (format 64), paper white 200 nits, peak 2000 nits [hos sead::MainThread] vi: QueryDisplayHdrStatus -> SDR [hos sead::MainThread] vi: QueryDisplayHdrStatus -> HDR10 (the game's native HDR) [hos Presentation Thread] nvn: window of 3 textures (3 active), 3840x2160 format 0x3d [hos sead::MainThread] vi: QueryDisplayHdrStatus -> SDR [hos Presentation Thread] nvn: window of 3 textures (3 active), 3840x2160 format 0x25 During the session the game's HDR status flips SDR -> HDR10 -> SDR, and the window format flips between 0x25 (RGBA8) and 0x3d (RGB10A2) along with it. Possibly related to #2038 (Native HDR flicker where one window image stays RGBA8), but in my case the picture is constantly washed out rather than flickering. [hookshot_log.1.txt](https://github.com/user-attachments/files/34671679/hookshot_log.1.txt) ### Screenshots or video Screenshot 1 (gameplay): washed-out picture with Native HDR. Screenshot 2 (settings): Graphics menu showing HDR set to Native. <img width="3840" height="2160" alt="1" src="https://github.com/user-attachments/assets/f64e2020-b450-44f9-83c3-6f5f6d546fe0" /> <img width="3840" height="2160" alt="2" src="https://github.com/user-attachments/assets/a5f7ce08-30b9-4128-8e76-8852e41628ec" /> ### Before you send it - [x] I'm on the newest release, or the problem is still there on it. - [x] I searched the open issues for this problem. - [x] I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.
PiPoLiNiO commented 2026-11-11 08:59:50 +00:00 (Migrated from github.com)

I confirm. The native looks like washed, and often when turned on, it starts to flicker.

I confirm. The native looks like washed, and often when turned on, it starts to flicker.
NotRexed commented 2026-11-11 21:25:46 +00:00 (Migrated from github.com)

Thanks for the report. Reports of the same problem are now collected in #2502, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2502 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.

Thanks for the report. Reports of the same problem are now collected in #2502, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2502 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.
Commenting is not possible because the repository is archived.
No milestone
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Hookshot#2162
No description provided.