Error Loading PlaySolo issue but not in Team Test?


Ok so this issue happens when I try to solo test the game. It takes a bit and tries but eventually fails


BUT this issue does NOT happen on team testing?.. I dont know why my studios acting this weird, I havent tempered with any files, sent logs on the private.

Expected behavior

I expected it to run the game on solo…

A private message is associated with this bug report

5 Likes

No no, there are differences.

1- The OS is Windows, Not Mac
2- The Error happens ONLY in local play, in that post it happens for both

This is not a duplicate. A studio engineer asked me to explicitly reopen this because it being locked was preventing them from addressing.

Please allow engineers and/or original poster to do the determination of whether a bug report is a duplicate or not. Thank you!

i’m having the same issue on any project i try to playtest, its not specific to one (using windows11)

Im having this issue on Windows 10 but if youre having it on W11, that means this is an error caused either by roblox-side or an update that was released in recent time. I cant know for sure but i hope it would help the engineers to understand

Btw I should note this down.

I am turkish which forces me to use VPN in order to access roblox and its services. It might be a leading factor.

Most likely, your VPN is the issue. I got the same error in Studio when I tried to solo test on a baseplate. However, when I disabled my VPN, Solo Testing worked fine.

update: upon reading the comments, its definitely vpn related. i use nord vpn and as soon as i turned it off it worked… weird

I cant test cus I cant connect to Roblox Studio without a VPN…

Can this be resolved and allow VPNs to use solo testing?

THIS IS STILL HAPPENING IN THE NEWER UPDATES
Can it be fixed please, bump.

This does not seem to be VPN related as I am having this issue without a vpn & not in a country that blocks Roblox

Odd… Only if we knew which engineer is looking over to this case so we can speak to them directly

It seems it was because my Network replication lag was too high, so my mistake!

What do you mean exactly?? can you tell me how you fixed it??

it was probably only on my side but I accidentally set the network replication lag value to a very high value