Just looked at that roadmap.[1] Good to know they are thinking about that.
I've discussed this in the context of Rust renderers. There are about four of them, and they all sit on top of Vulkan and export roughly similar APIs.
The API is roughly comparable to three.js - meshes, textures, materials, lights, shadows, and updating are supported.
They all get to the point where they can load static glTF scenes, and then the devs hit the hard concurrency problems and bail.
That's a much more comfortable level for users who need to get something done in 3D. Vulkan level belongs to people who write engines.
Getting off topic, though. This is not a retro problem. This is a current problem.
Further discussion on the Vulkan roadmap request for comments on Discord, here.[2]
I've discussed this in the context of Rust renderers. There are about four of them, and they all sit on top of Vulkan and export roughly similar APIs. The API is roughly comparable to three.js - meshes, textures, materials, lights, shadows, and updating are supported. They all get to the point where they can load static glTF scenes, and then the devs hit the hard concurrency problems and bail.
That's a much more comfortable level for users who need to get something done in 3D. Vulkan level belongs to people who write engines.
Getting off topic, though. This is not a retro problem. This is a current problem.
Further discussion on the Vulkan roadmap request for comments on Discord, here.[2]
[1] https://vulkan.org/user/pages/09.events/vulkanised-2025/T2-T...
[2] https://discord.com/channels/427551838099996672/115155677637...