vsgcompute issues with MoltenVK.. about vsgexamples

[robertosfield]

Hi Oscar, I don't have macOS system to test against so have to rely on the community for this. Could you run vsgcompute with the Vulkan debug layer enabled in MoltenVK supports it. Run with : vsgcompute -d Another step would be to run with the Vulkan api layer : vsgcompute -d -a It might be that no errors are produced as I everything runs cleanly under Linux and reports no errors, and it'll be the same Vulkan API calls being used. It could be that it's a MoltenVK error in which passing this error on to the MoltenVK to them might be required. The vsgcompute example is inspired by the vullan_minimal_compute project hosted on github, if the above don't provide any leads then it would be worth checking if it runs OK with MoltenVK.

…

[robertosfield]

I've had a look over the shaders/shader.comp that generates the saders/comp.spv that is used by the vsgcompute example and the part that looks like it might relate to the warning is the use of specialization constants. It looks like there are others who've hit upon this issue too:

KhronosGroup/MoltenVK#231

Which just so happens to have a comment from @oscarbg on the Issue :-)

A workaround would be to avoid the use of specialization constants but it's valuable feature so I'm reluctant to apply to workaround for what could be a bug in MoltenVK.