That makes me wonder whether the input framerate remained at 30. That would explain your impression that it just got visually smoother without changing the feel
in MCC if you use a controller the input framerate is locked at 60, so maybe I’ve always been good at Halo
It’s fine if you don’t care but a console game can run at 60 FPS and an old computer can play the original PC release of Halo CE at 60 FPS.
Let me know if you ever need PC parts, I guess.
we just got done talking about how the original PC release is inferior and not everybody has space for a desktop anyway
I’m just glad to know that it wasn’t my imagination and that the Jackal shields on PC are indeed substantially uglier than they were on Xbox
all the lighting is so much better on the xbox… like look at the depth of shadow in the room on that screenshot! it just does not look like that on PC. just flat and blah
2 Likes
okay but again, i want to play halo on a 360 and i dont care about framerates. i have expressed i have no idea what an xbone is since ill never play the 343 version anymore. you can send me computer parts for talking about framerates though
1 Like
The post they replied to was in response to
which I wanted to express wasn’t really true - a seven year old console and a ten year old computer can both run these games at 60 FPS.
I did not engage in the qualitative argument because @BustedAstromech expressed my opinion with more substance than I could and there wasn’t anything to add
1 Like
anyway, gonna take this opportunity to plug my youtube cuz why not. this game really did look beautiful in 480p. look at all that beautiful elite blood on the ground… also i always thought energy swords looked best in CE on Xbox. also look at the ground textures in the hallway. beautiful game tbh!!
3 Likes
these screenshots also point out the other thing that’s been bothering me for fucking years, the HUD is so crisp on the xbox compared to the PC version. just look at how much more it pops lol. such a shameful port of the greatest videogame ever made.
1 Like
yeah this rules
time to hook up the 360
2 Likes
i have experience with two ten year old computers, xbones and trying 60fps and with all of them it was not working with the new master chief collection at 60fps all the time.
like its not like i havent tried
sorry for posting so much, just wanted to point out how good the water effects on the left looked for a freaking console launch title in 2001
3 Likes
I think this is why the Halo PC modders have you download levels – I think they had to rebuild and repack them to get the lighting working correctly. Same for the HUD – they just put up new assets because the PC ones were borked.
It’s terrifying how easy it is for information to disappear when everyone’s following one port to the next. It speaks to how information-dense games are, with thousands of hours from dozens of people, and how hard it is for any port team to even check whether things are right.
And, the unusual savior, that crowd-sourcing with tens of hours from thousands of people can be even more powerful.
It’s mirrored in how falsehoods get replicated and spread for decades from one sloppy whitepaper citation or newspaper article.
3 Likes
Lighting in Bungie games is almost always baked into the assets - which needs to be recalculated for the scene when changes are made (which results in long render times for iterations see: the kotaku reporting about Destiny development woes)
Totally plausible to me that Gearbox had basically the wrong lighting bake
you basically got it, yeah. this is how bungie engines have worked since marathon, back then a lot of extra shit was packed into the map file and that carries over into the original halo. the PC version has a different file structure which you might be interested in, maybe read this if you’re interested in learning more about it. The PC version is specifically weird because they pulled a lot of those assets out into separate resource files.
It’s hard to speculate on why the Gearbox static shadowmaps are broken but I’d guess that they had to crack open the levels to make some PC-specific changes and they didn’t have the light baker working the same way – there are shadowmaps in the PC version, they’re just not correct or as good.
I wouldn’t assume it’s due to a data structure problem. Most obviously, the map geo and functionality is present in the Gearbox port, which would cause extremely subtle and nasty bugs if they hadn’t replicated it properly. Not having the light baking tool or setting up an existing one probably could be something that passed functionality tests (it took the same input! and rendered output) while being wrong.
The greater point we can draw from this is that Halo .map files are delicate little babies and break at the slightest provocation, so the lighting being fucked in the PC port is no surprise
1 Like
all game assets are subject to catastrophic failure from the simplest human error
this gets a lot more fun when you go from 30 people to 300
2 Likes
needed to upgrade to .mapx imo