Release 1.14.
1 unresolved thread
1 unresolved thread
Merge request reports
Activity
59 ‘Texture2D<unorm float4> t;’ 60 - Parser support for ‘ByteAddressBuffer’ resources, as well as their 61 Load()/Load2()/Load3()/Load4() methods. 62 - Parser support for ‘RWByteAddressBuffer’ resources, as well as their 63 Store()/Store2()/Store3()/Store4() methods. 64 - Parser support for the ‘compile’ keyword, as well as the CompileShader() 65 and ConstructGSWithSO() intrinsic functions. Actual compilation of 66 embedded shaders is not implemented yet, but parser support is sufficient 67 for allowing compilation of HLSL sources containing this syntax to succeed 68 when targetting shader target profiles like ‘vs_5_0’ or ‘ps_5_0’. 69 - Initial support for tessellation shaders. Only the most trivial shaders 70 are supported in this release. Perhaps most notably, both ‘InputPatch’ and 71 ‘OutputPatch’ are not implemented yet. 72 73 - The new ‘fx’ source type can be used in combination with the ‘d3d-asm’ 74 target type to dissamble binary effects. changed this line in version 2 of the diff
+ - Instruction count reflection data for shader model 4+ target profiles. + This data is contained in the ‘STAT’ DXBC section, and can be queried with + the GetDesc() method of the ID3D11ShaderReflection and + ID3D12ShaderReflection interfaces.
The unfortunate thing about this is that our ID3D12ShaderReflection in vkd3d-utils does not support anything in the STAT block, unless I'm somehow mistaken.
The unfortunate thing about this is that our ID3D12ShaderReflection in vkd3d-utils does not support anything in the STAT block, unless I'm somehow mistaken.
Yeah. Ideally it would, but it's probably too late to implement that before the release. Suggestions for better wording are welcome of course; all I could come up myself made the text more tortured than it already is.
Please register or sign in to reply