Thanks for the new 3.4 release.
All works fine except that when displaying the statistics screen (top right of game view) in 3.3, my build showed 1.8ms/frame and now with the 3.4 it’s showing 11.4ms/frame.
I did not change anything. I only upgraded Unity from 3.3 to 3.4. The game looks like it’s running at a fine speed but I’d like to know if the information shown in the statistics is accurate.
Also, some physics that worked fine using a configurable joint in 3.3 don’t work anymore in 3.4. I have an awkward behaviour now. I fixed it using RigidBody constraints, but why was it working before and not anymore?
Same here…
Looks like the frame rate is capped at 60-70 fps. I know the framerate was always “fake” and broken… however it did give a good representation of fast the game is running nevertheless. Now I have no idea if there is a change in the 200 → 400 fps range as before.
Edit: Checking the profiler… the game is running at 1->2ms 400 to 600fps. Looks like something in the stat window is adding 10ms to the whole.
You’re right, I just tested with an empty scene and I still get 10ms/frame.
I get this problem too. At first I thought I’d just made a change that totally slaughtered my framerate, and scrambled through my code to see what I might’ve done. O_O
I think the framerate it’s locked at looks like VSYNC is enabled. It’s hovering just above 60-ish, like it’s trying to match the monitor’s refresh. I tried to make sure VSYNC was disabled with ATI’s Catalyst Control Center for the graphics card, but that didn’t help. Really curious about this.
Found it. This is VSYNC related, as I expected.
There’s a quality setting in the new version that turns it on inside the editor. Go to Edit->Project Settings->Quality. The default for the Editor Quality is set to “Good”, and if you open “Good”, you’ll notice that VSync Count is set to “Every VBlank”. Setting that to “Don’t Sync” gives you your normal FPS back in the statistics window.
It might give you screen tearing too, of course, but…
I have Don’t Sync all the time and since 3.4 I am getting totally wrong framerate. Profiler is showing correct values, but usually profiler itself takes lots of performance down, so I prefered that simple window.