Vulkan is designed to be closer to the metal than something like DirectX 11 or OpenGL, which makes the API more explicit and difficult to use. This means it requires a great deal more care to use properly. And to complicate matters more, subtle bugs that are very difficult to debug are very easy to introduce.
But, this applies mostly to devs who build their own tech. Most of them these days are just using 3rd party engines like Unity or Unreal, so it comes down to whether or not the person making the game decides to check the box to use Vulkan and just how good those render backends are. Engine developers of 3rd party tech have to build their stuff to be as generic as possible. That’s likely gonna add a lot of bloat that might not be fully optimized for every game developer’s use case.
TLDR: It’s tough and time consuming for someone writing it themselves. And for the ones who aren’t, they’re having to place a lot of trust in a renderer that is probably a black box and might be buggy/slow.
thejevans@lemmy.ml 5 days ago
It’s becoming more common, but it mostly comes down to available tooling. At this point all three of the big game engines have a Vulkan backend available, but that’s a fairly recent development. And if a developer isn’t using a game engine, writing their own openGL renderer is easy, and writing a Vulkan renderer is a nightmare.
dormedas@lemmy.dormedas.com 5 days ago
Also a lot of old proprietary game engines were written either specifically for DirectX or additionally for DirectX because in the olden times it was the most advanced and compatible rendering software.
Then, those developers move forward in time to work on other engines and focus primarily on DirectX because it’s still good, compatible, and it’s what they know best. OpenGL languished and it took a while for Vulkan to come out, catch up, and standardize their API.