After a period of extended use, Play Solo begins to fail to load. This appears to be a macOS specific issue.
I have run into this issue several times. Some friends also on Mac have reported this happening as well.
The only way to clear it up is to relaunch studio.
Hello @Usering thanks for the report. We took a look by filtering for your placeId in our backend logs and it looks like there’s a chance that one of our services was experiencing issues for a short period of time which might have been the cause for this. Two questions:
Would you happen to remember the exact time and day when you and friends experienced this issue? This will help us compare with the timing of our logs to confirm.
I don’t recall any time specifically. But this post was made in the same afternoon that the issue happened for me. The issue did occur maybe 2-3 isolated times in month prior though.
This issue consistently happens to me for the past month, teamcreate or not. I am also a macOS user (15.2).
Workaround:
The only workaround is to close studio and reopen.
Other observation:
If you just close place and reopen the place, there is a chance that you could spawn in after an extended load time with a Noob skin.
We are continuing to investigate this issue. If you continue to run into it, please send in your log files privately from the failing sessions to help with debugging.
Also, if possible, please exit the broken studio normally rather than force-killing the process as that might cut off the end of the log file.
Thank you for providing the logs, and to everyone else who has reported the issue. Based on the information provided, Studio seems to be failing to create any network connections, even to itself on the loopback interface. This suggests the issue is in some interaction between Studio and macOS. Our existing logging hasn’t proven useful for understanding exactly why this is happening, and we haven’t been able to create a reliable repro of the issue internally yet, though we’re still trying.
Unfortunately we don’t have a root cause or solution yet, but I wanted to provide an update that we are still working on it. We may post here requesting more logs once we’ve added additional logging code to Studio, or if we have any update on the cause of the issue.
In the meantime, if you notice any patterns for when the issue occurs, such as always after waking your laptop from sleep, or always on the fifth Play Solo run, etc., please do share them here.
Has been happening to me constantly. Doesn’t have anything to do for me with leaving my computer idle or anything like that. Sometimes I click play and it works, other times it doesn’t. I did also notice however it keeps appending the date to the game name.
Same issue here, but on Windows. It happens every time I press Play, even after restarting both Studio and my PC. Team test doesn’t seem to work either. When I launch team test, the incident ID is 6425272072148345452 and the place ID is 86504767518318. I’m also having the same problem as Fizzy where it keeps appending my game name with the date. Run seems to work, though. This issue is happening in all of my games, not just one particular experience. They all result in ‘Failed to connect to 127.0.0.1|XXXXX; no response. Connection attempt failed.’ I uploaded a few log files to the dump page.