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
I confirm this issue is not an exploit. (Required)
BYOND Version
515.1647
Issue Description
When jumping to AI core and then attempting to move your camera it rubberbands back to your previous location.
If you attempt to track someone and move your camera your camera rubbersbands back to your previous location.
If you track someone and move your camera your camera will still attempt to track them.
Bug may be related to multiple AIs but not sure.
What did you expect to happen?
If I jump to AI core I can move my camera freely from the AI core.
If I track someone and move my camera it should be able to freely move from that new location.
If I track someone and move my camera I should stop tracking them.
What happened instead?
If I jump to AI core and move my camera my camera snaps back to it's original location
If I track someone and move my camera my camera snaps back to it's original location.
If I track someone and attempt to stop tracking them by moving my camera it continues to track them.
Why is this bad/What are the consequences?
Makes AI annoying to play.
Steps to reproduce the issue.
(Potentially) Be in game with 3 AI
(Potentially) Use a holopad at some point
Jump to core/Track someone
Hit any WASD key
Camera snaps back.
When did the problem start happening?
Not entirely sure haven't played AI a lot recently but may be releated to #25078 or one of the various bug fixes for it.
Extra information
No response
Relevant log output/runtime error
The text was updated successfully, but these errors were encountered:
Given a issue to this, general movement feel's sluggish at best, and is really annoying if it isn't instant like it's supposed to be. Your input feels like a big 500ms delay and if you stop moving your keys, it shoves you 1 extra tile into the direction you were going which is...???.
I've identified the cause of the bugs described in the issue description and have a fix in the works. This is a duplicate of #28089.
Given a issue to this, general movement feel's sluggish at best, and is really annoying if it isn't instant like it's supposed to be. Your input feels like a big 500ms delay and if you stop moving your keys, it shoves you 1 extra tile into the direction you were going which is...???.
This is a separate issue; I have observed it locally but have not yet identified the cause, but it likely originated with #25078.
Exploit Reports
BYOND Version
515.1647
Issue Description
When jumping to AI core and then attempting to move your camera it rubberbands back to your previous location.
If you attempt to track someone and move your camera your camera rubbersbands back to your previous location.
If you track someone and move your camera your camera will still attempt to track them.
Bug may be related to multiple AIs but not sure.
What did you expect to happen?
If I jump to AI core I can move my camera freely from the AI core.
If I track someone and move my camera it should be able to freely move from that new location.
If I track someone and move my camera I should stop tracking them.
What happened instead?
If I jump to AI core and move my camera my camera snaps back to it's original location
If I track someone and move my camera my camera snaps back to it's original location.
If I track someone and attempt to stop tracking them by moving my camera it continues to track them.
Why is this bad/What are the consequences?
Makes AI annoying to play.
Steps to reproduce the issue.
(Potentially) Be in game with 3 AI
(Potentially) Use a holopad at some point
Jump to core/Track someone
Hit any WASD key
Camera snaps back.
When did the problem start happening?
Not entirely sure haven't played AI a lot recently but may be releated to #25078 or one of the various bug fixes for it.
Extra information
No response
Relevant log output/runtime error
The text was updated successfully, but these errors were encountered: