For people who do experience lag & high CPU usage, mind posting the profiler dumps and screenshots of Windows Task Manager with “logical cores” information enabled?
To get profiler dumps:
Press Ctrl+F6 in-game
In the menu, click Dump and pick 32 frames
Look in your C:\Users\username\ folder - there should be a microprofile-…html file there.
On a serious note, I never experience any of that on my computer but mine is biased cause its pretty tuned out, crossfired 2x R9 290’s on an i7. On my iPad however Plaza runs fine of course at lower graphics settings but still good FPS…
I’m also getting reports from some people that the game freezes up for them or very low FPS as they join the game. It seems to become better when they’ve been in the game for a bit.
I have had this type of issue since day one of CSG streaming. It seems like loading takes a lot of CPU utilization away from the game (with a 60 FPS game going down to 15 FPS not being rare).
I’ve actually been getting the CPU problem now, but it’s strange:
To add on to the problem I previously had, I figured out why ROBLOX wasn’t using my GPU:
When launching through Firefox it would just use the integrated graphics. It would completely ignore the GPU being there. However launching through chrome seemed to fix it. This might be a completely unrelated bug (and it could just be Firefox) however;
Whenever I launch through chrome, I get the CPU killing problem. It only happens for the first 5 or 10 seconds after I launch the game. So that probably verifies it’s GPU related, (and if not the case, browser related).
Could we get a fix for the browser-gpu issue as well (or if it’s not the fault of ROBLOX, get instructions on a fix for Firefox)? Launching through Firefox means that I can’t get the GPU working to play games and develop.
I don’t know what exactly the issue is here - we only give the graphics driver a hint as to which GPU to use. I don’t know what specific hooks it has into the system - maybe when FF launches the game it does not take that hint, since FF and Chrome use different launch flows.
However, we are migrating to the same flow we use for Chrome in FireFox as well - so if this is the case this should be resolved in the coming month or so.