Let me copy-paste my July 2020 feedback again here, with some modifications along the way, as Xbox now officially supports Gyro Aiming via xCloud.
Misc/Other Feedback:MCC HALO GAME: ALL
The Short version:
- Simultaneous Controller+Keyboard/Mouse / Mixed Input support, as a Accessibility option. (If enabled, you will considered a Keyboard/Mouse player in Public PvP Multiplayer)
- Disabling Aim Assist
- Steam Input API Support + Controller Rebinding
- Dynamic Resolution
- FULL Subtitles (as in, Gameplay Dialogue subtitles)
- Locking Cutscenes at 30fps, In-Game.
The Long Version:
1. Simultaneous Controller+Keyboard/Mouse / Mixed Input support
Ever since the launch of Halo 3 on PC, you can now switch between Controller to Keyboard+Mouse...but not both at the same time.
While a lot of games has Mixed Inputs, they don't always take account of how certain players want to use both inputs at the same time. otherwise, the Glyth/Button prompts will fight each other or conflict with Controller Input (such as Sunset Overdrive's Weapon Wheel/UI UI & Camera and Middle-earth: Shadow of Mordor's Build-in Controller Aim Assist).
While a very small number of games offers a option to manually Lock Button Prompt (or/and Switch Button Prompts) and/or allow Mixed Inputs, such as Fortnite's "Lock Input Method as Mouse" or Death Stranding's "Button Icon Display/Change Button Icons" Options, Call of Duty: Modern Warfare (2019) and soon, Halo MCC, may (or will) force you to use either Controller or Keyboard/Mouse Input due to Input-based Matchmaking reasons.
Since Halo MCC plans to include Cross-Platform Play and Input-based Matchmaking, the best solution is to make "Mixed Input" as a Accessibility option, which will allow both Controller and Keyboard/Mouse Inputs to be used at the same time instead of conflicting with each other and the Game's UI.
But, as a major downisde; in Context of PvP Public Multiplayer (NOT to be confused with Co-op), turning that option on will make you a Keyboard/Mouse User (even Aim Assist will be turn off by force) and you will be put to Keyboard/Mouse Matchmaking Pool.
Despite that, this will allow Steam Controller, Gyro Aiming and Azeron Gaming Keypad players to use Controller Input and Mouse Input together (this is important for Steam Controller and Gyro Aiming players the most, especially when the interest of Gyro Aiming is increasing and more games on Nintendo Switch are starting to add it.
) instead of having to choose between Controller or Keyboard/Mouse Inputs. (and it's not possible to replicate "Universal Default - Recon" control scheme if you're trying to translate "Keyboard/Mouse" Input to Controller.)
speaking of Aim Assist...
2. Disabling Aim Assist as a Option
in context of Mixed Inputs, it should be a option across all Halo games instead of making it as a Skull, with a exception of Multiplayer IF
Mixed Input is turned on.
3. Steam Input API support + Controller Rebinding
Valve has a Controller API that uses In-Game Actions and Action Sets (useful for Vehicles and Menu UI) instead of Controller/Keyboard Inputs.
There's a document/videos on how to implement Steam Input:
If implemented well, this will allow support for various controllers, including PlayStation Controllers, Nintendo Controllers, Steam Controller, Steam Link Touch Controls and even Future Controllers while allowing Rebindable Game Actions beyond Halo MCC's Controller Options (although, Controller Rebinding can added In-Game, if 343i and Co. wants to)
without having to manually add support for a specific controller. (Even Xbox Controllers can have some benefit!)
No need for non-Xbox Controller players to rely on Input Mappers such DS4Windows, JoyShockMapper, reWASD and Steam Input Legacy Mode JUST to play a Halo game.
....just take account of Trackpad and Gyro/Motion Controlled function beforehand. Most games just make the Camera "In-Game Actions" as a "joystick_move
" instead "absolute_mouse", as it doesn't work well for the Steam Controller's Trackpad and PlayStation/Nintendo Controller's Gyro Sensors.
I mean, xCloud Touch Controls supports Gyro Aiming now.
4. Dynamic Resolution
Halo 2 Anniversary on Xbox One already has it, it would be nice to have Dynamic Resolution across all Halo Games.
As Halo 4 will be the last game in the collection (and I believe it may or less demanding than Halo 2 Anniversary), this will benefit Low-Spec PC Users the most in the long-run.
5. FULL Subtitles
Instead of Cutscene only Subtitles, there should be one for Gameplay Subtitles. Halo CE Anniversary already has it build-in, so why not?
It's hard to hear Dialogues during Combat as it is.
6. Locking Cutscenes at 30fps In-Game.
Instead of dealing with 30fps animations while everything else at 60fps or higher, it's better if you just lock the in-game framerate for cutscenes only, similar to how Ryu Ga Gotoku / Yakuza games on PC handles it. /
This will save a lot of trouble with Cutscene Animations.