Disable incompatible rendering methods in the project manager

[Calinou]

The project manager can now only create projects that use a rendering method compatible with the current platform. Rendering methods that are disabled at build-time are also grayed out.

While it is possible in theory to create a project using Forward+ on Android or HTML5 (thanks to the automatic fallback), it will look different once edited on a desktop platform.

Preview

Desktop	Mobile	Web

[Riteo]

Could this also handle rendering methods disabled at build-time? I recall there being some feature flag somewhere, but I guess that this could also work with just #ifdefs.

[Calinou]

Could this also handle rendering methods disabled at build-time? I recall there being some feature flag somewhere, but I guess that this could also work with just #ifdefs.

This could be done too using VULKAN_ENABLED and GLES3_ENABLED. (Can Forward+ and Mobile be toggled separately at build-time?)

[Riteo]

@Calinou

This could be done too using VULKAN_ENABLED and GLES3_ENABLED.

That's what I meant with "using #ifdefs".

Can Forward+ and Mobile be toggled separately at build-time?

From what I can tell, no. This seems to be solely a Vulkan vs GLES3 thing.

[Calinou]

That's what I meant with "using #ifdefs".

That's what I understood 🙂

I pushed an update that grays out rendering methods that were disabled at build-time. Example on desktop with opengl3=no SCons option (the Vulkan counterpart is vulkan=no):

[Calinou]

I've allowed selecting the Forward+ rendering method on mobile. Note that the descriptive text still says "Supports desktop platforms only" though.

[clayjohn]

Seems good to me

[akien-mga]

Thanks!