According to Hans-Kristian Arntzen, a prominent open-source developer working on Vkd3d, a DirectX 12 to Vulkan translation layer, Starfield is not interacting properly with graphics card drivers.
I’m convinced large video game publishers make deals with graphics card manufacturers to force the end user to upgrade, the AMD and Nvidia deals are not for free access to new technology it’s for which ever bids the highest price to sell more cards. There is little progression in graphics fidelity since 2016. We used to take giant leaps and now we take small insignificant steps.
The problem is so severe, in fact, that the aforementioned translation layer had to be updated specifically to handle Starfield as an exception to the usual handling of the issue.
“I had to fix your shit in my shit because your shit was so fucked that it fucked my shit”
This is how games and drivers have been for decades.
There are huge teams at AMD and nVidia who’s job it is to fix shit game code in the drivers. That’s why (a) they’re massive and (b) you need new drivers all the time if you play new games.
I read an excellent post a while ago here, by Promit.
It’s interesting to see that in the 8 years since he wrote it, the SLI/Crossfire solution has simply been to completely abandon it, and that we still seem to be stuck in the same position for DX12. Your average game devs still have little idea how to get the best performance from the hardware, and hardware vendors are still patching things under the hood so they don’t look bad on benchmarks.
I’ll give a different perspective on what you said: dx12 basically moved half of the complexity that would normally be managed by a driver, to the game / engine dev, which already have too much stuff to do: making the game. The idea is that “the game dev knows best how to optimize for its specific usage” but in reality the game dev have no time to deal with hardware complexity and this is the result.
It’s poorly optimized code, and the comments from the top brass has been “lol your PC sux” when they can’t even get it running right on their own hardware.
It’s not the variations of PC that’s the issue, it’s a design and quality control issue. Direct X and Vulkan are the bread and butter of PC gaming. Microsoft developed direct X to establish a common graphics framework for Windows and Microsoft game studio still fucked up working with it.
This is just classic corpo shit, developing their own proprietary stuff when no one asked for it. Apple with Metal too. Then it falls on developers to write abstraction layers
I’m amazed that Bethesda has one of the premier game developers in their stead in id Software and didn’t bother to just use their shit. Instead they actively chased their staff away.
Bethesda the publisher and Bethesda the developer are different things.
The publishing arm seemed to know what they were doing, certainly enough for MS to buy them.
The developing arm is nothing if not consistent. You know what you’re getting into. An RPG, with lots of character build possibilities (even if a particular build overpowered enough for 90% of players to accidentally stumble across it, like Skyrim’s stealth archer build), a handful of memorable NPCs, no real character development, so-so performance, and a shitload of bugs.
If people are still buying them and still not enjoying them I don’t know what to say. It’s like watching Fast and Furious 10, and going “well that’s fucking dumb”.
I saw the ending of the last F&F by mistake (they sold us tickets for a movie that started an hour later), and let me tell you - that was fucking dumb.
I watched the first one many years ago, which appeared to just be Ocean’s 11, but for people who think putting blue lights under your car makes it go faster.
Then I watched F&F9 on Netflix the other month. I don’t remember any of the plot. At one point a car did a Tarzan rope swing.
Add comment