Since the Halo 3 flight concluded, the team has been working on resolving and investigating the community’s reports. The following highly reported issues from the Insider Halo Support site are currently being tracked by the team and are known. The following are Top Issues reported from flighting that we are continuing to work on for Halo 3 as of 7/14/2020 in build #1.1698.0.0.
Top Reported Known Issues
Poor Hit Detection/Registration Issues in Halo 3 Multiplayer. Some projectiles (such as those from the BR) are updated twice in the first frame, causing shorter-than-expected hitscan detection vs legacy’s range due to the higher tick rate in MCC (for more information about this, see the MCC Development Update for June 2020). On our side, this investigation is ongoing in finding a quality fix and is our top known issue of Halo 3 for both Xbox and PC.
Receiving “One or more actions are not bound to a key” error after taking an update or switching between Insider and Retail builds. We’ve improved our reporting of missing keybindings by adding a per-title notice when another title has actions unbound. While we are still investigating causes of this, it is recommended to run “Restore Defaults” at the “Controls” setting page if you still encounter this issue.
Secondary Weapons do not reload in Halo 3 while dual wielding. Halo 3 introduced per-weapon reloading (compared to Halo 2, which only had a single reload action for both weapons). Both Controller and M/K support this by having the “reload” functions on separate keys. Check the “controls” page for your input of choice to find out where it is bound (on M/K, this is defaulted to the “F” key, but can be rebound).
Weapon view model positions expose clipping or culling of the model. We addressed this during and after the flight further to eliminate the “exposed” elements of the Spartan’s (or elite’s) arms. While some issues remain at various FOV, Centered Crosshair and Ultrawide displays, and we are continuing to take on feedback and work on developing further support for adjusting the view model position across all titles.
Holding an object in Forge causes unintended clipping through the map, often killing the player.We changed to an “object-oriented” method of camera movement while holding an object for H2A, H3, and Halo: Reach (we are still working on bringing these features to H4). This caused some unintended side-effects, including the rapid death of players who may be accidentally flung outside of the map bounds. We’re continuing to take feedback on this and looking for ways to better improve this behavior across all titles and platforms.
Throwing equipment or a grenade in multiplayer sometimes results in multiple objects to be thrown. Our team is aware of this and continuing to investigate potential causes and fixes for when this occurs. We hope to have more on this in the future.
The following are Active Issues for Halo 3 as of 7/14/2020 in build #1.1698.0.0.
- “Security” is available as a separate chest option in customization and cannot be saved. To equip Security gear in gameplay, use the “Security” Helmet option
- Campaign Terminals can only be navigated with Page Up/Page Down Keys (PC Only on Mouse and Keyboard)
- Player Emblems may appear incorrectly on the Pause Menu on Xbox One S devices
- Some keys cannot be bound when using non-English keyboards
- Host and Clients may see inconsistent behavior while moving objects with different physics set in multiplayer forge sessions - all yellow bugs below.
- Auto-Turret in Forge will target friendly users when placed.
- Navigating Forge Menus with d-pad on controller will toggle the axis rotation option