4.3 Standalone Builds Really Poor Performance

It looks like quite a few people are noticing a performance drop on PC builds in 4.3

To test this try the following CubeMark builds.

CubeMark 4.2 - https://dl.dropboxusercontent.com/u/19148487/CubeMark/Unity4.2/cubemark4_2.zip
CubeMark 4.3 - https://dl.dropboxusercontent.com/u/19148487/CubeMark/Unity4.3/cubemark43.zip

CubeMark thread - http://forum.unity3d.com/threads/151813-Unity-Benchmark-v0-1?p=1426634&viewfull=1#post1426634

 

We have the same problem here, Windows standalone builds runs painfully slow.

 

Do you have a bug report number of this issue?

 

Vote on the issue in the tracker http://issuetracker.unity3d.com/issues/build-performance-drops-after-building-in-4-dot-3

 

vote 10 in the tracker... but one thing i want to know... should we wait 3-4 months for the next release of unity to get the problem fixed or unity is preparing a patch... does anyone succeed to contact unity and get information about the problem and when is going to be fixed because this is not an issue but major problem... the only answer we got from the support was that we need to provide a bug report number or something (i cannot call this just a bug) and nobody gives us information... building and testing a game with such a performance 15 fps (about 100 in 4.2.x) is not possible... but waste of time and this concerns everyone... hope we wont have to wait much time

 

You can roll back to 4.2, and build from there, otherwise it's just waiting for UT to find fix and re-test and release an update.

 

usually pre-made public scripts in my experience always have errors on the run-time, those errors decrease your frame-rate.

 

I also voted 10/10

 

I'm having the same issue, ive been tearing apart my entire project trying to figure out what magically ruined my performance

I then remembered the only major thing I did was update to 4.3

 

Just tried this.

16k cubes at 60fps on build 4.2
4k cubes at 60fps on build 4.3

So Unity 4.3 is a 4x performance drop.

 

This was wonderful and gave me a big sigh of relief. Ill have to halt my public alpha tests until 4.3.1 :\

 

Awesome thank you for posting this, I just used all of my 10 votes for this issue as well. Seems there are a few of us that got caught out making the assumption everything was fine because it runs fine in the editor. Everyone please go and vote on this issue to bring it to the top, it's current priority is only a 7 I hope that is an actual indexed queue and not a scale of severity because IMO this is a show stopper.

 

good news : ) thanks..... : )

 

Great to hear! nearly 80% of my testing base is unable to run the 4.3 builds at a playable rate, everyone is looking forward to it

 

~20k on 4.2
~20k on 4.3
No difference.

But my real project runs 10 times faster in editor than as a build, like 190fps vs 19fps.

 

Are you on nvidia or ati?

All of my testers with ati reported severe fps issues compared to the last build, nvidia users also reported a hit but it wasnt as bad

 

Radeon HD6950, Catalyst 13.9, Windows 7 x64

 

I also have a HD6950 on Catalyst 13.1, Windows 7 x64. On the 4.2 build that we have I was getting 40fps and then 3fps in a 4.3 version.
Well the devs found a fix so it'll solve our problems.

 

The bug is marked as fixed already, but I haven't got my 10 votes back. Maybe I should send a bug report about the bug tracker.

 

Did it here; http://forum.unity3d.com/threads/212339-New-Issue-Tracker-Bugs-are-public

Maybe it's not at "Fixed" but once a build is released with it.

 

I can confirm, the bug is solved in 4.3.1. Just tested it.

 

Yep 4.3.1 gets a Cubemark of...

35,212 (4.3.1) - Cubemark 4.3.1 zip (PC)

11,820 (4.3) - Cubemark 4.3 zip (PC)

33,765 (4.2) - Cubemark 4.2 zip (PC)

So it's 104.285% faster than 4.2 on my PC.

 

Same for me. 4.3.1 Windows builds are back to normal.

 

I'm experiencing low frames per second with the project "Unity Projects 02: 2D Platformer", compiling for android with version 4.3.1 and the fps is very low . when running in OUYA. The movements looks jerky. Please help anybody with this issues.

 

My android project is performing terribly on 4.3.1 as well. Practically no batching is being performed whatsoever. The same project on iOS does not seem to be experiencing the same issues.

 

Editor feels really choppy in 4.3.1 on OSX Mavericks -- unity's framerate counter says 100+ but it feels like 15-20

edit: might be a photoshop problem. Noticed 4.2 didn't feel any better and was worried it was Mavericks. Closed everything else, then slowly opened stuff -- photoshop (CS6 sub) made a big difference.

 

I ran head long into this one as well.. Unity team, i think you rushed 4.3 out!

 

Wrong thread for your problems @rdelossantos, @foobar , @JTown; submit a bug report.

@ev3d; it should be fixed in 4.3.1.

 

New version out

 

My android project is performing terribly on 4.3.1 as well. Its impossible to run in nexus 7 more slow build.

 

Be aware that the terrain max mesh tree setting does not work: all trees will be displayed as meshes (only the billboard start setting works)

 

Our project is also performing horribly on Android 4.3.1. Our fps on Nvidia SHIELD is substantially slower than our 4.2.2 builds.

 

Hello,

I solved the error message Mismatched serialization in the builtin class 'Mesh' due changing the ProjectSettings | Editor | Asset Serialization | Mode force Binary. it only happens again if I convert back to text or mixed.


kind regards,


Peter Fonk.
Unity Pro 4.3.2

 

Ugh, having this issue myself and only just came across this thread. I've got an AMD graphics card running on latest drivers and a 144hz monitor, not sure if that might play a part, but the latest AMD drivers seemed to completely destroy everything for me (f.lux doesn't work anymore, second cursor on my monitor at the top left...)

Disabled OC and tried dynamic/no batching, both with little gain. Editor still runs a lot faster :|

 

Just to chip in, even though I am a basic user, I have been trying to figure this out today. In my gameview when running the game is 60fps, with drops to 30fps when things get really heavy. If I build the game, I get 40fps dropping to 12fps when things get heavy. I cannot through any adjustment seem to mitigate this issue. I tried reducing the clipping planes to be really low and moved relevant things closer to the camera, but to no avail. It is quite a basic scene as well, that only involves some spinning rocks and a couple of missiles. I cannot view the scene in build without an unplayable fps.


EDIT: Updating Unity fixed this issue for me. I was not on the latest build, so some bug with an older version. If you have this problem just update Unity.

 

I've seen this kind of frame drop in the IDE but it tends to happen when I hit an obscure repeating error showing up in the console window, when I was playing with procedural geometry.

 

If I change to Force Text, it gets rid of the errors for me. Thank you for your help. I've had this error hanging over me for days.

 

I've been having the same issue as the rest of you guys but I have found something that works for me that seems to fix it, but is far from ideal. And this may only be relative to myself, and it is quite obscure fix - but it may help elude to the real issue.

When I start seeing performance issues, I open NVidia GeForce Experience program.
While this is open, my issues disappear.
The second I close it, the issue reappear.

This wasn't happening at all during 4.2x and since this also has shown up in AMD cards, I'm not sure what to think.
Perhaps there is some settings in Player, Quality, or otherwise that isn't actually saving and is being freed/hampered by these types of enhancing programs when working with Unity.

 

I'm running 4.5.3f3 and seem to running into this problem. Is this def fixed in this release?

 

Check out the Unity Mark thread, I've been building standalone PC and Web versions of the benchmark with each release of Unity. It looks like the 4.5.4 release has dropped in performance for me at least from 70k to 64k Cube Marks. But download and run the benchmark to test for yourself.

Note the benchmark only tests 3d cubes and quads, not sprites.

 

Interesting, looks like I will be running this each release before upgrading my project. Cheers

 

OK Just give me a nudge if I haven't got the latest release built.