- Home /
Is a variation of up to 40 FPS between sessions normal on standalone? If not what could be going wrong here?
Hey guys, seems like I manage to find all the weird ones ; ).
I’m used to working on the iOS platform so I’ve got to ask if this is normal? Like maybe hidden application background processes could be radically affecting the frame rate of the game or something. (Not that I normally get any lag from background processes.)
My scene in unity varies from 70 FPS average to 27 FPS average with EXACTLY the same objects active and placed, under the exact same conditions but during different play throughs of the same scene.
The variation seems to be triggered by me resetting the editor layout and/or activating then deactivating a water4 GameObject (Its always off again before I record the FPS, drop IS NOT because I’ve turned water4 on when before it was off.) However this doesn’t always change the FPS so it honestly could just be happening at random. I’m sure it’s changed after resetting unity sometimes as well.
Each sample represents an entire session in the scene. So for one play through it'll average 70FPS then another play through 5 mins later it'll average 27FPs.
I’m using Unity 5.1 p3 on an Intel MacBook and was encountering the same problem with earlier versions of Unity 5.
I have a pretty intense scene with a lot of geometry placed.
Static batching is active and saving a good 600 calls.
My lighting is baked, apart from ambient GI that is real-time.
I’m using Linear colour space.
I’m using Forward rendering.
I’m using the new standard material for pretty much everything.
Update: i've started using this script http://wiki.unity3d.com/index.php?title=FramesPerSecond to measure FPS rather then the statistics window and I’m now getting more consistent results.
Launching as a standalone application it'll run at high FPS just after my $$anonymous$$acBook is turned on, then after having its hardware exercised more by me stopping to do some editing in unity the same application will later launch at a much lower FPS and consistently stay around that low FPS, though occasionally increasing a small amount if I $$anonymous$$imise and maximise the app.
I can't explain why $$anonymous$$imising and maximising improves my fps, but the larger drop seems to be because of my macbook “being tired from working" which sounds kind of feasible. I suppose my only real option is to try and decimate the geometry some more so that my macbook doesn’t get "exhausted” to start with.
The built in FPS is sometimes a bit buggy.
But the best thing would really be to open up the profiler and check what out what takes so much time.
Of course there's also a possibility that other application slow down your $$anonymous$$ac Book, but I would start with checking the profiler :)