Sometime before October 25th there was a change to terrain replication/initialization that has noticeably caused huge issues for our game where the entire game completely freezes for a short duration until Terrain has been fully loaded.
This was the post:
After a month or so, it appears that this must have been 2 separate issues because we are still experiencing this issue in our game to this day. We are still getting many reports from many users about this issue and we have no way of solving it. For some users with weaker devices, this can even crash the game entirely or take an excessively long time.
Video showcasing the issue: (resolution crunched due to size restriction)
I’ve done testing and removing all terrain completely fixes the issue, so for sure this is related to the terrain.
I’ve also tried reverting the game to older versions months and months before the issue started showing up and the issue is still presenting itself when running, so there has to have been a change in the engine that is specifically causing terrain to initialize like this.
During the state where the entire game is about to freeze for all the terrain to be loaded in, you are unable to use the roblox menu and console. The only source of information I can get is from the microprofiler, but it doesn’t show much, and dumping the results only seems to yield results after the big lag spike.
microprofile-20241123-182956.html (5.9 MB)
This issue might be related to the fact that we are not using streaming enabled. Thought I should mention that.
Edit: the creator of TWW mentioned their game has no streaming enabled and they also have very large terrain, and yet they don’t seem to have as bad initialization as us, so I’m not too sure why exactly this is happening anymore.
Link to game: