|
I wanted to pick up the Master Collection but the stories of these bugs are putting me off a bit
|
# ? May 30, 2020 22:01 |
|
|
# ? May 14, 2024 00:57 |
|
I've heard really lovely things about the audio quality of the ports as well and I don't think they've ever been fixed so far.
|
# ? May 30, 2020 22:06 |
|
I've played through the 3 games so far in co-op and we've had no real issues in a full playthrough. Especially worth it if you can get a cheap Game Pass Ultimate trial.
|
# ? May 30, 2020 22:16 |
|
Cardiovorax posted:I've heard really lovely things about the audio quality of the ports as well and I don't think they've ever been fixed so far. I think that the audio is only hosed up in Reach, not the other games. Apparently it's not an easy fix either, something about the audio codec got hosed up when porting Reach from the 360 and they're having to rebuild it or something. I dunno', I don't really understand this stuff. Apparently they've hired some former Bungie devs who worked on Reach's audio to fix it.
|
# ? May 30, 2020 22:17 |
KennyMan666 posted:PYF Game Glitch: so, the code causing the bug wasn't even in the same game does fit.
|
|
# ? May 31, 2020 00:29 |
|
Veotax posted:I think that the audio is only hosed up in Reach, not the other games. Codecs being discontinued or depreciated for whatever reason isn't uncommon so I'm not surprised. Digital formats need to be maintained and so they're hard to future proof.
|
# ? May 31, 2020 01:47 |
|
Lord Lambeth posted:I wanted to pick up the Master Collection but the stories of these bugs are putting me off a bit i *think* these are stories of the bugs for the console release of the collection which is over half a decade old, not the recent arrival of it on pc
|
# ? May 31, 2020 07:33 |
|
flatluigi posted:i *think* these are stories of the bugs for the console release of the collection which is over half a decade old, not the recent arrival of it on pc The dev story specifically points out that the bug only shows up in PC builds of the collection
|
# ? May 31, 2020 07:57 |
|
Veotax posted:I think that the audio is only hosed up in Reach, not the other games. it was unplayably bad for me
|
# ? May 31, 2020 08:05 |
|
flatluigi posted:i *think* these are stories of the bugs for the console release of the collection which is over half a decade old, not the recent arrival of it on pc Nope The worst of the MCC stuff is being/already is fixed up and I don't really blame 343 for it - MS is really breathing down their necks to get it all out there fast.
|
# ? May 31, 2020 08:56 |
|
Yeah, the pace of it all seems a bit extreme. For a reminder, we're up at 3 games ported so far the last ~6 months, with a 4th currently in testing. (You'd think they could have started doing this earlier to avoid this crunch, but I guess they just suddenly made the decision to slam everything onto PC around the time they decided Halo Infinite was going to roll out on PC as well.)
|
# ? May 31, 2020 16:19 |
|
Yeah, I wouldn't want to be the poor third-party studio that has to port Microsoft's flagship title while getting rushed to hell and back. I know they're a MS subsidiary, but that's not the same thing as actually being familiar with the stuff.
|
# ? May 31, 2020 16:30 |
|
SubNat posted:Yeah, the pace of it all seems a bit extreme. My guess: they knew this was coming but have found that bullshit crunches can be accomplished so it’s become part of the process in a philosophy of “gently caress the people doing the work.”
|
# ? May 31, 2020 17:12 |
|
And on top of it porting... 6? 7? different titles from 3 separate generations of console to pc. (Or in the case of 1, tweaking an existing, lovely pc port that had been turned into a 360 port, and porting it back to pc. Instead of doing a new, proper port of the original source.) It's Reach, 1, 2, 3, 3:ODST, 4, and 5 they're doing, right?
|
# ? May 31, 2020 17:20 |
|
SubNat posted:And on top of it porting... 6? 7? different titles from 3 separate generations of console to pc. The Master Chief Collection actually came out in 2014 on the Xbox One, so they're actually porting from that. From what I hear, the PS4 and Xbone aren't that far from PC's, since they're not using bizarre custom processors like the Cell or some bullshit, so I guess the porting process isn't as bad? Maybe? So for Halo 1 it's a port (og Xbox to PC) of a port (PC to 360) of a port (360 to Xbone) of a port (Xbone to PC). quote:It's Reach, 1, 2, 3, 3:ODST, 4, and 5 they're doing, right? Not Halo 5, the MCC came out before 5 on the Xbone so I can't imagine them adding it for the PC. Maybe they'll port it as a separate game after?
|
# ? May 31, 2020 18:25 |
|
The best part is that there's 11 total engines involved. Legacy UUI Halo: CE legacy engine Halo: CE remastered engine Halo 2: legacy engine Halo 2: remastered engine Halo 3 ODST Halo 4 Halo 2: Anniversary MP Halo: Reach UE4 (MCC menus)
|
# ? Jun 1, 2020 10:52 |
|
honestly I'm kind of shocked it works at all
|
# ? Jun 1, 2020 11:04 |
|
kirbysuperstar posted:The best part is that there's 11 total engines involved. How does this work exactly? The games have real time graphic switching so do they run two game engines simultaneously?
|
# ? Jun 1, 2020 14:59 |
|
Sininu posted:How does this work exactly? The games have real time graphic switching so do they run two game engines simultaneously? Yes. The legacy engine is responsible for the gameplay and the modern engine takes over when it's time to render a new frame. Pressing the switch button makes it invoke the legacy renderer instead. Both of those games targeted 64MB of RAM originally so there's more than enough on a modern system to load both asset collections at once. There's a bit more cleverness involved because there are places where changing the renderer actually changes the world geometry (there are hidden bonus areas in the modern mode) and it has to push you out of a space that no longer exists. Or at least that was the case in the standalone Halo 1 remake for Xbox 360, I don't know if it's in the MCC.
|
# ? Jun 1, 2020 15:06 |
|
haveblue posted:Both of those games targeted 64MB of RAM originally
|
# ? Jun 1, 2020 15:28 |
|
Halo was and is never that good. It was just the only decent FPS on a console for a while.
|
# ? Jun 1, 2020 20:51 |
|
dialhforhero posted:Halo was and is never that good. It was just the only decent FPS on a console for a while. It's one of the best co-op campaign games I've ever played.
|
# ? Jun 1, 2020 21:01 |
|
Halo is one of those games that spawned a genre. Doing it first and doing it best doesn't tend to go hand it hand.
|
# ? Jun 1, 2020 21:07 |
|
dialhforhero posted:Halo was and is never that good. It was just the only decent FPS on a console for a while. Multiplayer's still been fun as hell on MCC, especially now that we're in the Good Halos and not just stuck with Reach and CE. Also, maybe it's just my setup but the audio in Reach sounds fine? Positional audio sounds a bit janky but it's 100% playable and not distracting.
|
# ? Jun 1, 2020 21:20 |
|
LifeSunDeath posted:It's one of the best co-op campaign games I've ever played. I miss the era of halo, where we got Halo 3, Halo ODST and Reach then Halo 4 in fairly quick succession. Me and a buddy had so many epic moments in coop. One of the best coop experiences ever and I really miss that epic feeling of every mission being a big sandbox you could mess around in. GyverMac has a new favorite as of 23:34 on Jun 1, 2020 |
# ? Jun 1, 2020 23:31 |
|
I did like Halo when I played it on PC all those years ago. Halo 2 didn't really hook me when I tried it though and I'm not exactly sure why. Installing Halo 2 was a little dumb, though, as it didn't let me install it at first because I wasn't using Windows Vista... because I was already on Windows 7. Running the installer in compatibility mode solved that, but that didn't make it any less silly. Pretty sure there was nothing at all in Vista that was actually required for the game, Microsoft just made the game refuse to install on not-Vista since they wanted to push the OS.
|
# ? Jun 2, 2020 00:16 |
|
WeedlordGoku69 posted:Also, maybe it's just my setup but the audio in Reach sounds fine? Positional audio sounds a bit janky but it's 100% playable and not distracting. For me the audio shat itself during every cutscene but was mostly ok during gameplay (save for the mission in space where it was the worst). The audio just became a garbled unintelligible mess of digital fart noises and weird clipping and desync and repeating. It was great tho because it meant the game literally ended on a massive, long, drawn out fart.
|
# ? Jun 2, 2020 02:33 |
|
Jawnycat posted:It was great tho because it meant the game literally ended on a massive, long, drawn out fart. My opinion on the franchise in general
|
# ? Jun 2, 2020 02:39 |
|
dialhforhero posted:Halo was and is never that good. It was just the only decent FPS on a console for a while. So it's like Goldeneye
|
# ? Jun 2, 2020 17:00 |
|
It standardized console FPS controls which was neat because fuuuuck, every game had a different layout then.
|
# ? Jun 2, 2020 17:54 |
|
Croccers posted:It standardized console FPS controls which was neat because fuuuuck, every game had a different layout then. yeah except for these dinguses
|
# ? Jun 2, 2020 17:56 |
|
That's what the layout of the old SNES controllers was, so I guess we can blame that on Nintendo being stubborn and refusing to adjust to modern conventions because they did it first, harumph.
|
# ? Jun 2, 2020 18:06 |
|
Yeah, don't give Nintendo poo poo for the ABXY layout, it's been there forever. Do give them poo poo for switching to A being the confirm button and B being the back button somewhere along the way, though.
|
# ? Jun 2, 2020 18:10 |
|
Captain Hygiene posted:Yeah, don't give Nintendo poo poo for the ABXY layout, it's been there forever. Do give them poo poo for switching to A being the confirm button and B being the back button somewhere along the way, though. Wait, what? Nintendo set that as the standard though, I thought?
|
# ? Jun 2, 2020 18:11 |
|
I haven't used a real SNES controller in almost 30 years, but whenever I play an emulated game, that still is how it works, yes.
|
# ? Jun 2, 2020 18:13 |
|
ChaosArgate posted:Wait, what? Nintendo set that as the standard though, I thought? I dunno if it was completely standardized, but a lot of games used B as confirm back in the SNES days (when my brain got all these conventions set, so that part now feels more natural on Sony/Xbox menus than Switch).
|
# ? Jun 2, 2020 18:16 |
|
Nintendo and sony both have the same button layout, it is microsoft that is wrong.
|
# ? Jun 2, 2020 18:18 |
|
Primary button being the one closest to your thumb, and down, makes sense because people can't remember right/left very well in general, up down is better, so bottom button just works best for a primary.
|
# ? Jun 2, 2020 18:20 |
|
LifeSunDeath posted:Primary button being the one closest to your thumb, and down, makes sense because people can't remember right/left very well in general, up down is better, so bottom button just works best for a primary. It's O for Confirm and X for Cancel on the Playstation in international markets because that makes perfect sense, is in line with what Nintendo was already doing, and it was literally designed for that purpose, but Americans are so loving stupid that you are in fact correct for that one demographic, yes.
|
# ? Jun 2, 2020 18:23 |
|
|
# ? May 14, 2024 00:57 |
|
Circle for confirm and X for cancel is japanese only because they use those symbols for those exact things (Circle for "Correct" and X for "Wrong") and everywhere else, not just the US, it's the reverse.
|
# ? Jun 2, 2020 18:27 |