@super600 said:
@sancho_panzer said:
They said this hardware was specced for parity, but with dropped resolutions. If it's confirmed this is because of the S (has it been, though?), something's going to have to give.
That dev explains at the end of that video why spiltscreen is not in the new forza at launch. He says it's because of the graphical features they are pushing and the new rendering engine. If I am correct it's the opposite issue of BG3 where the features and the engine they are using are making spiltscreen difficult to implement on likely both the S/X. The issue with BG3 was that it was rendering the world multiple times in spiltscreen and people could go whereever they wanted. In forza you don't have to deal with that since all players would likely be racing on a track where their isn't a huge distance between everyone.
TLDR: They probably didn't have enough time to focus on these features while developing the new Forza.
Thanks for the response
@super600
I've not watched the video, but, as far as Forza is concerned, that sounds plausible. i.e. it's a delay because they were simply behind schedule, same as with Sony's latest hints about their upcoming batch of first party delays. Platform holders have a habit of getting unreasonably optimistic about their own products' dev cycles till crunch time.
For Baldur's Gate 3, though, this should be a bit more worrying to MS. It's hard to swallow the suggestion PlayStation's architecture is so radically different that PS5 should represent an absolute hardware cutoff point. I mean it's not like BG3 is barely running in split-screen on PS5, right? It's doing so comfortably, from what I've understood.
Now, I could buy the idea that certain design decisions Larian made might lie on a development fault line between X and PS5, but then there's the question of why MS has allowed themselves to get shut out of the dialogue like that again. Is it a question of inferior development tools? Maybe they're just not "liaising with devs" appropriately? If parity is not a major issue at a hardware level, and it boils down to either of those explanations, then there's still potentially a way to resolve the problems they've been having the last decade.
If it's not about developer-platform relations though, MS needs to think hard about their parity clause for S. If they're insistent, there are strategies they could mitigate the issue with, but a pretty-on-paper Activision acquisition isn't going to do that alone.
Log in to comment