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
In Grubs, we have run into an issue while playtesting:
Players join
The game starts
Grubs are spawned
The [Sync]'ed public Vector3 Velocity { get; set; } is equal to {0, 0, 0} on the host, since the Grub is not moving.
On other clients, we see an incorrect value on the Velocity, until the Grub moves.
This is annoying, because we check a Grub's velocity to determine if things are resolved, which lets us move safely to processing the damage queue and moving on to the next turn.
As a workaround, I have attempted to use the Query sync flag, in case somehow a stuck value just doesn't get set on other clients properly, but this did not fix the issue.
The value is still CORRECT on the owning client. But it is incorrect for other clients.
Here is a video of me reproducing the bug locally. The host owns Wormbert Jr, and the host shows the Velocity as 0. But the second instance sees Wormbert Jr's velocity as roughly (-5.6, 0, 0).
Describe the bug
In Grubs, we have run into an issue while playtesting:
public Vector3 Velocity { get; set; }
is equal to {0, 0, 0} on the host, since the Grub is not moving.This is annoying, because we check a Grub's velocity to determine if things are resolved, which lets us move safely to processing the damage queue and moving on to the next turn.
As a workaround, I have attempted to use the Query sync flag, in case somehow a stuck value just doesn't get set on other clients properly, but this did not fix the issue.
The value is still CORRECT on the owning client. But it is incorrect for other clients.
Here is a video of me reproducing the bug locally. The host owns Wormbert Jr, and the host shows the Velocity as 0. But the second instance sees Wormbert Jr's velocity as roughly (-5.6, 0, 0).
To Reproduce
Expected behavior
Synced values are accurate, especially when using the Query flag
Media/Files
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: