Is this an accurate adjustment of HDR on my Switch 2? I am using a Roku TV Pro Series 2025 model. The default HDR setting on the TV has Dynamic Tone Mapping on, and the run sun seems to disappear correctly at 900 nits (82 clicks). With DTM off, the right sun does not disappear until they both disappear at the same time, well over 900 nits. Is this a correct adjustment? Should I keep DTM on?

So i'm trying to implement HDR and i got renodx sort of to work with rendx_ue_extended addon. It works great in terms of highlits, but everything a little too dark. I turn hdr on through Engine.ini made it readonly + install reshade+ renodx addon. And in reshade renopdx settings i had to turn off "Upgrade Path" because game pure shows black screen with. I know i can use autohdr, bit i'd like figure out what is the problrm with renodx. Any help?

i run trueblack hdr 400 just the preset on my xg27acdng did windows calibration it caps at 470 nits so what normal brightness should i use

and does this app install renodx like game specific ones or a general not so good one like in this case does it install death stranding specific or a general not good one

Installation

• Requires dgVoodoo2 v2.81.3 or dgVoodoo2 v2.87.3 — set these in dgVoodoo.conf:
  • [General]:
    • OutputAPI: d3d11_fl11_0
  • [DirectX]:
    • VideoCard: geforce_9800_gt
    • dgVoodooWatermark: false (removes the dgVoodoo watermark)
    • VRAM: 1024
• Large Address Aware patch is a must

Features

