You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason, when tilting the freecam while using a speed modifier key, and letting go of said keys, the tilt can get "stuck" and it keeps on going. I believe it might be due to the Input wrapper still registering the tilt for some reason. What its weird is that this only seems to happen in Aragami? Should investigate.
shift / alt key down -> tilt key down doesn't work tilt key down -> shift /alt key down -> shift/alt key up -> tilt key up continues with the tilt
Edit: I found this problem on Sable as well. I have read that it may be a Unity bug. In either case, we could try refactoring how the tilt works with GetKeyDown and GetKeyUp if those are not affected by this bug.
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
originalnicodr
changed the title
[Aragami] Tilt get stuck when interacting with the fast/slow speed multiplier
Tilt get stuck when interacting with the fast/slow speed multiplier
Mar 10, 2024
Are you on the latest version of UnityExplorer?
Which release are you using?
BepInEx 5.X Mono
Which game did this occur on?
Aragami
Describe the issue.
For some reason, when tilting the freecam while using a speed modifier key, and letting go of said keys, the tilt can get "stuck" and it keeps on going. I believe it might be due to the Input wrapper still registering the tilt for some reason. What its weird is that this only seems to happen in Aragami? Should investigate.
shift / alt key down
->tilt key down
doesn't worktilt key down
->shift /alt key down
->shift/alt key up
->tilt key up
continues with the tiltEdit: I found this problem on Sable as well. I have read that it may be a Unity bug. In either case, we could try refactoring how the tilt works with GetKeyDown and GetKeyUp if those are not affected by this bug.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: