Hooooo boy- this one is a doozy. I have a feeling it's pretty dang unique, too. A couple of days ago while playing Destiny 2, I noticed that one of my controllers began having a seriously odd issue- but ONLY in Destiny 2 and, to a lesser extent, Destiny 1. The odd thing is that only the one controller is having this problem. My other controller works just fine. Here's the basic list of what the controller in question is doing: - Cannot use any emotes whatsoever in PVE combat zones in Destiny and Destiny 2. D-pad is completely unresponsive. D-pad (including emotes) functions perfectly outside of PVE combat zones, including in social spaces. Emotes work as intended in PVP activities. - When a sword is actively equipped, but ONLY a when a sword is equipped, right trigger is completely unresponsive. Occurs in D1 and D2. Melee/Light attacks work in D2, but not in D1. Does not occur with other Power/Heavy weapon types- only happens with swords. - In Destiny 2, whenever a sword is actively equipped, the following actions will cause the sword to swing on its own with no input from the melee button or right trigger, including: leaving the game menu, resuming the game from the Xbox One dashboard, coming to a stop after sprinting, at the end of the class ability animation for each class, and at the end of a slide. Does not occur with other Power/Heavy weapon types- only happens with swords. Again, this behavior is only on the single controller in question, and ONLY in Destiny and Destiny 2. No other odd behaviors have been observed in any other games or apps, which eliminates the possibility of a hardware issue as far as I can tell. And the fact that it only occurs in D1 and D2 and the second and third behaviors only occur with swords makes me think it's some sort of odd programming gremlin. Any thoughts or advice? At this point I am completely baffled.