InputHud uses in-game values for angles instead of inputs

Description

The input HUD angle element (available under the tas preset) calculates its values from the player's in-game rotations instead of monitoring the raw inputs. As such, whenever the player gets rotated, SAR picks it up as human input, even if the player hasn't moved their mouse/joystick/gyro device.

Similarly, when the player's view angles are partially or completely locked (like when using the Reset Camera action), SAR erroneously shows no inputs on one or both axes.

Accidentally discovered in this thread in the P2SR Discord server.

Steps to reproduce

1. sar_ihud 1
2. sar_ihud_preset tas
3. • play sp_a1_wakeup,
   • use the Reset Camera action via Steam Input, or
   • use the Spin 180° action via Steam Input

Workarounds

sar_ihud 0

Repro clip

https://github.com/user-attachments/assets/1767c592-d123-48da-9c77-1ce71cdaee24

Slowed down 20x¹

https://github.com/user-attachments/assets/27ad9578-77f5-4cd4-822f-05966399a9a1

_____
¹ Your browser might have issues playing this one. It's the same video bitstream, just slowed down 20x.

Start with the InputHud angle element used by the tas preset, then reproduce the behavior with sar_ihud 1 and sar_ihud_preset tas in sp_a1_wakeup. Check how the element obtains angle values during player rotation and the Reset Camera or Spin 180° actions. Done means the HUD reports raw mouse, joystick, or gyro input without treating game rotation or locked view angles as input.