I suppose, but all xgs titles on the switch have been identical ports so far and I don't think that will change.
I'd love to play Halo on the go, but unless it comes in a full package like MCC I can't see it happening. Would love to be wrong tho! I'd finally get some folks of mine to play...
They already switched up the release schedule on Steam/PC - so they will adapt if necessary. I dont see them using 343i ressources on a Switch port when they have to prepare for a massive current/next gen Halo.
It's more than just space, too. We're at 11 game engines + UE4 for Reach customization.
Man don't remind me, we should already have Reach on PC ya know. I'd like to see it run without screen tearing for once lol (at least Xbox bc fixes this problem but the framerate can still be a bit butt).
You can't play a game because of an ad campaign involving a soft drink and chips?
A direct port would be a mess. It would depend on how is handled (individual releases, ports of the 360 versions with the 360 assets, etc.)
And there you go, as good as confirmed.
I agree with this. It may not be one release that is called the MCC, but I think all of the games in the MCC will hit the system and be purchaseable separately -- although maybe not simultaneously, effectively being the same thing. It's basically what they're doing with MCC on PC anyway.
I wouldn't call that a monkey's paw since RTS is very underrepresented on Switch
I wouldn't mind one way or the other. I haven't played halo wars since the original release but I think it was quite good. I severely doubt we'll see the MCC though.
They don't run through BC on Xbox One, these are native ports
Yeah - Minecraft Dungeon should be a big one on Switch as well. Game looks really good.
While there's no disputing that they said this (well, they said specifically that adding Reach and the new menu was pushing it over, but semantics), I've seen nobody yet state why exactly this limitation exists and exactly what legacy issue is causing it. Reach alone won't be using all 5GB, it fit into 448MB after all. Remember that what 343 said is at the moment that's the problem they have. They will of course fix this problem (I doubt they would have mentioned it if they didn't already have possible solutions penned), and the solution to that could very well be the stepping stone to allowing MCC as a whole to run with a more limited memory landscape. Not to mention the savings you'd make by default of reducing the VRAM footprint with lower resolution textures and such, or even just cutting back on OS dependent resources.
