The Issue
I am a game developer and I can no longer keep ignoring this issue. Upon trying to join any game in ROBLOX, website client of the application completely freezes, and takes 30 seconds or more each time to load a single frame. I have tried to reformat my PC and it still did not fix this strange occurrence. I tested on my other devices and they work completely fine. And yes, all of my drivers are up to date. There should be no issues with my computer, as ROBLOX worked for me up until around I believe October, before occasionally running into this issue, to now, no longer able to be playing ROBLOX entirely. This is very strange because when I try to play on the Microsoft store version of ROBLOX, it works perfectly fine, along with when being in-game using studios, there is no issue. When trying to run the game (the web application), it takes up practically no resources, like ROBLOX isn’t even trying to initialize. It only happens with the website version of the client. While I COULD use the Microsoft version, I have only ever used the website version, and, no offense to ROBLOX staff, the Microsoft version is still fairly buggy and slow. For the staff reviewing this post, I have privately attached all my msinfo32 information. Thanks for reading, and hopefully this gets fixed.
UPDATE 1: I’ve noticed comparing running roblox on my main PC versus another windows 11 device (that roblox runs perfectly on) that Windows on my main PC assigns the status “Efficency” to ROBLOX automatically in task manager, versus the one of my other windows 11 device where roblox does work. It may be something with Windows that’s bottlenecking ROBLOX. Not too sure…
This is what it looks like when I try to play games:
(Youtube link for if some reason you cant see the video: https://www.youtube.com/watch?v=DHvlP8YoRX8)
PC Specs:
CPU: Core i9 12900k
RAM: 64 Gigabytes of DDR4 Ram 4200MHz
SSD Roblox is installed on: Samsung SSD 970 EVO Plus 1TB
GPU: NVIDIA GeForce RTX 3060
Motherboard: TUF Gaming 7690 PLUS Wifi D4 from Asus
Internet Speeds:
A private message is associated with this bug report