matthus 0 Share Posted Sunday at 05:45 PM (edited) Currently, Metal API support in game articles is only displayed if set to true. It should be displayed with a red cross if it set to false, to differentiate with games with unknown Metal support. Also it should be displayed as "Metal" and not "Metal support", like others API : D3D, OpenGL and Vulkan... To test this behavior, check Firewatch game article for game without Metal support and Hollow Knight game article for a game with Metal support. Edited Sunday at 05:49 PM by matthus I misclicked Tab and send the post half-written ;( Reply (Quote) Link to comment Share on other sites More sharing options...
radioheadsucks 0 Share Posted Monday at 06:57 PM On 4/12/2026 at 7:45 PM, matthus said: Currently, Metal API support in game articles is only displayed if set to true. It should be displayed with a red cross if it set to false, to differentiate with games with unknown Metal support. Also it should be displayed as "Metal" and not "Metal support", like others API : D3D, OpenGL and Vulkan... To test this behavior, check Firewatch game article for game without Metal support and Hollow Knight game article for a game with Metal support. wouldn't this be kind of pointless, though? just looking through the editing guide, graphic API support is listed based on what is available for a game, not on what isn't - so if what you're proposing was to be implemented, every single game that doesn't have, say, support for Vulkan would have to be explicitly edited in order to mention that they don't support Vulkan, which (in my opinion) is just more confusing than simply editing a game article in order to explicitly note Vulkan support for a game I will say though - changing the header name to simply "Metal" is a solid idea Reply (Quote) Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.