Jump to content
Sign in to follow this  

Halo 5 November community update

Unease Peanut

As you may have noticed, Halo 5 has had an update. Not only is the weekly playlist, shotty snipers, available for the weekend but we also get some updates to the playlists and game itself.

One of the updates is the removal of the 'Orion' map from all playlists. Don't fret, it will be back! It has been pulled from matchmaking temporarily to fix some of the bugs and glitches. Including, but not limited to, spawning and the issue where people would get banned for suicides for trying and failing to get to the DMG boost. In place of this we get a total 15 more map gametype combinations which I'll list down here:




Team Arena



  • Trident


  • Regret


  • Empire


  • Plaza


  • Truth
  • Empire
  • Pegasus


  • Empire
  • Fathom
  • Coliseum
  • Truth


  • Empire
  • Fathom
  • Coliseum
  • Truth




Additional matchmaking fixes include the removal of the "One or more members in your Fireteam has a high latency to the dedicated server" error and expanded parameters for the Warzone matchmaking system which allows international players to find matches quicker and easier. 343i is still working on the last fix and has let us know that they did see improvement in Warzone search times but need some more time to check if it doesn't interfere with anything else, so they've pulled the changes for a bit untill they're sure no other problems are caused.


We also got a little sneak peak at some additional REQs that will roll November 16th. In the upcoming weeks 343i will fill in the blacked out REQ cards below:








So keep your eyes on their blog :D


Additionally 343i's Lead Sandbox Designer for Halo 5 Chris King and Scott Sims acknowledge the issues with the aiming mechanics within Halo 5. They've written a nice little piece which I'll paste below:



"Hey everyone – Chris King (Halo 5 - Lead Sandbox Designer) and Scott Sims (Halo 5 – Lead Sandbox Engineer) here. Thank you all for your passionate feedback on Halo 5, the team has been actively following as much as we can and have identified one issue we really wanted to respond to.


First things first, in the grand scheme of things, this is happening to a small number of people. Most folks are having a good experience and the last thing we want to do is inject either placebo effect or confirmation bias into your gameplay feel, so bear that in mind if you’re having no issues, and just enjoy the dry but interesting technical data. But this is good news for those who are suffering.

Aiming is the core of any first person shooter experience, and the way Halo controls is key to making Halo, Halo. Weapon aiming is a complex subject and something that the sandbox team obsesses over every day. There are a huge number of factors that feed into the feel of aiming, be it controller hardware, acceleration curves, turn speeds, player movement speeds, aim assist, or weapon fire rates.


When we started development on Halo 5 we had some very specific goals with regards to aiming. We wanted to provide a best in class 60fps shooter experience, embracing competitive play, with an increased skill gap, while still retaining the essence of Halo.

To preserve that Halo feel we chose not to re-write any of our base control systems, but instead to perform targeted retunes to balance for the higher framerate and myriad of other changes made to our movement and weapon systems.


Throughout the project we have worked hand in hand with the 343 Pro team, Microsoft User Research, and test teams and of course absorbed the awesome feedback from the Halo 5 Beta to tune and validate our control systems to what we believe to be the sweet spot for fine control with fast turn speed across all aiming ranges, on all weapon types.

Players have identified that, by design, the game is a shade “harder” than it used to be, but we are seeing players adjusting to the new speed and precision pretty quickly.


Unfortunately, some players have identified an issue that occurs due to variance in controller hardware, commonly referred to as “slow turn” bug. This can cause players to become unable to, or inconsistently reach what we call a “pegged” state.

The “pegged” state is a region in the outermost range of the analog aim stick in which we blend the players turn speed to a much faster rate. This issue is compounded as the control input fluctuates depending on multiple factors - if you are applying even the slightest bit of downward pressure (clenching), moving the stick around the edges a bit (which is why it’s even more problematic when aiming diagonally), or torqueing the stick on the edge a bit more than normal on some controllers.


The good news is we have a fix for this issue that introduces no perceivable change to the current feel of the game. This change is going through test and pro team validation now and we will have it out to you soon.

One thing that has become clear in absorbing all your feedback is that Halo players want choice when it comes to controls. And with that in mind, we are also working on another little pet project that will allow even more precise tuning. This update will offer more custom fine-tuned control over controller settings (hint: independent vertical/horizontal sensitivities, the ability to calibrate your own dead zones, more granularity in sensitivity, and more). We hope to have that out for you in December and we will follow up with more details later.


Thanks for all the passionate feedback, know that the team is reading as much as we can. See you on the battlefield."

~Chis King and Scott Sims




What are your thoughts on the changes and plans, and do you have any suggestions for changes yourself?

Let us know down below!

Thank you for reading




Sign in to follow this  

User Feedback

Recommended Comments

There are no comments to display.

  • Create New...