stride icon indicating copy to clipboard operation
stride copied to clipboard

Silk.NET D3D Discussion

Open ykafia opened this issue 3 years ago • 4 comments

So we can chat about the Direct3D Silk.NET switch here

related to PR #1123

ykafia avatar Nov 03 '21 12:11 ykafia

I'm at a point where we could use the latest specification for direct x (version is 1.6). Originally Stride is handling only 1.0 to 1.2. (that's the feature level values).

Should we keep the same feature levels, add 1.3 to 1.6 or just keep 1.6?

From what i can tell, this would add more preprocessor conditions in classes :

#if DIRECTX11_0
OutputDesc desc;
#elif DIRECTX11_1
OutputDesc1 desc;
#elif DIRECTX11_2
OutputDesc2 desc;
#elif DIRECTX11_3
OutputDesc3 desc;
// ...

ykafia avatar Nov 03 '21 12:11 ykafia

My opinion would be that we should support the latest D3D11 specification only (since win11 is rolling out and a lot of older hardware do not seem to be supported + only 5% of windows users are using win7) and focus on VK/DX12/OGL since the three of them have official support mesh and ray shaders. So i'd love to know any other opinions for confirmation

ykafia avatar Nov 03 '21 12:11 ykafia

Another thing I want to point out here is that there are no DX11 Era GPUs in support anymore from Nvidia with the exception of MAYBE a few GT cards. AMD has done much the same as well, I am fairly certain that there are no DX11 only cards either from that point. Pretty much every GPU that even the manufacturers support for gaming are DX12 capable and most were made when the DX12 spec was out, not to mention to support DX12 to begin with you only need FL0/1 and FL1/2

Redhacker1 avatar Nov 17 '21 14:11 Redhacker1

Great. Less historical baggage means faster R&D and promotion.

LeaFrock avatar Nov 18 '23 16:11 LeaFrock