Your latest update broke the ability to use the Legacy thumbsticks setting on H2A. It functions the same as the Default. It works on the other games fine still, but I cannot even begin to tell you how big of an annoyance this is. I literally cannot play H2A until this is fixed.
Yep so painful. Considering selling the gsme as H2A was my favourite online mode. Been a legacy user all my life and I literally get pwned on default. Please 343 fix this game
I’ve been playing Halo forever and also use Legacy. This bug is paralyzing. Please fix guys!! I can’t play H2A 
I ordered one of these yesterday (CronusMAX) It lets you play Legacy even on games that only offer default. Hope this helps 
I also forgot to mention that this problem is also relevant in Halo 4 campaign and multiplayer 
I found out a way to get around it though, you need to have DEFAULT setting set before the match starts. After the match starts then you can switch to LEGACY and it works. You need to do this every time though for H2A matchmaking. This trick however did not work in Halo 4 Campaign 
i would understand the pain for pros that use legacy haha bummer
Really 343? This was not addressed in the 12/15 update! This should be such an easy fix and I basically have a useless new game until it is!
I so doubt this will ever get enough attention because I know it is a very small minority of players, so dumb. Glad there’s a chinsey workaround until then, thanks Lose.
EDIT: The workaround did not work for me either.
I’ve been out of town and haven’t been able to play for awhile. On the playlists where legacy is working did they ever fix the sensitivity problem with the right thumbstick where it doesn’t register when you press in certain directions.
I saw with the patch notes from today that they’re going to be fixing what they broke in the last update, but I’d really prefer it if they put in the effort to fix the legacy controls completely and not just revert to the previous half -Yoinked!- setup they had before.
delete
> 2533274950663738;9:
> > 2579517108016271;7:
> > Really 343? This was not addressed in the 12/15 update! This should be such an easy fix and I basically have a useless new game until it is!
> >
> > I so doubt this will ever get enough attention because I know it is a very small minority of players, so dumb. Glad there’s a chinsey workaround until then, thanks Lose.
> >
> > EDIT: The workaround did not work for me either.
>
>
> It’s such an easy fix? How would you know? Why don’t you go over and fix it for 343 then, while they’re addressing far more important problems that impact far more players than a control scheme?
I get where your coming from, but dismissing the problem this creates for those of us who use legacy as less important isn’t really fair. It’s a completely game breaking obstacle for legacy players.
> 2579517108016271;7:
> Really 343? This was not addressed in the 12/15 update! This should be such an easy fix and I basically have a useless new game until it is!
>
> I so doubt this will ever get enough attention because I know it is a very small minority of players, so dumb. Glad there’s a chinsey workaround until then, thanks Lose.
>
> EDIT: The workaround did not work for me either.
What doesn’t work for you with the workaround? I assure you the cronus adapter method does work and in some ways improves upon using the inbuilt legacy controls within the game. If you are having issues getting it set up I would be happy to try and help you with any questions you might have.
Nillaz - I was referring to the one he mentioned that you have it on Default, then switch to Legacy once in game. Also, I’m not sure about the sensitivity issue. I only really saw problems with movement/aim in H3 games. It still seems more sensitive than in the past, but that was easily remedied by turning my sensitivity down.
GoonMaster - Go be a Goon somewhere else. The point was that the setting was working until the 12/7 update, there’s a 99% chance it’s a minor tweak.
Thank you. I’m glad i’m not the only one who’s experiencing this issue. Except for me it’s broken in every Game, multiplayer and single player. Can’t play h1 - h4. When set to legacy, controls somehow revert back to default.
The new update again ignored this issue for H2A. It says H4 was fixed, but I have not tried. This is getting ridiculous, and there is also another thread on this:
> 2579517108016271;13:
> The new update again ignored this issue for H2A. It says H4 was fixed, but I have not tried.
I jumped online after the update and tried it within both Halo 2 Anniversary as well as Halo 4. While it works perfectly in Halo 4, H2A is still broken!
Once again 343i team, I truly appreciate the extraordinary amount of time and effort you have dedicated towards fixing Halo MCC, but this is beyond frustrating. It has been over two weeks since I have been able to actually play the most prominent matchmaking playlist in The Master Chief Collection! Can you at least give us an estimated time frame on when this will be fixed?
I reiterate my earlier post that this issue will continue to be ignored since it affects a low amount of the population. Thanks!