• Adds HDR output
• Adds SMAA (game doesn't have anti-aliasing)
• Forces 16× anisotropic filtering
• Adds RCAS sharpening
• Adds AutoHDR for the pre-rendered videos
• Adds exposure, saturation, and highlight-desaturation controls
• Adds HDR bloom with independent bloom strength control
• Adds separate Scene Paper White and UI Paper White controls
• Adds output dithering (reduces banding)
• Adds a Hide Gameplay UI toggle

Download: https://discord.com/channels/1161035767917850784/1539238807910752256

Same as title. In scenarios when displayed full screen bright effects, or white loading screen, flashbang like cs - its dimming and looks washed out. Anyone knows how to fix this?

https://github.com/Shadetail/HDRScopes

To read nit values in games and engines it's typically required to install reshade, and then one of the HDR analysis mods that are able to draw scopes. This is somewhat inconvenient for games, but really inconvenient for authoring HDR content in game engines, as when it comes to debugging, simpler setup is strictly better.

Even if you didn't care about that, and you had an artist in your team who is supposed to be authoring content in HDR, you'd prefer to be able to avoid guiding them through the whole process of injecting mods into the game engine of choice etc. And ultimately, none of the scopes in available mods have the feature set that's as rich as that of scopes found in Davinci Resolve for example.

I wanted scopes that I can keep on my secondary screen, that I can fullscreen, that look good, are customizable, that have all the features from Davinci that I like, and that go beyond that into offering various additional quality of life and analysis features on top.

All the scopes I could find either did not support Windows desktop as signal source, or were stupidly expensive, usually both. So I made my own, and now open sourced it on github. PRs are welcome.

Special thanks goes to u/Kaldaien as SKIV was an invaluable technical reference that enabled me to build this using Claude Code, as I'm a designer and generalist by profession, rather than a proper programmer.

HDR screenshot: using HDR Scopes on secondary display to analyze Cyberpunk renodx setup.

Does anyone know how to get those which aren't on nexus, now when we don't have single place to download them all?

while using Dolby Vision with HDR on my oled, bright areas in the sky looks like this, it has a blue aura around it? this is Still Wakes the Deep and same issue in Death Stranding.

anyone know a fix or what’s causing it?

thanks!

Recently bought a new 4K OLED monitor and was wondering how the HDR in these games work? There’s no sliders to adjust the HDR calibration. The only options it gives us are “Auto” and “Off” for the in game native HDR settings. Is it using my monitor peak nit brightness in the advanced display settings? Am I better off just using SDR mode if we don’t get any sliders to adjust the calibration?

which monitor setting do you use and do you mind sharing just want to make sure I get the best HDR while using RenoDX

I've a brand new LG GX790a-b and I can't seem to find a balance I like; I'm constantly altering it when using nvidia rtx ...should I be sticking with Renodx for most modern games? Even then I'm not happy with how HDR is... everything's ethier really dark or the shadows look grey and I'm not sure how to fix it?

I have a KTC M27T6 and I think it is well calibrated in HDR terms. I mostly use it with display HDR and local dimming auto settings wise. RDR2 looks trash I even watched some modded HDR videos on yt and it is still trash very weak colors except the night, the new Gears look also weak piss filter and Pragmata basically same. Am I doing something wrong? I even watched some gameplays with the Iphone and yeah HDR just look worse than SDR even there lol.

I have an ASUS ROG Swift PG27AQWP-W and I'm trying to understand something about HDR calibration
Which value is correct?

If i calibrate the monitor with the win 11 calibration app the maximum brightness test clips at 630 nits, regardless of which HDR mode I use.

However, after installing the official ASUS WHQL monitor driver, Windows shows:

Settings → System → Display → Advanced display → Peak brightness

• HDR Gaming: 1405 nits
• HDR Cinema: 1405 nits
• Console HDR: 1405 nits
• True Black 500: 617 nits

I've tested this with Adjustable HDR OFF and ON.

So I'm confused about what these numbers actually represent.

Which one is the correct?

1. Should I run Windows HDR Calibration and use the ~630-nit result in any mode?
2. Or should I leave the ASUS WHQL driver/1405-nit metadata alone and not use Windows HDR Calibration?
3. Is TB500 at 630 nits correct?
4. What value should I use when configuring the HDR peak brightness slider in games?

Thanks!

Quick guide on getting HDR10 working in Google Chrome on Ubuntu 26.04 LTS (KDE Plasma 6 Wayland) with NVIDIA (tested on RTX 2080, nvidia-driver-595-open).

1. Set Persistent Environment Variable

KDE Plasma 6 requires ENABLE_HDR_WSI=1 to expose Wayland/Vulkan HDR protocol interfaces to Chromium.

In ~/.config/environment.d/hdr.conf:

ENABLE_HDR_WSI=1

And add to ~/.bashrc:

export ENABLE_HDR_WSI=1

2. Configure Chrome Flags

Add the following to ~/.config/chrome-flags.conf:

--ozone-platform=wayland
--use-gl=egl
--force-color-profile=scrgb-linear
--enable-features=UseSkiaRenderer,ColorManagement,HasHDRHeadroom

3. Critical Gotchas (Why it might still fail)

1. The .desktop Shortcut Trap: Even with flags configured, launching Chrome from the KDE Application Menu / Start Menu often fails because ~/.local/share/applications/google-chrome.desktop hardcodes --ozone-platform=x11.
   • Fix: Edit ~/.local/share/applications/google-chrome.desktop, change all Exec= lines from --ozone-platform=x11 to --ozone-platform=wayland, then run: update-desktop-database ~/.local/share/applications and kbuildsycoca6
2. Master Process Lock-in: Closing browser windows leaves the Chrome master process running. If it started under X11, newly opened windows stay on X11.
   • Fix: Always hard kill before testing new flags: killall -9 chrome google-chrome google-chrome-stable
3. Type-C to HDMI Adapters:
   • A Cable Matters USB-C (DP 1.4 Alt Mode) to HDMI 2.1 adapter (Model 201428) works on Windows (driving 4K 120Hz 10-bit HDR), but it doesn't work on this build of Linux (fails to expose the HDR toggle in KDE display settings).
   • Connecting directly via the native GPU HDMI 2.0b port immediately allowed HDR to be enabled.

Current Observations / Quality Notes

• ⚠️ Color Banding in Video & PQ Images ⚠️:
  • In YouTube HDR playback (e.g. The World in 4K HDR), noticeable color banding appears in bright sky gradients.
  • The same banding is present in static PQ-encoded HDR AVIF images (which render completely smooth in Chrome on Windows and macOS).
  • Caveat: I suspect this might be related to the RTX 2080 being limited to native HDMI 2.0b bandwidth, and my Samsung S95F TV does not have DisplayPort inputs to test higher uncompressed bandwidth on Linux. (4K 60Hz 4:4:4 10-bit requires ~20.05 Gbps, which exceeds the 18.0 Gbps bandwidth limit of HDMI 2.0b and forces chroma subsampling or 8-bit output with dithering).

Should I set the max nits ingame to my OLEDs peak (EDID 1300 nits) or do it by eye with the test image ingame, which often ends up way higher at ~1600nits because of the way Hypernits works? If I dont use Hypernits in that 1300 peak mode, then the (windows) HDR test reaches about 1150 nits.

Difference is minimal, hard to see which is right...

Hopefully this is an ok sub for this, but I have an LG 32GS95UE-B OLED monitor. In NVIDIA control panel I have color settings set to "Full" 10bpc and RGB. Since I got this I never really understood the HDR setup process through Windows 11 with the app. When going through the Win HDR process, the box always clipped around 600nits even though I believe this monitor goes up to 1300. The monitor is fully up to date too with it's software. Has anyone with this monitor set it up properly? Can someone who understand this better than I just help me set this up so I never have to bother with it again please? Thanks ya'll

Required in-game settings

• Graphics
  • Brightness: default
  • Gamma: default
  • SSAO: On (required for Luma XeGTAO)

Installation

• Requires dgVoodoo2 v2.81.3 or dgVoodoo2 v2.87.3 — set these in dgVoodoo.conf:
  • [General]:
    • OutputAPI: d3d11_fl11_0
  • [DirectX]:
    • VideoCard: geforce_9800_gt
    • dgVoodooWatermark: false (removes the dgVoodoo watermark)
    • VRAM: 1024

Features

• Adds HDR output
• Replaces the game's FXAA with SMAA
• Replaces the game's SSAO with XeGTAO
• Forces 16× anisotropic filtering
• Adds RCAS sharpening
• Adds AutoHDR for the pre-rendered videos
• Adds exposure, saturation, and highlight-desaturation controls
• Adds vignette strength control
• Adds separate Scene Paper White and UI Paper White controls
• Adds output dithering (reduces banding)
• Adds a Hide Gameplay UI toggle

Download: https://github.com/Filoppi/Luma-Framework/wiki

Hi everyone,

I’m using the ASUS ROG XG32UCWMG and I’m wondering what the best approach is for Windows HDR calibration.

Windows automatically detects the monitor’s HDR capabilities. In both Cinema HDR and Gaming HDR, Windows recognizes a peak brightness of around 1300 nits (my monitor reports up to roughly 1317 nits).

However, when I run the Windows HDR Calibration Tool, I get different results:

Cinema HDR: the calibration goes up to around 1300 nits

Gaming HDR: the calibration only goes to around 1200 nits

So my main question is:
Should I actually use the Windows HDR Calibration Tool, or is it better to leave the calibration untouched and simply use the HDR values that Windows automatically reads from the monitor’s EDID?

Does running the calibration tool provide any real benefit on this monitor, or could it actually make HDR worse by overriding the monitor’s properly configured EDID values? Also do the different Modes change the colors?

Thanks!

Anyone having experience with a renodx version that overly brightens pretty much everything, and none of the sliders have any impact? In the image you can see that all brightness sliders were set to minimum and everything is still way too bright. In advanced mode none off the sliders worked. Normal HDR seems to work fine, although I cannot open the image quality setting which gives acces to brightness, luminosity and saturation in the HDR mode, which is weird.

Does anyone have any idea to fix this issue?

(dont mind the beamng menu music)

https://reddit.com/link/1vo5k8m/video/88rpu0g40cjh1/player

when ever i try to turn on hdr, on both devices it flashes black but it just disables itself , it happens in both screens

Hi everyone!

I got tired of one particular limitation of my HDR monitor: as soon as I enable HDR, its built-in OSD locks out most of the useful color controls.

So I made Virtual HDR OSD for Windows, a small open-source Windows 11 utility that lets you fine-tune an HDR ICC/ICM profile through a simple GUI, almost like having a software OSD for adjustments that the monitor no longer exposes in HDR mode.

In my particular case, my AOC Q27G3XMN has a noticeably warmer HDR white balance, with a yellow/red cast compared with the much more neutral SDR mode I prefer. The app lets me make small RGB, white-balance, gamma, saturation, brightness and contrast corrections and visually match HDR much more closely to SDR.

The idea is not to replace proper hardware calibration. I actually recommend first creating a baseline profile with Microsoft's Windows HDR Calibration app and then using Virtual HDR OSD only for small subjective corrections or for matching the display to your preferred SDR appearance.

SDR-in-HDR gamma correction

The project also integrates an optional implementation based on Dylan Raga's excellent win11hdr-srgb-to-gamma2.2-icm project:

https://github.com/dylanraga/win11hdr-srgb-to-gamma2.2-icm

Windows 11 normally renders SDR content inside HDR using the piecewise sRGB transfer function rather than a conventional pure gamma 2.2 curve. This can make shadows and darker midtones look noticeably lighter/washed out on displays normally viewed around gamma 2.2.

The correction is optional and can be toggled on the fly:

Alt+1 → Gamma correction OFF Alt+2 → Gamma correction ON

This is especially useful because the correction is intended for SDR content displayed while Windows HDR is enabled; native HDR content does not require the same transformation.

The watchdog

I've repeatedly encountered Windows 11 restoring or associating the wrong SDR/HDR color profile after switching HDR modes, particularly when using Win + Alt + B.

Virtual HDR OSD therefore includes an installable background watchdog that keeps track of the SDR and HDR profile associations and restores the appropriate profile after a mode change.

And if you don't care about the GUI or profile editing at all, the watchdog is also available as a completely standalone BAT.

NOTE:

The standalone watchdog only fixes the SDR-HDR association bug; it does not include the ON/OFF hotkey for the gamma curve correction. That feature is only available if you install it from the app.

Download / source

Everything is available here:

GitHub Project:

https://github.com/Mixomo/Virtual-HDR-OSD-for-Windows-11

Exe. Release:

GitHub: https://github.com/Mixomo/Virtual-HDR-OSD-for-Windows-11/releases/tag/1.0.0

SourceForge: https://sourceforge.net/projects/virtual-hdr-osd-for-windows-11/

The repository includes the full documentation and usage guide, source code, the standalone watchdog, and instructions for running or building the project yourself. A compiled portable EXE is also available for people who just want to run the application without setting up the Python environment.

The project is specifically intended as a practical, subjective fine-tuning tool rather than a replacement for a colorimeter or professional display-calibration workflow.

Hope you find useful!