So it turns out that the issue is HDR. Impossible to have the game in HDR Fullscreen with dgvoodoo2. Anyone has a solution ?

Maybe settings for dgvoodoocpl ? I need this program for Windows AutoHDR to trigger even for a DirectX9 game.

Or another program that as the same function (make a DirectX9 game render as Directx11, for AutoHDR to work).

I thought the issue was the Fullscreen part so i tried to force Borderless Fullscreen Window with GeDoSato but it didn't work.

BehelitSkull wrote on 2024-11-19, 22:22:

I have default settings in Dgvoodocpl i just chose my graphic card in the menu and put the max memory vram setting (4000 ?). I t […]
Show full quote

I have default settings in Dgvoodocpl i just chose my graphic card in the menu and put the max memory vram setting (4000 ?). I tried to put the //./DISPLAYX name instead of default but it always change.

For Sunshine i use Virtual Display Driver that is disabled by default in device manager, with scripts/commands that activate it when i start streaming (and that disable the laptop screen) and disable it when i stop streaming. There's also a vsync toggle program that stop vsync when the stream starts, nefcon, Playnite, Playnite Watcher, MultiMonitorTool, Sunshine Virtual Monitor. All come from Sunshine AIO.

When i stream the same game in Steam Link in fullscreen i don't have this issue, but for me i like Moonlight/Sunshine better with only the client screen active and better performance.

And all the games without dgvoodoo2 works with no problem.

Can anyone help me find the issue and which settings to use in dgvoodoocpl please ?

Hi!

So, AutoHDR works with dgVoodoo, but not with dgVoodoo + streaming through a virtual display driver?

BehelitSkull wrote on 2024-11-19, 22:22:

I have default settings in Dgvoodocpl i just chose my graphic card in the menu and put the max memory vram setting (4000 ?). I tried to put the //./DISPLAYX name instead of default but it always change.

dgVoodoo stores the amount of VRAM in 64 bit, so you can type "arbitrary" values into the input box. Or just edit the .conf file directly in a text editor.
The full screen outputs are not named in dgVoodoo, they are simply identified by an ordinal number, so you cannot use the //./DISPLAYX device name.
"1" is the first monitor attached to the selected gpu, and so on. "0" is either the primary or the first attached monitor.

You can also achieve fake fullscreen natively by dgVoodoo, you just need to set option GeneralExt\FullscreenAttributes = fake, either in the .conf file or in the Cpl.
Also, there is an option, GeneralExt\Colorspace, for "HDR" rendering. You can force a different physical color space output other than the game uses (which is almost always plain 32 bit ARGB:8888).
Say, if you set it to ARGB:16:16:16:16 then the swapchain itself will have this 16 bit per component format, so AutoHDR doesn't have to replace it in the background and the game framebuffer will also be rendered in 16 bit precision (with some overhead in performance).
I don't know if it helps though, I cannot test it now.

If it does not work then you should try the _dbg version of dgVoodoo and look into the output logs to see which output dgVoodoo is initialized on (because of the virtual display driver), if there are errors reported and things like that.
If nothing interesting there then you can install the needed part of Win SDK to enable the DX11 debug layer as a final resort, and have a look into the DX11 debug log (if you're interested in it, I can point you into a topic where somebody else did that).