Direct3D feature levels discussion

That makes even more sense, because you have precedence.

edit: If you want to entertain that train of thought in the first place and do not dimiss it as conspiracy theory outright, which I would totally understand.

 

SM6.6 looks pretty interesting. Is this mainly about XBox Series, with forwards compatibility over time for PC?

 

@DmitryKo Could you add this to the starting post of this thread - just for convenience?

edit: Thx to the mod who did it

 

https://devblogs.microsoft.com/dire...the-release-of-the-dxbc-signer-nuget-package/

 

https://videocardz.com/press-release/3dmark-sampler-feedback-feature-test-is-now-available

 

Latest version of the D3D12CheckFeatureSupport tool has stopped reporting anything after SharedResourceCompatibilityTier : D3D12_SHARED_RESOURCE_COMPATIBILITY_TIER_0 (0) for some reason...

The output looks like this now:

Code:

Direct3D 12 feature checker (April 2021) by DmitryKo (x64)
https://forum.beyond3d.com/posts/1840641/

Windows 6.2 version 2009 (build 9200.1288 vb_release) x64

ADAPTER 0
"NVIDIA GeForce RTX 3080"
VEN_10DE, DEV_2206, SUBSYS_87AC1043, REV_A1
Dedicated video memory : 10078.0 MB (10567548928 bytes)
Total video memory : 42802.8 MB (44881985536 bytes)
Video driver version : 30.0.14.9613
WDDM version : KMT_DRIVERVERSION_WDDM_2_7 (2700)
Virtual memory model : GPUMMU
Hardware-accelerated scheduler : Enabled
GraphicsPreemptionGranularity : DXGI_GRAPHICS_PREEMPTION_PIXEL_BOUNDARY (3)
ComputePreemptionGranularity : DXGI_COMPUTE_PREEMPTION_DISPATCH_BOUNDARY (1)
Maximum feature level : D3D_FEATURE_LEVEL_12_1 (0xc100)
DoublePrecisionFloatShaderOps : 1
OutputMergerLogicOp : 1
MinPrecisionSupport : D3D12_SHADER_MIN_PRECISION_SUPPORT_16_BIT (2) (0b0000'0010)
TiledResourcesTier : D3D12_TILED_RESOURCES_TIER_3 (3)
ResourceBindingTier : D3D12_RESOURCE_BINDING_TIER_3 (3)
PSSpecifiedStencilRefSupported : 0
TypedUAVLoadAdditionalFormats : 1
ROVsSupported : 1
ConservativeRasterizationTier : D3D12_CONSERVATIVE_RASTERIZATION_TIER_3 (3)
StandardSwizzle64KBSupported : 0
CrossNodeSharingTier : D3D12_CROSS_NODE_SHARING_TIER_NOT_SUPPORTED (0)
CrossAdapterRowMajorTextureSupported : 0
VPAndRTArrayIndexFromAnyShaderFeedingRasterizerSupportedWithoutGSEmulation : 1
ResourceHeapTier : D3D12_RESOURCE_HEAP_TIER_2 (2)
MaxGPUVirtualAddressBitsPerResource : 40
MaxGPUVirtualAddressBitsPerProcess : 40
Adapter Node 0:     TileBasedRenderer: 0, UMA: 0, CacheCoherentUMA: 0DisplayableTexture.SharedResourceCompatibilityTier : D3D12_SHARED_RESOURCE_COMPATIBILITY_TIER_0 (0)

 

https://devblogs.microsoft.com/directx/first-agility-sdk-preview/
https://devblogs.microsoft.com/directx/d3d12-enhanced-barriers-preview/
https://devblogs.microsoft.com/directx/announcing-new-directx-12-feature-video-encoding/

 

Minimum video driver version for AMD hardware video encoding "In development – ETA Q2 ‘2022"

 

D3D12 "enhanced barriers" is virtually a clone of Vulkan's barrier model. Vulkan just got rid of render passes recently to be more like D3D12. Wow, what a turnaround ...

Basically the latest revisions between D3D12 and Vulkan aren't all that different anymore in terms of verbosity.

 

https://videocardz.com/press-releas...able-for-intel-and-nvidia-gpus-amd-in-q2-2022

 

revisioned barriers and more C++ like HLSL are bigger deal than a video encoding api upon d3d12 interfaces to be honest.

 

I agree, but 4 to 7 months for adding video encoding to a driver has surprised me.

 

C++ templates for shaders might not be as good of an idea as we once thought ...



A part of the reason why Tensorflow has ridiculously long build times is that they abuse templates and the Visual Studio team at Microsoft specifically tried to improve their case. Templates could potentially blow up shader compilation times ...

 

you can abuse for loops too if you are dumb enough :V

 

https://devblogs.microsoft.com/directx/in-the-works-hlsl-shader-model-6-7/

 

WDDM 3.1 incoming:


https://forums.guru3d.com/threads/windows-11-insider-nvidia-515-36.441826/

 

What's new with 3.1?

 

I don't think anything was disclosed so far.
Considering that it's coming around the time of Lovelace and RDNA3 launches it can be either another minor update or something more serious.

 

https://devblogs.microsoft.com/directx/updates-in-graphics-and-gaming/