Yes i am constistently seeing this in studio in team create.
I’ve tried making a seperate place file with only the terrain but it seems to not happen when the place file only contains terrain and no scripts.
I’ve tried making a seperate place file with only the terrain but it seems to not happen when the place file only contains terrain and no scripts.
1 Like
do you have scripts that interact with terrain in any way? If you publish your duplicated placefile with only terrain to team create, does it still repro?
It seems publishing as a team create place causes it to happen.
Could you send me a private message so i can send the place file?
1 Like
I have sent you a private message, let me know if you don’t see it.
yeah i mean the test mode. also im not sure how to send terrain, if i download it, you cant reinsert it. i can send you a copy of my place though
ive had this happen aswell
noticed it happen for a day around may, but about a week ago it started happening every single studio playtest
ingame, and in edit mode the terrain is perfectly fine. its only playtest
i dont have any terrain-editing scripts
other devs on the same game have experienced the same issue
every playtest results in different “chunks” being gone
its not just visuals cuz players and physics objects do fall through it
though it seems fine if i switch to server mode
in my case, this is purely a studio playtest issue
hope this gets fixed asap, makes games like mine completely untestable
heres a edit mode/ingame vs during studio playtest
terrain.rbxl (6.0 MB)
heres my game place with just the terrain
i did 1 playtest and confirmed it still happens even on a downloaded copy
2 Likes
I am also having this problem, in studio itself terrain looks fine and without issue, but when I load into studio test the terrain starts breaking apart with random gaps in the chunks of terrain.
We have rolled out a fix that should prevent the studio playmode issue from happening after a restart. Please let me know if you still see the issue happening. The previously reported issue for client might be different, so please let me know as well if the issue persists