-
- golgepapaz
- Posts: 43
- Joined:
poor performance of noesis calls.
I am drawing buttons that move with objects in unity and turning them on or off if whether they are visible
by the camera. I discovered much to my chagrin that this is very costly as shown in the highlighted sections of unity profiler capture below.
I am using canvas.SetLeft() and setTop() for moving and SetVisibility() for turning on/off the buttons every update. I am guessing there is a better way to this?
by the camera. I discovered much to my chagrin that this is very costly as shown in the highlighted sections of unity profiler capture below.
I am using canvas.SetLeft() and setTop() for moving and SetVisibility() for turning on/off the buttons every update. I am guessing there is a better way to this?
Last edited by golgepapaz on 05 Mar 2014, 09:42, edited 1 time in total.
Re: poor performance of noesis calls.
We haven been reported that calls from c# to c++ take too much time. We are investigating this issue. We are going to change a few things to improve the performance. Anyway, it is always important to consider:
- Avoid redundant calls as much as possible. If an item didn't change position in a frame don't set it again. If the visibility didn't change, the same...
- To improve stability and error checking, the perfomance of NoesisGUI inside the editor is worse than standalone (in fact, they are different Dlls) Could you repeat the benchmark with a standalone executable?
-
- golgepapaz
- Posts: 43
- Joined:
Re: poor performance of noesis calls.
As of 1.1.5 there is a great improvement (up to 20 times) in editor although still not comparable to standalone mod. I wonder is it possible to use standalone dll in editor time ?
Re: poor performance of noesis calls.
Yes, we improved a lot the error handling mechanism inside the editor in v1.1.5. Although it will never be as fast as standalone because inside the editor our priority is avoid crashing Unity. Under your own risk you could copy noesis.dll from the plugins directory (the standalone version) to the editor folder (although with this hack you won't be able to build). We could even add an "unsafe" setting to do this in the future automatically.
Having all our math types (matrix, point, rect..) as structs instead of classes will also help to reduce this problem. This is planned for noesisGUI v1.2
Having all our math types (matrix, point, rect..) as structs instead of classes will also help to reduce this problem. This is planned for noesisGUI v1.2
Who is online
Users browsing this forum: Google [Bot] and 7 guests