Is this still occurring? I tried enabling a physics replication change for a subset of users and reverted it after about 45 minutes due to issues I was seeing. Do you have a link to your place?
Yes, it’s currently happening. Here’s the link: Chicago: 1949 - Roblox
Thank you, I am looking into it. I’m sorry this is happening to you!
No worries, I’m happy to know that it’s a bug with the engine and not another DoS attack. Thanks for the quick response!
We are also seeing issues with vehicles at our game and network spikes.
Even though the timestamps don’t line up with the original report, I believe my change caused the problem. It’s already been reverted but will only take effect once people restart their clients. Would you mind restarting your servers?
Do you know about when it started?
We received a wide influx of reports on July 12, 2021 5:50PM EST lasting until around 6-7ish. After that point, it seemed to have settled down but we received a large number of reports again today at 5:57PM EST until present.
This seems to be a large scale issue around most Roblox servers, I have an application that tracks latency, I started receiving reports of latency issues a couple minutes ago: I have no idea if this is related or not but dropping it in here in case it’s relevant.
Looks like it might be unrelated to the physics change and just a coincidence. I’ll leave it here but it doesn’t seem to be related.
It could have been later, I started getting most of the reports between 5:45 PM and 6:15 PM I believe. I will restart all servers to see if it alleviates the issue.
@FxllenCode That should be completely separate, but thank you for chiming in!
Just to confirm: this is after the restart?
Yes, I shut down all servers and have rejoined since you advised me to. This is a brand new server started minutes ago.
Got it. Can you try restarting the servers one more time? I tried something else.
Edit: Coming back to this to offer a little more explanation. For this type of networking change, clients need to restart for the change to be reverted, but mobile clients don’t restart when joining a new game (only closing and opening the app counts as a restart). So I had to make a change on the server-side before the revert would fully propagate to all the clients.
I only became aware of what was happening about an hour ago and it looks like the issue is already mostly resolved, but I’ve been having serious issues with this on my game in older servers. Players and NPCs(which are server-owned) are constantly hanging for 10 seconds or more, but attacks still register. I would like to point out that I am extremely supportive of changes to physics replication—there are some replication issues that have been crippling certain aspects of my game since I launched it, for example creating explosions near players often leaves tons of sleeping physics parts stuck in the air, so it would be amazing to see replication issues like that get fixed. However, my game has a concurrent player count around 40% lower than what I would expect it to be at this time of day and old servers are completely unplayable. I have not shut down my servers, but new servers don’t seem to be having this issue as far as I can tell. Thank you for responding to this issue so quickly!
It appears to be fixed now. If it happens again I will update the thread. Thank you for the quick response to this, I really appreciate it!
At this point restarting should fix any issues with physics replication, I’m incredibly sorry for the interruption to your places! This change was tested and QA’d, but we obviously missed something. I might reach out to you to get some of your models and scripts if I can’t reproduce the issues on my own.
Thank you for helping debug this!
I don’t know whats happened but same issue here every things laggy
I’m sorry to hear you’re experiencing lag! The specific problem the original post was referencing has been resolved. If you’re having a separate issue please file a new bug report. You can find instructions here: How to post a Bug Report.
If you’re having trouble collecting the information needed for a bug report feel free to DM me.