When playtesting in Studio Play Solo, assets take abnormally long to load (1-2 seconds per request in the queue), and I believe as a result, using :LoadCharacter takes extremely long too.
This does not occur in the live game on Roblox, and loading takes less than 5 seconds consistently (data, framework and character). When checking with fast.com on my most used browser, I consistently get 800-900 mbps internet speed (I use ethernet connection).
I have attempted reinstalling (not clean, I have plugins I’d like to keep) and restarting my computer.
Assets loading extremely slowly, as well as footage of :LoadCharacter being waited for)
A successful :LoadCharacter call taking 27 seconds
Test setup and reproduction steps
I ran studio without any plugins enabled
Disable CharacterAutoLoads and create a server script:
Press Ctrl + Shift + F3 to view the request queue size
System info: Microsoft 10 Home, Intel i7-9750H, Nvidia RTX 2070, 16gb RAM
Beta features: Dragger QoL improvements, EditableImage and EditableMesh and New Audio API
Expected behavior
I expect assets to load significantly faster, and possible even cache like a normal Roblox play session rather than completely reloading on every playtest. I also expect LoadCharacter to perform faster and not be directly tied to asset loading (which is what I’m assuming is happening).
This might be related to a problem I’ve previously encountered:
It was happening because IncomingReplicationLag kept being incorrecly reset to 10 instead of 0 each time Studio was started, and amusicalzebra found a way to fix it:
Unfortunately no, I did check the IncomingReplicationLag setting before posting the bug report and I set it to 0. I checked the GlobalSettings_13.xml file too like in your topic, and even there it’s 0. Still extremely slow.
Unfortunately I’m away from the device where this issue was occurring, and I can’t replicate it on my other computer. For context, I don’t believe the device is the issue because the Roblox player and Studio editing loads at normal speeds.
I will send a log when I get back in a few days. Thank you for the reply!
After testing more on the original machine, it seems like the issue is resolved. I am still not sure what could have caused this, but I’m increasingly convinced it’s something on my end (though I haven’t installed/uninstalled or changed any relevant software on my device).