When I had a leak like this, it was the back window seal that was compromised. I had tested the trunk seal to no effect, but it still got wet when it rained or car wash. Took it to a shop and they figured out it was the window…I would have never guessed that.
There already isn’t feature parity, because the S doesn’t support the same video resolution and framerates as an X. Anyone who bought an S thinking it was just as powerful as an X didn’t do their homework. And yeah, MS is partially no blame for not making the distinction more clear.
I’m an S owner, of multiple units, because the consoles were cheaper and most of all actually available to purchase. I knew going in it was a lighter console. For what my family plays, that’s perfectly fine. We’re more of an indie game or older game house, with very little time spent on AAA games. Having multiple cheaper consoles vs 1 expensive one gives us more gaming options, including multiplayer if we want to. For me, the S is fine even if feature parity goes away.
And as far as multiplayer goes, split screen coop in a AAA game is pretty much a rarity anyway. Devs aren’t incentivized to optimize their code. They’re pushed to hit deadlines and make it work. Split screen exposes all the cut corners and poor performance code, so a lot of game devs won’t even bother.
It’s the right choice, in this circumstance. Drop the split screen for the S to get the game out there. They can always circle back later and add it back in, if time and money allows. Other games have proven it’s not impossible, and I’m sure BG3 devs -could- do it. They just need the time and resources, and it’s not worth holding up the X release for that.