Today, I’ve opened Roblox Studio and tried to update a game, but there’s this mild inconvenience of a bug which doesn’t let me to drag and drop instances. I have no idea when this started happening since I’ve micro-quit using Studio for a while because of constantly getting 20-40 FPS with DirectX since Vulkan just instantly crashes studio all of the sudden.
(derailed tangent about the low FPS)
At first I thought it was the memory management of plugins, but after it was fixed it persisted so I had no idea. A workaround to this is by disabling the integrated GPU, but that destroys overall system performance since the integrated GPU isn't available to help the dedicated GPU with background tasks using a GPU, like DWM and RGB lighting service, so I just have it enabled. I have no idea if it's just my system or if other people are also experiencing these bugs. Let's just focus on this drag and drop bug for now.
While I can tolerate the choppy FPS (which still happens today), the inability to drag and drop in explorer annoyed me a lot.
Here’s a video of it happening.
I’m using the latest version of Windows 11, drivers, Studio, etc.
Here’s my system specs:
OS: Windows 11 Home Single Language 25H2
RAM: 16 GB
CPU: 13th Gen Intel(R) Core™ i7-13650HX, 2600 Mhz, 14 Core(s), 20 Logical Processor(s)
GPU0: Intel(R) UHD Graphics
GPU1: NVIDIA GeForce RTX 4050 Laptop GPU
Beta features:
glTF Export
Improved Find All/Replace All
New Video API
Next Gen Studio Preview
Proximity Prompt Indicators
Expected behavior
I expect for this drag and drop bug to be fixed. A fix for the low FPS bug is unexpected but is welcome.
whenever I am extracting an archive into the HDD, the same concept applies… closing the docked windows at the left fix spikes, though in this case the spikes also fix themselves once the archive finished extracting, but that’s really strange
however, despite no spikes, the dragging still doesn’t work while the file archive is extracting
So this doesn’t make any sense
Why does this issue happen? The next thing I am going to accuse is the Windows file tranfser progress window.
Doing a while loop will not be able to re-produce this issue… something else has to be under load.