I get an error whenever I try to local server test, using:
Server loads and works normally, but both players receive this error after some seconds of loading the place’s data model:
Attempted solutions:
- Re-installing Studio.
- Disabling all plugins.
- Re-starting computer.
- Re-starting Studio with all beta features disabled.
This seems to only be a problem with myself. Team Create is enabled in the place and the collaborators don’t get this error, they can local server test just normally. Place is held under a group - we also have a private indev place, and I get the same error on it as well. Tried downloading a file of the place, opening it, trying out local server test again, and same error. I have had this issue since yesterday, maybe the day before yesterday too.
System information:
CPU: AMD Ryzen 3 7320U with Radeon Graphics
Memory: 8 GB
GPU: AMD Radeon™ Graphics
A private message is associated with this bug report
UPDATE: This is likely a system/device corruption error? I tried doing a local server team test on an older laptop, same place, and it works correctly. I remember that on some testing sessions on my newer laptop - the one this issue is ocurring in -, my device crashed sometimes due to running out of memory or other errors. I don’t remember what happened before this issue started occuring, but local server testing used to work just fine on my new laptop. My theory is that crashing corrupted the data in some way and led to this issue. I will attempt a studio re-install from scratch and update accordingly.
Nvm it worked just once on my laptop and then it broke again, I have no idea what’s causing this issue
Do you get the same error when doing client server test with a single player?
Hello. As of today, this issue seems to have been resolved for me, so I’m not sure. I’m unaware of a Studio update or some internal change that might have fixed it. I found an X post of a developer having the same issue around the date I was experiencing it, and commenters said they encountered it too. I will mark this report as solved, although I’m not sure it was globally fixed.
