I’ve spoken with several other friends who are currently experiencing the same problem, havent seen any posts on it so I figured I’d post something.
I selected a game at random, but just walking around for a few seconds and it instantly crashes.
Game Played: Survive A Week In The Winter - Roblox
System Information:
64gb ram
i9 10850k
nvidia geforce rtx 3070
Expected behavior
the games not supposed to crash
this seems to be happening to everyone
im having the same issue, for now im playtesting in the roblox page.
Finally a proper thread.
Yeah, recent update seems to break things, waiting for the hotfix.
Cant Playtest or just use Roblox app
Can confirm it’s happening, and it seems to be on other platforms as well, not just PC.
I’m experiencing the same thing. Pretty sure Roblox just pushed a bad client update. Whoopsies, I guess.
I’m experiencing this as well.
It’s doing it for me too, and SEVERAL posts are currently discussing this.
By experience, It might be the Hyperion crashing the client (false positive).
I thought so! Haven’t seen anything on the engine bugs so I figured I’d post something.
It’s a server-wide outage. Everyone else is confirming and Roblox is most likely aware. Just another day on Roblox.
I think its fixed now, everything is working again for me
somewhat glad to hear im not the odd one out with the issue
hope they will fix it soon
Can confirm as well.
(also can we fix the c++ error that can randomly happen in studio too while were at it, im going insane, both studio playtesting and playtesting manually on the actual app both don’t work now so i have no way to test anything, actual nightmare fuel)
same issue right now currently happening
recent update seemed to cause not just crashes for me honestly
it started like yesterday when roblox just stopped responding to any inputs, even to something basic such as alt+f4
It’s now fixed, that was fast 3
seems to be fixed now, didnt take long
Hey all, thanks for the report. Our engineers were alerted to the changes as soon as they happened a couple hours back and resolved it quickly as you have noticed.
Closing out this bug report since this issue has resolved.
