Difference with SpecialK ?

[Foul-Tarnished]

SpecialK can also add HDR to DirectX games, even HDR10 with 16bpc depth etc
You can also tweak the HDR settings like nits etc, and it has already made presets and tools to calibrate it to your monitor/TV

[clshortfuse]

SpecialK can only upgrade textures to output from 8bit to 10bit or 16bit. It doesn't modify shaders. If a game has tonemapping or clamping from shaders (most games in my experience) SpecialK is only going to change the 8bit SDR image to 10bit or 16bit SDR.

After that SpecialK does apply some AutoHDR processing on the final image. But that doesn't mean it will actually create new detail. That's just stretching to peak.

For example, what you get from just upgrading textures (16bit SDR) versus actually modifying the tonemapper for HDR:

[Foul-Tarnished]

Apparently that's not taking into account sk's pipeline remastering for d3d11 games

A screenshot from SK itself with "HDR retrofit" settings tweaked would be a better way to compare them

[clshortfuse]

Apparently that's not taking into account sk's pipeline remastering for d3d11 games

What do you mean "apparently"? I addressed that in the very first sentence.

SpecialK can only upgrade textures to output from 8bit to 10bit or 16bit. It doesn't modify shaders.

RenoDX does the same "retrofitting". But that won't stop shaders from capping to SDR.

[Foul-Tarnished]

Your screenshots are not accueate The part about textures is not accurate Le mer. 6 nov. 2024 à 19:03, Carlos Lopez ***@***.***> a écrit :

…

Apparently that's not taking into account sk's pipeline remastering for d3d11 games What do you mean "apparently"? I addressed that in the very first sentence. SpecialK can only upgrade textures to output from 8bit to 10bit or 16bit. It doesn't modify shaders. RenoDX does the same "retrofitting". But that won't stop shaders from capping to SDR. — Reply to this email directly, view it on GitHub <#53 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZVYVBUVDFFRKVUXWM63HOTZ7JKX5AVCNFSM6AAAAABP27RJBCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJWHE2TOMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[clshortfuse]

Name what is not accurate

[Foul-Tarnished]

Name what is not accurate

[clshortfuse]

And SK doesnt upgrade textures at all

Here's SK hooking into the function D3D11Dev_CreateTexture2DCore_Impl:

https://github.com/SpecialKO/SpecialK/blob/d446335a24e56f331d947c765fd4e3816cb0278e/src/render/d3d11/d3d11.cpp#L5465

And here is SK taking that texture, comparing it to the swapchain size and upgrading it to RGBA16:

auto hdr_fmt_override =
          (config.render.hdr.enable_32bpc) ? DXGI_FORMAT_R32G32B32A32_FLOAT
                                           : DXGI_FORMAT_R16G16B16A16_FLOAT;

 if ( ( ( pDesc->Width  == swapDesc.BufferDesc.Width    &&
                             pDesc->Height == swapDesc.BufferDesc.Height ) && (! bUpgradeNativeTargetsToFP) ) ||
                             config.render.hdr.remaster_8bpc_as_unorm )
                    {
                      hdr_fmt_override = DXGI_FORMAT_R16G16B16A16_UNORM;
                    }
                  }

I don't know what Kal is talking about. It's taking textures and upgrading them. The term "upgrade" is their code, not mine.

Here's RenoDX hooking into texture creation, checking against a custom target (default is swapchain size), and then upgrading against custom format (default RGBA16F)

renodx/src/mods/swapchain.hpp

Line 421 in 781bcc1

static bool OnCreateResource(

It's the exact same process. I also don't know why Kal says it's not upgrading texture when that's literally the name of the function: D3D11Dev_CreateTexture2DCore_Impl. Render Targets can be varying resources and the resources that SK is upgrading are Texture2D.

https://learn.microsoft.com/en-us/windows/win32/direct3d10/d3d10-graphics-programming-guide-resources-creating-textures#rendering-to-a-texture

So, again, second time. Name what is not accurate.