If you've ever wondered why Baldur's Gate 3 allows you to choose between either Vulkan or DirectX 11, the answer is pretty simple - and it all comes down to none other than the Google Stadia, a now-failed cloud streaming service.
As reported by Video Gamer, Larian Studios' senior graphics programmer Wannes Vanderstappen describes why the team opted to use an API like Vulkan on PC when they needed "to support DirectX 12 for Xbox Series anyway" while speaking during a recent Graphics Programming Conference. Vanderstappen says there's "a simple answer for that," and it's "Stadia" - the discontinued cloud gaming service from Google that ended up shutting down last year.
"Baldur's Gate shipped in early access on PC and Google Stadia," explains Vanderstappen. "Google Stadia needed Vulkan, and because we shipped in early access, this also means a shorter release time frame." On the other hand, consoles had the luxury of being prepared for the RPG's full launch rather than its early access journey. That's not the only reason Larian made use of Vulkan, however, according to Vanderstappen.
"Vulkan had a bit wider hardware support than DirectX 12," continues the developer, "so we went for Vulkan as our main API." As for why Larian is still using DirectX 11 then - "things didn't really go according to plan." So, what was the problem? "BG3 was in full production already. The engine code team only moved to BG3 after pre-production happened because we were still working on the Definitive Edition of Original Sin 2."
Vanderstappen goes on: "So the whole company was actively using a DirectX 11 toolset, which means that we couldn't break anything while replacing DirectX 11 with Vulkan." The team attempted to gear things towards Direct X 12, as the dev states, but everything kept going wrong. Larian was in "a vicious cycle where nobody was using the Vulcan toolset, which means it wasn't really stress tested, which means that Vulcan was not stable."
The studio "didn't really find a good time to switch" toolsets, so "in the end," DirectX 11 was released alongside the game as a backup to Vulkan. Shipping the now-beloved RPG with an API like Vulkan was, as Vanderstappen puts it, admittedly "a bit scary" because "it's a bit more prone to crashes than DirectX 11" - hence why the latter tool came and served as a backup to the arguably less stable API, Vulkan.
