Bugs that get ignored by Halo Support

I have been an avid user of submitting Bug tickets on Halo Support. However, some bugs and issues get more or less ignored if they are more of ways to improve functionality rather than game breaking bugs. In these Reports that get immediately “Solved” without much follow up from the Agents, they suggest going on the waypoint forums to discuss with other users to get the bug more traction in order for 343i devs to take the suggestion more seriously. So I am listing each issue/bug/suggestion I can think of and I encourage others to respond to this message with their own improvement ideas or bugs that get ignored by Halo Support. I am also going to list the Bug submission number for my bug list here showing I have indeed attempted to provide feedback, and so I do not get a canned response from 343i forum mods telling me to submit my bugs to Halo Support.

Submission #38818
This is one I would really like to see changed or at least a decent explanation to why 343i has moved in this direction. This is a big difference between KB/M and Controller. On controller the ‘Action’ button responsible for picking up weapons/opening doors, and ‘Reload’ have always shared the same button. For example Recon is Right Bumper for both. However, on KB/M these actions both need a separate key and cannot be combined. This extends to duel wielding, picking up a second weapon and reloading the second weapon are all separated on KB/M. For those who like having every button separated for maximum precision, I can see this being beneficial, however, I personally would at least like the option for these actions to be combined to reflect controller a little closer as that is what I am used to and have been using in Halo for nearly 20 years.
In the 2003 Gearbox port there is an option to combine ‘Action’ and ‘Reload’ to one key on KB which I have also gotten accustom to over the years playing there. So to me MCC does not even have the functionality of the Gearbox port of 2003.
In the Halo Infinite Flight for KB/M 343i have also separated Action and Reload into separate keys so this is a purposeful decision on 343i and I want to know why this is the direction they have taken.

Submission #230581
Skipping cut scenes in CE for MCC on KB/M also causes the player to jump immediately. Skipping cut scenes is locked to Space Bar, however, this is also my jump button. And for some reason pressing Space to skip the cut scene will also count towards jumping on the first frame when the level begins. So my one Space Bar input counts towards 2 separate actions. This feels like a more serious bug/issue but also went ignored. This can be seen on levels The Library, Two Betrayals, and Keyes for examples.
Also in the 2003 Gearbox port, ‘Enter’ also allowed for skipping cut scenes, something that MCC does not include.

Insider Submission #46918
MCC on PC only also for KB/M and Controller as input devices. Why can’t I play with a Guitar Hero guitar if I so please? Once again 2003 Gearbox port allows for this.
Also why is the transition between KB/M and Controller so rough? Games like Minecraft and Portal let me use 2 input devices at the same time with no issues. I can hold W on KB and look around with a Controller at the same time no problem in those games.

Submission #63920
This one is actually still open yet I have been following up on this report every time there is an update to game to remind Halo Support this is still on going for over a year and it has been fairly frustrating. I would like to see if anyone else can replicate this bug. In ODST as the Rookie, this can been done on any New Mombasa Streets level, with the VISR (light) on, scoping while the FOV is on 90-92 causes the view to shake and not zoom in smoothly/properly. This only occurs as the Rookie character and with the VISR on and it very clear with the starting SMG and Magnum.

Submission #93932
This one is also still open yet has been an issue since 2015 and anyone who has ever played Halo 2 on any other version to MCC would have noticed immediately so I am surprised it is still an issue. Halo 2 has a ‘proximity radio’ as I like to call it. When characters in game are far enough away so their voice lines are not heard, their lines play over the radio instead for us to hear. However, the radio has been silent for nearly all of MCC’s lifespan. This is a legacy issue with the Vista Port that was brought into MCC. In Vista, these radio lines were said extremely loudly for an unknown reason and this was present at the start of MCC as well. However, this was ‘fixed’ by just muting the radio. The radio has been muted ever since. These radio voice lines are delivered by characters on the map, all radio lines heard are by characters not actually present on the map like, Cortana are still delivered. In game characters like Johnson that have in game lines do not come over the radio.

That’s a good start but I have many other bug/issues that do not mirror the original releases of the games. However, Halo Support makes me check up on all my submissions every update to make sure they are still happening so I can’t make a bug for everything because that would take a time commitment I would not be able to fulfill. And if I do not response to their request for confirmation the bug is still present, Halo Support will just close the report due to inactivity and the bug never gets fixed.

I’d like to hear from anyone else who has had a similar experience with Halo Support, and tell me anything that you would like to see fixed in MCC!

6 Likes

It’s great that you’re uploading bugs to the support site. They are definitely being added to a list.

But the fact is the bugs you’ve submitted aren’t really all that big or game breaking. And a fair few of them are intentional features or about a feature that you want added to the game.

Bringing it to the attention of the forums is a good way of gauging how significant the community thinks these bugs are. That’s why a lot of CE’s graphics has been fixed. Though it doesn’t look like anyone has any strong opinions on the bugs you’ve submitted.

4 Likes

Major audio issues like music barely being audible and most cutscenes having too low dialogue in Halo 2 Classic. This still hasn’t been fixed.

3 Likes

There is a similiar radio comms issue in Halo Reach, where the characters who speak far away from you have their voice switched to radio comms, except the bug makes these lines extra quiet, as if they’re still just talking far away from you with no radio comms at all. You can hear the audio “shift” from regular speech as you get further away, to radio speech- but it doesn’t sound like it’s coming from a radio headset, it just still sounds like it’s coming from the other Noble Team member far away.

Has anyone ever got an actual response on support tickets? AFAIK I only got automated responses during flights and assumed everything was just piled up on a list of things to work towards. Maybe that happens with your tickets as well. They have ben added to a list with possibly low priority since they’re not game breaking issues.

In this case I do agree that some sort of response would mitigate this feeling of being unheard.

Would also like the toss in a complaint about H2 Classic’s audio being mixed rather poorly. And the radio lines not playing if you aren’t close enough to the characters saying them should also still be fixed. I don’t know how much longer 343 will be patching MCC, but these two bugs in particular should be fixed before they’re done.

Maybe but it does feel like things do get ignored. It’s like some of the most requested things for MCC is things like support for Linux and they still haven’t fixed the Halo Reach graphic glitch that can cause seizures…though I’m surprised that isn’t a priority since there’s no warning and well I think 343i could get sued if they don’t at the very least have warnings about this glitch.

It’s interesting. I actually have received responses from real people on the team. Some are automated, telling me to check up on them again every update. But for the most part, they’ve shown investment by describing back to me certain aspects of the issue, and acknowledging whenever I include screenshots and/or footage.

I do understand though. I currently have 3 tickets that have been active since 2019. But I’m holding on.