Two Long Standing Controller Bugs
There are a couple of major bugs relating to controller use that have been in the game for as long as I can remember...
Controller Bug 1.. Sometimes when you are running & turning whilst trying to use your ULT or trying to ping something your movement controls can completely lock up and you have to release all your pressed inputs to regain control of your character again. The cause of this issue is most likely something relating to the L1/R1 functions (the buttons that control pinging and ULT/'Q' activation) because you can hold down any combination of movement inputs and the L2/R2 trigger buttons without the bug ever occurring (in other words, this bug never occurs during normal movement, aiming & shooting, it only happens when you try to throw in a ping or an ULT activation during movement).. I guess it is also possible that auto-sprint could be causing this, because pushing the sticks to the point where 'sprint' is engaged is a common denominator with this issue, it nearly always happens when both sticks are at max threshold whilst holding & aiming an ULT or trying to ping something.
It is an annoying bug, especially if you use certain characters.. for example, Maggie is perhaps the character I notice this bug the most on... when you have L1/R1 held and you try to aim/direct your wrecking ball whilst also doing some kind of running/turning manoeuvre all your controls can lock up preventing you from changing the direction you are running & aiming. I also experience this bug occasionally with Loba Q's (because her 'Q' is like a quick escape ability so you are usually running/sliding & swivelling around whilst trying to aim the held 'Q'). I have experienced this bug using multiple controller types (on PC) so it is not peripheral related. It should be fairly easy to recreate this bug (and diagnose) using the descriptions I have supplied. Triggering the bug is possibly dependant on timing, for example mistiming the simultaneous L1/R1 click when activating an ULT might initiate the glitch.
Controller Bug 2.. This is a biggie. It is something a lot of controller players have noticed and I guess we've just kind of learned to work around it.. Customized ALC settings affect the default sens settings even when the ALC's are turned off.. I am not talking about the Per-Optics settings in the ALC menu, it is fairly common knowledge that they change the default ADS sensitivities (not just ALC settings) and this is a fairly useful setting (I've always assumed it is an intended feature).. However, the problem is this.. It's not just the per-optics that affect the default sensitivities, it is some, or all, of the other ALC settings to.. they don't change the default sens in very obvious ways (like the per-optics do) so it is not immediately obvious to most players. Some players do notice the difference though and even though this enhanced ability to tinker with your default sens via your ALC settings might be considered a useful thing it actually isn't because it means that your default sens is NEVER actually default, instead it is always a combination of your default sens mixed with whatever settings you have in your ALC's. My guess is that the cause of this bug has something to do with the ability to change your default per-optics via ALC's, the intention was probably for this feature to only work for per-optics but for whatever reason it also causes other ALC settings to bleed through (or 'stack') thus subtly affecting the default sens values.
I've seen players try to report this ALC bug in the past but they never got any reply on the issue so I don't know if it has ever been fully tested.. it would be nice to know if this bug is actually a thing or not. It is quite easy to test, you just get accustomed to a default sens with the ALC values in their pre-set 'factory settings' (and turned off) then start messing around with the ALC values (so they are no longer at their pre-set 'factory settings' values), and you will notice that even when they are turned off they still affect your default sens. Your default sens will now feel completely different depending on what deadzone value, outer threshold value, response curve value, etc. you have configured in your ALC's (despite them being 'off'). Even changing the yaw/pitch/ramp up values in ALC's affect the feel of a default sens.. This is highly problematic because it means that players who have been using a default sens for thousands of hours are not actually using a 'pure' default sens, they are using a sens that is being unintentionally influenced by their ALC settings (whether they are set to their factory values or not). In some ways, having your ALC's set to their pre-set factory values when you are using a default sens is actually more problematic because the pre-sets in ALC's force a high deadzone/high response curve 'classic' sens which (even when turned 'off') changes the way a default no deadzone/zero response curve 'linear' sens feels.
If testers can confirm that there is some kind of issue with various ALC settings influencing the default sens settings, some kind of fix that maintains the option to still use the ALC per-optics for default sens (without any bleed through of other ALC settings) would be favourable. As someone who used ALC's for a very long time but pretty much only uses default sensitivities now, I would like to know that when I do use a default sens that it is 100% pure, unaffected by any of the values in the ALC menu. (Side note - even if it is found that the per-optic sub-menu is not part of the problem it probably still needs to be a completely separate setting rather than part of the ALC menu).
