If you have a lot of water in studio, and you move the camera with the mouse, you will drop significant frames. This only happens if there’s water and you’re moving the camera. This obviously makes it practically impossible to do anything that involves the viewport.
Interesting. I don’t know if this is related to water - for some reason some frames are very very long with no activity, almost as if something is delaying next render frame in Studio. cc @Silent137 in case this has been observed before
It only happens when the file has water in it, but it used to happen if you go into play solo, though I haven’t personally seen that behavior for a few months.
@Silent137 This is now happening with every place file. It might have been doing this at the time of posting this thread but I didn’t notice because I was only working in the water place.
I seem to be having this issue, but it’s not consistent. Sometimes it’s happening, sometimes it isn’t. When it’s happening, I can face the camera to the sky and move my mouse around to drop my FPS as low as 30 FPS (from 60 FPS).
Here is a microprofiler dump from when I caught it happening last time. Shortly after this it stopped happening again.
I’ve been experiencing this for a while now. I think it started around the time (or when) the new studio start screen came. I always assumed it was just because I’m using a toaster.
For the benefit of anyone finding this thread while searching for a fix, I experienced the exact same problem today after a mouse driver and software package update. In my case, SteelSeries engine and Rival 300 mouse. The issue was that the new software set the mouse input polling rate to 1000Hz, which totally overwhelms Studio in Play Solo whenever moving the mouse. Symptoms are identical to Sharksie’s video. Setting polling rate to 125Hz completely fixed the issue.
