this post was submitted on 11 Sep 2023
814 points (98.3% liked)
Games
32704 readers
1302 users here now
Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.
Weekly Threads:
Rules:
-
Submissions have to be related to games
-
No bigotry or harassment, be civil
-
No excessive self-promotion
-
Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts
-
Mark Spoilers and NSFW
-
No linking to piracy
More information about the community rules can be found here.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Do we know for sure that the Starfield devs weren't able to figure out the problems with performance? I find often with companies, the larger they are, the more bureaucracy there is, and the more prioritization of tickets becomes this huge deal, where you even end up having meetings about how to prioritize tickets etc.
I would be surprised if the devs didn't know what was wrong already, I think it's more likely that management and higherups doesn't care about them fixing it right now.
Game devs have many teams all with different jobs, for a big game like this you'd typically have multiple teams dedicated to optimization in different areas (and between them). The specific problem in this case was how the game was communicating with graphics drivers (among others), which for any graphics heavy game is very fundamental to performance optimization. The problems aren't even an after-the-fact optimization sort of thing that teams should have to identify and follow-up on, batching jobs is standard practice when interacting with GPUs whether or not there's a translation layer.
When the devs of a core translation API between two supported graphics drivers that are commonplace in the gaming ecosystem have to write code to specifically fix issues with your application you've done something fundamentally wrong.
A lot of posts like these also seem to imply that the open source community should somehow be less competent than these companies and are surprised that the open source community can fix these issues. But the open source community has a ton of very respectable and extremely smart developers, it shouldn't be any surprise really.
To be even more direct: there's a huge overlap between the circles of "works in software dev" and "contributes to open source projects".
I really try to do different things at home than work, but I've definitely contributed fixes to game mods (why do so many modders fail to do null checks before trying to interact with short lived shit like projectiles?) and open source software I've needed to do stuff.