Author Topic: LateUpdate eating away performance  (Read 14092 times)

ivomarel

  • Jr. Member
  • **
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 53
    • View Profile
Re: LateUpdate eating away performance
« Reply #15 on: October 06, 2013, 10:38:17 PM »
Hey ArenMook,

This does not seem to decrease my drawcalls. Since I'm developing for mobile, 50 extra drawcalls is very expensive. Or am I missing something?

Cheers,

Ivo

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: LateUpdate eating away performance
« Reply #16 on: October 06, 2013, 10:39:18 PM »
One panel set to static, 50 widgets inside it.

ivomarel

  • Jr. Member
  • **
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 53
    • View Profile
Re: LateUpdate eating away performance
« Reply #17 on: October 06, 2013, 10:40:45 PM »
So I remove on widget and that requires all the geometry of 50 widgets to be rebuilt, correct?

Edit: Remove/move

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: LateUpdate eating away performance
« Reply #18 on: October 06, 2013, 11:00:28 PM »
Less posting more trying.

ivomarel

  • Jr. Member
  • **
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 53
    • View Profile
Re: LateUpdate eating away performance
« Reply #19 on: October 07, 2013, 12:09:14 AM »
Hey ArenMook,

Fair enough - I guess your great support made me lazy.

So concluding, the edit in my post was actually essential.

Removing a widget is fine, it works fine, even in a static panel.

Moving is a different story as widgets can not scale, rotate or translate while in a static panel.

I can work with this. I'll give every building a widget all in one static UIPanel, which I'll disable on tap, while enabling a separate widget (for only that building) which tweens.

Thanks again ArenMook for the great support!