Larian is having trouble fitting Baldur’s Gate III on the Xbox Series S, the lower-priced and lower-powered console in Microsoft’s ninth-generation lineup.
I was looking up more information on why there’s such an issue getting BG3 on Xbox, and found this article with a lot more detail on the topic.
EDIT: The issue isn’t graphics or frame rate; it’s memory. The article goes into detail.
I hope this leads game engine developers to improve their optimization skills. Chances are the technique(s) needed here have been around for decades.
And how would you recommend they optimize a game so they can render it twice in split screen, when the S only has 10 Gb of RAM? Because that’s the issue here.
It’s obviously impossible for me to recommend specifics without seeing their code and data. But a lot can be done in 10 GiB with some effort and clever resource management. They might have to make fundamental changes to their engine if they didn’t plan for such constraints ahead of time, so maybe it won’t happen for this game. But what they learn through this experience could benefit their future work.
We get it, you’re a huge xbox fan and you’re disappointed it doesn’t have a release date. But let’s be clear here: this is 100% on Microsoft. Larian has made it clear they aren’t happy with the level of quality of the game on the S (believe specifically for split-screen) and they are holding out on a release date until solutions can be found. That is 100% their right, and you better believe if they released with a shitty performing S version there would be tons of articles, tweets, threads, etc moaning and calling them out on it (instead of the universal praise it is currently receiving). If Microsoft really wants the game on their console sooner they have options: They can help Larian get the S version running properly by providing developers/knowledge/tools/etc, or they could allow for games to have exceptions for certain game features on X vs S.
If anything, Larian have gone above and beyond what most other larger AAA companies put out: Cross-play, cross-save, DRM free, and a huge open-world full of enough options and branching paths to put basically every other RPG to shame. It’s clear they want to deliver a great game that has everything possible they can put in it to please their customers. And part of that is not putting out a crappy version of the game. If you don’t like it, maybe take it up with Microsoft; or wait patiently and see if they can’t optimize and get things figured out once they game releases on the other platforms and they can spend more time focusing on the xbox platform.
There’s two views I see here from a software engineering perspective: multi-targeting devices with different specs can get really hard, and that modern development consumes resources in excess.
View 1: If you design a device that won’t catch up to modern expectations (limited, shared memory being the factor here), don’t expect to run all of the games. Some (or most) games will demand a certain level of resources. Microsoft either expected their status to swing their will upon the developers or were willing to help but just flopped on predicting what would be needed over the device lifetime. It’s a hard job, balancing developer need and cost. The hardware developers did their best. This comes down to
View 2: It’s an old coot viewpoint, but goddamn are modern computer programs are bloated pieces of mess. This is NOT an insult to the game developers, but it is to the OS and the engine developers as a whole. The entire programming industry has assumed that bigger more betterer computer always gonna come in a year or so. So now we have gigabytes of unused HQ textures in game downloads for no reason. Windows OS with Chrome takes gigabytes of RAM to display a webpage. We went from ultra strict data streaming to CPU rates for Crash Bandicoot to an NVME SSD shoveling half a terabyte a second when you want it in the Xbox Series X. This has left those who cannot afford strong PCs (note: most of the third world) and now consoles from playing the latest and greatest games. Developers leave them behind by grasping at the end of Moore’s Law. If BattleBit can produce good gameplay with 256 players on a raw potato, AAA game engines should try and appeal to everyone now.
No, you really don’t.
Please take your misguided rant elsewhere.
Iirc, Microsoft is actually trying to help them get it running on S. I wish I could remember where I heard that, but I’ve been reading and watching too much on the game recently to find it.
What they learned is that they don’t need Xbox to have one of the most successful games of the year.
Mate, you’re not John Carmack. It would be a ridiculous assumption to think their developers didn’t take a serious look into optimisation before deciding to ignore the xbox ecosystem for initial launch.
Mate, nobody has made that assumption. (And Carmack is not the only one who can see there’s probably room for improvement here.)
Thing is, it’s got 2Gb less than the One did. The S isn’t a good long-term option because it can’t even hold up memory-wise with the last gen console.
To be fair fully maxed out settings on PC It’s only using ~4GB for me? I was surprised but that seems to be how it is. I have 32GB and was using roughly half overall on the machine so plenty available.