When running a Local Server Test in Studio, I often encounter many issues.
For example, most of the time, at least 1 of the clients (I test with 2 clients) encounters this error:
“Studio encountered an unrecoverable error and must shut down. Device encountered an error: Device removed”
However, the client will still remain connected to the game server until the Studio window is closed, resulting in weird behaviour like the character floating; essentially no client-sided things work for that client.
I often encounter other issues, such as:
Roblox Studio not responding/taking an excessive amount of time to respond
After closing a local server test, basic functions on my computer stop working, such as the taskbar. I can’t even shut down my computer 90% of the time, so I need to force turn it off with the power button, leading to more issues.
Roblox Studio will sometimes make my whole computer screen go black for a few seconds. When it turns back on, only the viewport is visible in the window and everything else is black. Stops responding.
This only happens when running a Local Server Test
Device info:
OS Windows 11 version 24H2
Processor 11th Gen Intel(R) Core™ i5-1135G7 @ 2.40GHz 2.42 GHz
Installed RAM 8.00 GB (7.79 GB usable)
System type 64-bit operating system, x64-based processor
It’s also important to note this issue will only happen on places with the amount of assets a standard game would have, i.e. it is not reproduceable on an empty baseplate.
Expected behavior
Roblox Studio should not crash. It should also not break my PC.
I tried to upload the relevant crash file, but it was too big for the forum.
This behavior is abnormal, and the culprit is most likely in graphics driver/HW. The error string you’re getting is coming from the graphics subsystem and most likely the driver halting and rebooting (hence “device removed”). When doing a client server test, you’re tripling the amount of video memory used for textures and such. My immediate guess is that you’re starving/overloading something in that area. Do you have a dedicated GPU or integrated graphics? How much memory is available to the GPU (either dedicated or shared)? At a certain point, if Studio can’t allocate VRAM it will fail - typically we do not fail gracefully in this case but crash and report. A set of logs (one from edit/client/server) from a case where this occurred might help indicate what the actual crash is and provide additional information, so please send that over.
Always a good idea in any case to update drivers in case the driver is the source of the issue, but I’m leaning towards resource starvation since it doesn’t sound like this occurs in a Play Solo session or just editing. Team test is by far a more expensive option for testing, so the more clients you have the beefier the HW that’s needed to run it.
That said, I’m suspicious of the other symptoms like the task bar disappearing - this indicates the graphics session is compromised - odd things can happen if the driver is wonky or you exhaust the memory.
Also, its most likely unrelated, but make sure you’re windows patches are up to date - there has been a lot of chatter about 24H2 and some HW. You can also try disabling the “Optimized for Windowed Gaming” setting - but its a bit of a stretch and not sure that would be related here.
I use integrated graphics (I’m on a laptop) and there is 3.9GB of memory allocated to it. I also updated my graphics driver to the latest version (here) and the issue still persists. It might also be important to note that Windows appears to stop running executables after this; I compiled an executable a while back which has the sole purpose of restarting my computer, and that only runs about 50% of the time.
While the “Optimized for Windowed Gaming” setting is enabled, under app exceptions, Roblox Studio had it disabled, so I don’t think it’s relevant.
As for the log files, I’ll private message them to you.
Yeah, this is for sure at the driver level, as indicated
DXGI_ERROR_DEVICE_RESET
which is where Studio hits a fatal error.
After that, the system may recover, or it may not depending on what’s driving the error and causing it.
I think the thing to do here is narrow down exactly what’s triggering it on your end. Some things to try:
If you have a pretty good repro, try reducing the Studio Settings → Renderer → Editor Quality Level from Automatic (which actually just pins it to max, a bug we’ve discovered) to a low level value and see if the repro rate is affected.
Similarly, starting from base plate, see if there’s any specific asset in your place that causes the issue. Does this happen on a very specific place/asset, or just with any “complicated” scene - check out some of the heavier templates and see if it occurs there.
Just to set expectations, if there’s not a specific thing we can pinpoint triggering the driver, i.e. some bug with a texture/asset/shader that the renderer is failing on with your HW, then it could be a HW problem or driver issue out of our hands.
The log is littered with texture errors when it starts to go bad, and all of them pointing to the driver closing up shop and resetting (887a0005) - this wouldn’t be exclusive to Studio by any means.
Other things to try - does the place run fine under Player? Is it only with three copies running at the same time that you get the issue?
Does any other game give your an issue (Roblox or not) that you’ve seen?
For my place experiencing the issue (Universe ID 5540431734)
I’ve discovered that the issue starts occurring on my place at Studio Editor Quality Level 8
It doesn’t happen with only one player in the local server test. I’ve had rare cases of both clients throwing the error, but not in a while.
Doesn’t happen on a standard play test and also doesn’t happen in the Roblox Player
Confirmed driver issue on my end too, a more verbose error “Studio encountered an unrecoverable error and must shut down. Device encountered an error: the device driver encountered an error”.
I’ve tried this:
On the FPS template: One client showed the error
On the Racing template: One client showed the error
On a blank baseplate: One client froze, but neither clients showed the error
This does not happen on any platform except for Roblox. I’m not sure if it’s related, but there’s been a couple of games that will rarely crash Roblox when I try to join them, mostly Flood Escape 2 and Blox Fruits (although I haven’t played Blox Fruits in a while and was unable to repro it when I tried to, so not sure on that one)
After you said it might be a driver issue, I was slightly concerned about this. However, I think it might be a Studio issue because this doesn’t happen on any other platform (as I said before) and I can run other more resource-intensive games such as Minecraft without issues.
So the key here this doesn’t happen on Studio either unless you are running multiple windowed games at the same time, which is a local client server test. Since its not place specific, I think HW/driver has to be the suspect here. You could try to reproduce this outside of Studio by running multiple programs/games utilizing the GPU - Roblox, another game, maybe a third one for good measure. The heavier the better just to stress it.