Yes, you are correct, but zavatarteam2
is still unlocked, also they do exist it’s only that they have only been locked down for Roblox staff only.
Only a select few channels were locked.
Let the poor guy have a break? I’m sure other engineers are sliently working on the issue
Also have you tried the following:
- Unplugging all hardware apart from your keyboard and mouse to verify the crashing isn’t caused by other non-essential peripherals
- Make sure to not enforce the Player to use the Vulkan rendering API via FastFlags
- Make sure you have quit out of Bitdefender fully (If you have it)
- Make sure you have unplugged any Logitech steering wheels as it has been confirmed to cause crashes (If you have one)
- Quit out of non-critical processes and try again
- Go into Task Manager, disable most if all applications on start-up and restart your machine to try again
- Changing your deployment channel to
zavatarteam2
or other (Has been confirmed to fix SOME instances)
If all else fails, check if a crash dump has been generated, these strategy steps are very helpful.
Send your crash dump to @Bitdancer via DevForums direct messages, remember to:
- Do not directly upload or link your dump publicly, to anyone other than Roblox staff
- Crash dumps will be massive (We are talking 5 to 1 GB) be sure to upload them to a file sharing platform like Google Drive
- Make sure that only people with the link can view and access the file so Bitdancer will be able to download the crash dump without issues