Feature Request: "Force Compatibility Rendering" via Project Manager

[mymstake]

The editor will soft-crash 100% of the time
Trying to open a Forward+ rendering mode project on a machine which doesn't support it may cause the editor to fail to load properly resulting in a blank window (in my case) due to Vulkan driver issues

Instead of leaving the user to figure out what's going on and how to fix it, new feature!

A:

• Add a "Force Compatibility Rendering" option to project manager
  • (in that drop-down under recovery mode or whatever would be perfect, see mock-up image)
• Show current rendering mode for each project.
  • (so users know a project will soft-crash before they open it)

B:
- A small back-end system which automatically detects a user trying to open a project for editing which their machine can't (due to rendering mode support.) (Automatic Fallback already exists, I slipped through a crack)

• Upon detection, display a confirmation dialog that notifies them of the issue, providing 3 options
  • Use Compatibility Rendering Mode
    • (enable compatibility fallback and proceed)
  • Ignore
    • (disable compatibility fallback and proceed)
  • Cancel
    • (return to project list without opening the project to edit)

[Calinou]

The editor will soft-crash 100% of the time trying to open a Forward+ rendering mode project on a machine which doesn't support it.

This is not supposed to happen since 4.4, as there's an automatic fallback implemented by godotengine/godot#97142. There are some known bugs in the fallback though, such as godotengine/godot#104435.

As a workaround, use --rendering-method gl_compatibility on the command line while specifying the path to a project.godot file on the CLI at the same time.

[mymstake]

AH, Indeed, and a bug was preventing me from realizing it. At least I assume it's a bug.
Turns out my GPU does support Vulkan, so I got it... but it must be stinky or something because Godot doesn't wanna be friends.


I think I'm running into some kind of Vulkan API limbo issue where my Vulkan does exist but there's an error linking up or something
godotengine/godot/issues/98848 This issue mentions Direct3D 12 and a device that doesn't support Vulkan, but nearer the bottom there's a mention about that API existing but not found bug.
I should probably open an issue and drop my vulkaninfo in there..

Anyways, I'd like to leave this open on behalf of the confirmation dialog to make the automatic fallback a user directed fallback.
I remember a post (during my search through those links) mentioning that automatic fallback could cause things in the project to break if they relied on certain aspects of Forward+.
Being warned and given the opportunity to back out before altering a project to compatibility was not "core" to the function of this feature proposal but the entire proposal made the compatibility fallback user directed to begin with.