What happened to -fvk-disable-depth-hint ? about directxshadercompiler HOT 3 CLOSED

@s-perron - this flag doesn't seem to have ever been supported in DXC. Maybe this was in some other fork that was distributed to users?

from directxshadercompiler.

I am unfamiliar with that option. I've looked for it in our internal documentation, and could not find any reference to it.

The only feature I believe I could map it to is the depth operand in OpTypeImage. If the value of that operand is 0 or 1, then it given an indication of whether or not that operand is used a a depth image; however that seem to be just be a hint because it is ignored in Vulkan. If a value of 2 is used, then there is no indication.

The DXC compiler always generates 2 anyway. I don't know if that was always the case. It is possible that this flag was added to "disable" the hint and cause the compiler to always output 2. That is the only behaviour now.

I would recommend removing the option from your build scripts, and look into any problem that may come up. If you find a problem with the compiler please report a new issue.

from directxshadercompiler.

Apologies, looks like O3DE uses a fork of DXC where they added that option to work around a mobile driver bug, instead of pushing it upstream...

from directxshadercompiler.