No, the tools aren't linux compatible.

There won't be a similar fix for Reach, correct?

Or well, it's skipping one full update then firing. Since there's two per second, it fires every half second.

Further explanation.

0.566 is the limit because of two reasons.

0.5 ensures that 30 hz is skipped every second. It skips half the first update then half the second update. This puts the total delay at 0 seconds.

If you use 1, it would normally skip one full update then fire, however now it is skipping one, firing, then skipping another and firing again, putting the delay at 0.5 seconds.

If you use 2, it skips both updates then fires, putting the delay at 1 second.

Etc, etc.

0.066 ensures another 33 ms of time is skipped per update, in case any frame dependent actions are being taken.

They fixed the weapon bugs but not the AI bugs. I fixed the AI bugs.

I thought they fixed this bug in the past, or is it they only fixed tickrates in Multiplayer?

The mod tools don't support it, so idk, has anybody else gotten Halo 2 Anniversary mods?

Can you eventually get this working with anniversary graphics ?

The tickrate causes double updates, which you have to fix. There's then the fact that a lot of timers update per frame, so they need a delay added to not outpace the engine. The complicated part when it comes to the new tickrate is that 0.5 = 0.

So, for example if I want to take a timer with a .1 delay and fix it, then I have to use the following formula:

0.1 * 2 + 0.566 = 0.766.

But the really ♥♥♥♥♥♥♥ annoying part is that some things have parent timers, so you have to figure out what the parent timer is. Changes to any timer underneath the parent work normally, the parent is the one that updates per tick.

For AI behaviors, it's the perception timers.

For AI attacks, they use the difficulty scales.

It is very, very complicated.

I don't think most people actually have the knowledge to implement this fix correctly is why it hasn't existed thus far.

This is amazing and should be integrated into every single mod on here. MASSIVE oversight that this bug is present and I'm surprised I'd never heard of it before.

New update fixing the AI computation speeds, so now both their combat behaviors and regular behaviors are fully restored.

I can do everything but Reach due to compatibility issues.

The jackal leg thing is just because the jackal's legs don't have collision. That's not a bug, it's actually just the case for every character before Reach.

One of the jackal death animations is glitched in Halo 3 as well the legs cross and glitch through each other

Sorry if this has already been asked but can these fixes be applied to the rest of the campaigns ?

"Brother, Elon Musk is a Nazi,"

Nothing else to say, just look at that quote.

Oof, a MAGAt out here blaming all the wrong people for their problems, most common L I've ever seen lmao.

Brother, Elon Musk is a Nazi, the remards "leading the current techsphere" or whatever are all fascists grinding the world and people down for quick cash, that's literally why that AI generative slop is everywhere and pervading every single part of our lives now.

It's not slander, it's my first amendment right to voice my opinion on what is wrong with both the modding community and this game.

Disregard all that previous slander below, this is the number one bug I wanted fixed for MCC. Thank you.

Or whatever delay your current framerate applies to it, which will pretty much always be less than 33 ms.

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.

Also the MCC tickrate thing isn't in CE, it's just in every other game and breaks them all.

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.

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 ♥♥♥♥ but fixing other ♥♥♥♥.

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 ♥♥♥♥ out on their own.

It wasn't that the animations were going too fast, they were just completely disabled.

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.

@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

You can't say, "I call ♥♥♥♥♥♥♥♥," 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.

>It's the same modern liberals that have taken over the rest of the tech sphere.

I call ♥♥♥♥♥♥♥♥. The two main big modding community discords are both led by trans figureheads. Them and their teams are pretty much the only reason we even have *any* documentation in the first place, ♥♥♥♥ one of them is one of the founders of C20 which is the only actual formal resource we can point people to to learn the basics and is used by nearly everyone daily.

Three of the biggest modding projects in development (H2R, Halo 3 Combat Evolved and Halo:Reborn) are led by queer folk, while one of the biggest CE mods ever (TSC:E) with *extensive* documentation was also made by a team of likeminded people with most of them being very eager to answer any questions you may have in the Reclaimers discord, not to mention they were fundamental in putting together the early beginnings of what would turn into SPV3.

What is the CE issue, I'll go fix that.

This issue has been present since the Vista port. Halo CE has a similar issue.

The entire burden of a community's culture cannot be placed on the companies alone. Hence why the comments I made.
I think the community is indeed responsible for a lot of its own shortcomings.
That said, 343, Halo Studios, and I'd argue even Bungie themselves, were responsible for a lot. Even still, I do think Halo's community, both modding and not, has had major cultural issues. That's really my main point with that.

The tools being ♥♥♥♥ and MCC making things harder doesn't fully explain the community hoarding basic info and knowledge as a currency only some people have the right to have. Companies are an enemy of all, but there are definitely internal issues within any community that are not exclusively caused by a company's managers.

To be honest, they likely haven't fixed this because they don't care. Let's be real, it's 343 Industries, it's a team of people that don't want to be working on someone else's titles. They're getting forced to, and realistically that's not fair to them in the same way them ♥♥♥♥♥♥♥♥ out terrible games isn't fair to the consumer. The Halo Studios rebrand just means they're on borrowed time.

I don't agree with some of the sentiments but I do think credit is due here. Modding communities are one thing, but the real enemy are publishers who keep devs from doing their work (or devs that don't think this is an issue for MCC)
Thanks for your hard work!

It's the same modern liberals that have taken over the rest of the tech sphere. Only difference here is that, the games have been out so long they were able to fully kick the normal people to the curb.

Yeah, the modding tools are extremely hard to use, and the community does not help itself with proper documentation and prefers to heavily guard basic info. Literally every other modding community, even those that deal with way more technical issues, have way better culture.

Well, in all fairness. This is a ♥♥♥♥♥♥♥♥ of work for zero pay. Even setting up something basic can take hours with the tools. The issue I have with the mod community myself is that they will spend all that time and then produce something barely quality enough to share.

@Bruurbs, I second that on the modding community. The only worthwhile mods being made are by Youtubers. Which, come to think of it, is baffling that a Youtuber can pump out high quality mods while maintaining their Youtube channel, but the rest of the modding community can only be bothered to make a pink Grunt tag file.

That is a big part of why I hated playing Halo 2, so this mod will end up being one of my main ways of playing the game in the future

I was actually kind of surprised it affects shield recharge rates. However, without this fix some enemies just become invincible unless you use certain weapons.

Also, don't be discouraged by the community's lack of interest. Halo's community is probably the worst in all of gaming, which extends to its modding community. These fixes are welcome by anyone who is here with a brain.

This is ♥♥♥♥♥♥♥ amazing. I have an insane interest in these kinds of fixes, thank you very much for making this!

I'll leave it up but unlisted for the three subscribers that do exist.

There is no community interest in having these fixes. Guess I'll just keep them for personal use.

Weird, I don't remember them doing that back on the original XBOX, but as a kid I only ever played that on easy.

Nah I'm pretty sure they just do that.

Holy hell, is THAT why Elite melee instantly kills sometimes???