MoltenVK silently fails when loading vulkan versions greater than 1.2 and using dynamic rendering without explicitly requesting the extension

[9291Sam]

As noted here in my comment on this issue.
#1810 (comment)

MoltenVK will fail with a very tricky to debug segmentaion fault when using dynamic rendering and specifying the application's API version as greater than 1.2. I think that this should be an assertion failure to make this easier to debug for others in the future as when requesting 1.3, one would expect that dynamic rendering would just work.

[dboyan]

Not sure if it counts as a bug in a strict sense. First, MoltenVK doesn't support vulkan 1.3 yet (due to the lack of fully functional VK_KHR_maintenance4 implementation as of now), so requesting version 1.3 is not quite valid in the first place. At the same time, vulkan drivers have no obligation to validate API calls.

With current moltenvk, the only valid way to get dynamic rendering is to request vulkan <= 1.2 and enable the extension. Once version 1.3 is there (hopefully in the near future), one can do it by enabling version 1.3 directly, and at that time, things should properly work (otherwise, it would be considered a legitimate bug).

[cdavis5e]

Vulkan 1.3 is coming soon, but until then, you won't be able to create a 1.3 device with MoltenVK.