Abort on startup with a visible alert if required Vulkan features are missing

[Calinou]

See #70013 (comment).

Preview

[clayjohn]

Amazing! Does this work on mobile devices as well?

[Calinou]

Amazing! Does this work on mobile devices as well?

It should work as alert() seems to be implemented on Android and iOS, but I haven't tested.

[RedworkDE]

At least on Android alert() is not blocking #49969, so it won't actually be possible to read the dialog.

[lostminds]

At least on Android alert() is not blocking #49969, so it won't actually be possible to read the dialog.

I just tested and it's not blocking on iOS either.

OS.alert("This is our message","Alert!")
OS.crash("Crash message")

Causes a crash before the alert is visible on screen, so I assume it would be the same in this case of the alert about required vulkan features.

[lostminds]

Given the current situation that on mobile alert() isn't blocking, perhaps a compromise could be to simply not crash/exit on mobile. As I understand it that would leave it at a black screen once the user closes the alert message with the info, but that's fine and much better than the alternative (crash with no explanation) or current situation (black screen with no explanation).

[Calinou]

I removed the CRASH_NOW_MSG() call, so the previous indefinite black screen behavior is restored.

[clayjohn]

I think this still needs to return ERR_CANT_CREATE otherwise it will try to continue initializing Vulkan

[Calinou]

I think this still needs to return ERR_CANT_CREATE otherwise it will try to continue initializing Vulkan

Done 🙂

I've also modified the dialog to mention the GPU model name (useful for systems with multiple GPUs to choose from).

[clayjohn]

Tested locally and this seems to work fine now. The popup works as expected and then falls back to the normal "failed to initialize vulkan" error which points the user to using the compatibility renderer.

[akien-mga]

Thanks!