You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recommend using assembly rather than HLSL for those - the HLSL decompiler will never be able to accurately decompile every shader due to some fundamental issues with the difference between DXBC and HLSL, so more effort has gone into making the disassembler + assembler support everything possible rather than making the decompiler support a few more esoteric types.
Alternatively remove the partial precision types - most implementations transparently replace them with 32bit types anyway so there is rarely any point to using them.
Oops, didn't mean to close the issue since it is a legit limitation of the decompiler, and perhaps some day it will be implemented, but don't hold your breath.
Files:
HLSLDecompiler_Test_min16f4.zip
Reproduction step
Issue description
Unknown data type: min16f4
the Corresponding instruction
mov o0.xyzw {min16f}, r0.xyzw {def32 as min16f}
The text was updated successfully, but these errors were encountered: