Terrain Trees causing slow framerate

Since upgrading to Unity 4.3 I am facing a big problem.

Even one terrain with only billboarded trees significantly slows down the framerate. I dont use any Occlusion Culling btw. It was not neccessary.

I tried varying the terrain values und reimporting the used tree assets. No luck.

I really need help because I can't downgrade to Unity 4.1, loading a scene with an older version ends in a deadlock.

Edit: Also started a complete fresh Project, added a terrain to the scene, placed trees, set billboard very low, set max mesh trees to 0. The result is still the same

If I downgrade this fresh scene I get 999+ errors with the message:

typeTree.m_Children.front ().m_Type != SerializeTraits<SInt32>::GetTypeString (NULL)

Maybe this helps a developer to reproduce?

 

I appreciate any help, any hints, any advice! As long as this is not fixed, I am stuck. I can't make a dev build because the framerate drops to 20 fps on a pretty powerful system (i7, amd 7870, 8gb ram) because of this bug.

 

If you can't downgrade and you want to use the terrain tree system, I don't think there is anything you can do but wait and hope it gets fixed soon.

 

Well, I would like to know if the devs know about it... But apparently they don't care.

 

Yeah, can we have confirmation that this is being dealt with?

Thanks

 

Thanks for your help Griautis,

with bug report you mean a small scene to reproduce the problem?

 

Is there a bug report for this now?

 

7

 

Make sure to vote to fix this bug: http://issuetracker.unity3d.com/iss...change-when-changing-the-max-mesh-trees-value

 

Wrong bug. This one is so much more debilitating than that one.

 

If it's a different bug you should add it; I assumed it was because the number of mesh trees was too high.

 

Not sure how a person would create a test scene that will show you the performance drop between versions (which is what people are saying has happened).
http://forum.unity3d.com/threads/224212-Max-Mesh-Trees-setting-broken
It doesn't have much to do with max mesh setting being broken though, as you can set the billboard start to 5, and it still performs poorly.

Unity should just run one of their own demo scenes that contains trees. They can compare the performance between 4.3 and an earlier version, like 4.1
I'm guessing that 4.3 performs worse.

I tried reproducing this on a flat terrain and massplacing "BigTree", but for some reason unity wouldn't give me the correct stats, it's like they were they were being throttled.
It kept saying I was running at 60-70 fps whether I had anything in the scene or not, so I was not able to measure difference in such a simplistic contrived scene to see if I was getting a performance drop.

 

Thanks alot, these were my exact thoughts about that, too. I just created a bug report without a sample project or something like this. I added the profiler screenshot I showed in this thread. But so far no answer or anything else...

 

You could try replacing the trees with models as a work around.

 

You probably had VSync turned on in the Player properties.

 

Where can I find the case number? I haven't received any email.

@NA-RA-KU: Could you try to create a test scene with VSync off and send another bug report? Maybe it works this way. I won't be on my computer with Unity for a few days, that's why I ask.

 

Case number 596894

 

Ok just saw the mail in my spam folder, sorry. If it helps, case number is 595705

 

@Griautis: Could you confirm that you guys are dealing with it?

 

Great news! ^_^

Thanks for letting us know

 

Yes, great news! Thank you

 

Can we get this fixed for the next version? The terrain tree system and all related bug fixes are largely rendered useless when there is really no way around this particular bug strangling the FPS.

 

So still no fix in 4.5?

Damn...

 

I haven't tried 4.5, but I didn't see it in the list of fixed bugs, and on issue tracker it's still marked as "active".

 

Really, I don't get it... IS EVERYONE experiencing those heavy performance drops and Unity just worked a few months on an update and NOTHING happened?

Still, a complete fresh project in 4.3 or 4.5 with just a few trees need calculations around 3 ms even with billboard only.

 

I kindly expect an answer from a Unity Dev.

 

Bump

 

Bumpety bump

 

Thanks for letting us know that you are still working on it. Unfortunately I don't use any shadows and the problem is still there.

 

I feel your pain and I've been documenting this issue and testing against it since version 4.3

I just wrote a new post about IOS terrain tree issues here: http://forum.unity3d.com/threads/ca...ree-bug-is-fixed-unity-4-3-and-higher.259116/

Please take a look and add your vote to this bug if it's affecting your game development:

http://issuetracker.unity3d.com/issues/terrain-tree-culling-performance-regression