Halo: The Master Chief Collection

Halo: The Master Chief Collection

Not enough ratings
Halo 2: Tickrate AI Balance Fix
2
   
Award
Favorite
Favorited
Unfavorite
Engine: Halo2
Game Content: Campaign
File Size
Posted
Updated
9.590 GB
27 Aug @ 9:48am
30 Aug @ 9:05am
5 Change Notes ( view )
You need DLC to use this item.

Subscribe to download
Halo 2: Tickrate AI Balance Fix

Description
MCC's Tickrate broke the AI, I fixed it

There is a notorious bug with Halo 2's AI in the MCC release, they act at double the speed they should, oftentimes causing instant death. This is due to the tickrate for the game being doubled, but 343 not bothering to make the necessary balance changes.

What this fixes:
  • Instant deaths due to mass damage.
  • Jackal Snipers can actually be reacted to. They also can't fire twice at a time.
  • Shield recharge speed no longer outpaces weapon damage.
  • Behavior is 1 to 1 to it's Original Xbox version.

What this does not fix:
  • Tickrate issues not related to gameplay.
  • Legendary being extremely unfair. It's just playable. Play Heroic.
29 Comments
Zephyr 22 minutes ago 
Disregard all that previous slander below, this is the number one bug I wanted fixed for MCC. Thank you.
Gard Hater  [author] 12 hours ago 
Or whatever delay your current framerate applies to it, which will pretty much always be less than 33 ms.
Gard Hater  [author] 12 hours ago 
All of this to say, the problem with the animations is that soft pings are set to play every 0 seconds, which on Xbox is every 33 ms. On PC it is obviously 0 ms, which is notably less than 33 ms.
Gard Hater  [author] 16 hours ago 
Also the MCC tickrate thing isn't in CE, it's just in every other game and breaks them all.
Gard Hater  [author] 16 hours ago 
Also because of that, it's kind of impossible to know what is and isn't frame dependent in the engine. Some things are tied directly to tickrate, other things will just break if you don't fix their values. So, since you need every value to be at minimum 33 ms, you just make sure every value you're actually going to use is at minimum 33 ms.
Gard Hater  [author] 16 hours ago 
The lowest value you can use for anything is 0.033, equal to one tick. Anything under that will not work properly and a good number of things in the mod tools default to a minimum value of 0.

Now, this doesn't make any difference whatsoever when you're developing a game for a console under fixed conditions, but GBX and MCC both increased the framerate.

MCC's solution to these problems was to increase the tickrate to 60, breaking a bunch of shit but fixing other shit.

The actual solution is to just make sure the game's internal functions all run at minimum 33 ms.

Which, it is just a matter of incompetence and/or apathy that they couldn't figure that shit out on their own.
Gard Hater  [author] 17 hours ago 
It wasn't that the animations were going too fast, they were just completely disabled.
Gard Hater  [author] 18 hours ago 
It's actually much worse than that based on the gameplay footage I found. I know what's happening though, so it shouldn't take me long to fix it.
Ratich 18 hours ago 
@Gard Hater In Halo CE on the Gearbox port and MCC the Elites recover from their stunned status much faster than on OG Xbox. Making the current version much harder than the OG version
Gard Hater  [author] 22 hours ago 
You can't say, "I call bullshit," and then say, "The two main big modding community discords are both led by trans figureheads," if you're trying to reply to, ">It's the same modern liberals that have taken over the rest of the tech sphere," goofball.