- cross-posted to:
- gaming@kbin.social
Larian has delayed the release of Baldur’s Gate 3, currently on pace to possibly be 2023’s Game of the Year, until they can figure out how to make split-screen work on Series S.
Larian has delayed the release of Baldur’s Gate 3, currently on pace to possibly be 2023’s Game of the Year, until they can figure out how to make split-screen work on Series S.
I still don’t really understand this. Local splitscreen on a game the size of baldurs gate does make sense to me as being a technical hurdle, obviously rendering the game world twice is extremely taxing.
I keep seeing complaints about other games also, lots off people seem to be blaming the Series S for Remnant 2s slow xbox patches.
The Series S is basically an X with a weaker GPU, how are games (that also release on PC) not scalable enough to run on the S at 1080p when they can run at 4k on the X? I’d love a technical answer, if I replace my 3080 with a 1060 I could run the game on my PC and a lower resolution/graphic settings. How is this different from the Series X/S? I’m not a programmer/developer and I’d really like if someone could explain too me why the Series S is a problem because from my view point it’s lazy developers with unoptimised games
If it was just a GPU difference, you’d be right it should be easy to just run it less pretty. But the memory limitations are the real issue. The X has 16 GB of memory and the S has 10 GB. And worse, the memory performance is drastically different. The X has 10 GB that runs at 560 GB/s and 6 that runs at 336 GB/s, where as the S has 8 GB at 224 GB/s and 2 GB at 56GB/s. (I did not miss a zero on the last value)
Holy crap that’s an absurd kneecapping with the RAM. No wonder they’re having parity issues
It has less RAM than the Xbox ONE X as well and is incapable of running backwards compatible games with Xbox One X enhancements.
https://www.videogameschronicle.com/news/xbox-series-s-likely-wont-be-able-to-run-xbox-one-x-content-its-claimed/
Holy shit I had no idea. The Xbox One X really is more powerful, at least in some regards, than a system that came out 3 years later.
Wow i did not realize that about the ram
Some phones have more RAM than a Series S? Wow.
They are usually more expensive too tbh.
I was unaware that the memory difference was so drastic. I was under the wrong assumption it was the same speed but less (as less is needed for 1080p)
Split screen might be difficult for Series S due to memory constraints. Keep in mind that all assets both players are seeing must be loaded in memory simultaneously. This includes textures, models and animations. These assets are normally not loaded into the memory unless they’re visible by the camera. This becomes problematic if there are two cameras facing different parts of the map at the same time. Then you potentially need to double the memory requirements, which the Series S might not have.
did you think of the possibility that even Larian’s low settings still can’t run on series S? Given the amount of assets I saw it’s actually quite possible that vram requirement are pretty high and that’s why PS5 have delay as well so they can figure out ways to consolidate textures used etc. Like they can’t even manage to let me stack rope or water bottle properly in inventory(maybe some asset id not cleaned up during development), so having excessive vram usage is fairly easy/common for content heavy games.
Today’s Digital Foundry video suggests that this is far from the issue. Even the highest texture settings fit comfortably in 6 GB. IIRC it was around 4,5 - and consoles typically go for high rather than ultra settings.
Xbox series S have 8GB for game, so while BG3 might consume around 4-5GB on PC, console with unified memory couldn’t afford this. All the other assets(model/animation/audio clips/massive amount of icons) needs to be loaded as well. With split screen, you can have one person tries to go into conversation (that streaming in high res texture/face models, etc) while the other one stay and still render the world with all the things their camera can move around with.
I went back and had a look. It’s between 2165MB and 3720 MB based on settings. Doesn’t really seem problematic on the low end.
I don’t know what to say other than maybe you should send Larian your resume and type “I am sure series S can be ported no issue, here is my numbers.” I am sure Larian would love to have simultaneous launch like PS5 and you can cut a really good deal if you can manage to pull that. BUT, you would have to pass the [Persuasion] check though, hope you have high cha to back it up. :)
Very funny. Just saying that textures don’t seem to be the issue. Any number of other things might be from rendering methods to whatever.
For one viewport!
The problem with Series S is split screen.
Also that’s 6GB of dedicated VRAM. Consoles have unified memory, so you need to fit the OS and the non-graphics memory in there too.
That’s only VRAM. You’re missing the other half.
It’s unified RAM on Xbox. And medium settings are 2165MB on PC.
To be clear, I’m not trying to attack Larian here. I think splitscreen is a much bigger technical hurdle than other games have to deal with and delaying it on the Xbox was the right idea. But, the PC versions minimum requirements is 4GB vram and recommended 8GB vram. The Series S has 10GB vram. I’m more annoyed by the anti Series S rhetoric going around about it holding all games back, because most games with a PC release scale no problem
What you forgot to consider is that the Xbox has to share the RAM with the VRAM. The game on PC has 8GB RAM and 4GB VRAM as minimum. That is 12GB of RAM. The Series S only has 10GB. Which is 2GB less than minimum.
You needs less RAM in total on a system with a unified memory architecture, like both Xbox consoles.
True but not 2GB less, the Xbox is also still running an OS albeit a slimer one. I’d guess the smaller OS saves at best 1GB of RAM.
I did not realise that the Series S shared it’s Ram and VRAM. That is something I had missed. Thank you
And with PC, there is only one view point at one time. You can have characters all over the map, but it only needs to render one at a time. Worst case it loads and unloads assets as you switch back and forth. With split screen console, gotta have both loaded at the same time.
It’s not baseless rhetoric when a dev team has literally called it out as a big tech hurdle.
What you’re not seeing or understanding:
The Xbox Seried S does not have 10GB VRAM it has 10GB VRAM/RAM that can be dynamically allocated to whatever the game needs.
Baldur’s Gate 3 needs 12GB combined VRAM/RAM at minimum. While the Xbox OS peobably doesn’t eat as much RAM as Windows does the difference is apparently not 2GB which leaves the Series S with not eniugh RAM to power the game.
As others mentioned for the Steamdeck Splitscreen was disabled, however that was likely done to save GPU performance, unlike the Series S the Steamdeck has enough RAM (16GB) to meet the minimum requirements.
See my other reply, 4gb beam is not the same requirement for series S cause consoles use unified memory.(also it only have 8GB for game)
https://www.thegamer.com/xbox-series-s-apparently-vram-issues/
It wasn’t delayed on the PS5; that was the original release plan. They moved the release UP for PC because they didn’t want to have to compete with Starfield’s release. Since that’s not coming out on PS5, they left the release date as is.
Right, I forgot about this, thanks for correction.
And significantly less RAM, which is probably the issue here.
The main difficulty with split screen is that you need to be able to fit everything you need to render the scene into RAM, twice. Let’s go through some cases:
Just rendering to a higher resolution still lets you get away with the same amount of RAM if you use low-res textures, or a moderate increase because you’re using high-res textures, but only in the foreground – all you need is enough GPU compute power to push the pixels.
If you’re rendering VR both camera perspectives are going to be nearly identical, looking at the same objects, so RAM use is nearly identical to a single camera. Your frame time targets are much stricter in VR, you have to have high and very regular fps or people are going to puke, but again that’s compute pressure, not memory pressure.
In the split-screen case all bets are off: When players are at opposite sides of the map there may be literally zero meshes and textures in common between those two areas and you need twice the RAM for twice the amount of camera views. Nothing in common is the worst case, yes, but it’s bound to happen, and not leave PR in a situation where they have to say “We degraded performance when players are far apart to promote an atmosphere of closeness and cooperation”.
The problem here is implied to be local co-op between X and S players?