Slow frames when enabling panels with many widgets

[ArenMook]

How so?

Widget
- Scroll View
-- Panel (constrained)
--- Sprite

Set widget alpha to 0, hit Play, move widget alpha to 1 -- it's visible. Use TweenAlpha instead -- same, it's visible.

[helmesjo]

How so?

Widget
- Scroll View
-- Panel (constrained)
--- Sprite

Set widget alpha to 0, hit Play, move widget alpha to 1 -- it's visible. Use TweenAlpha instead -- same, it's visible.

Hmm... Try this setup (which is pretty much exactly the same without the "noise"):

- Panel (constrained)
-- Widget A
--- Widget B
---- ScrollView horizontal (clipped)
----- ScrollView vertical (constrained)
------ Sprites & Labels

Set alpha of the Widget A to 0 in Awake (i do it in another component than UIWidget, if that matters when you debug), then back to 1 (again, done from script but that shouldn't matter.

Sorry, don't have time to create a repo atm but that is the current hierarchy.

[ArenMook]

Right off the bat, Awake is the wrong place for this. Awake should only set properties of the script you're executing it from. It should never be used to alter values of other scripts. Use Start for that.

[helmesjo]

Right off the bat, Awake is the wrong place for this. Awake should only set properties of the script you're executing it from. It should never be used to alter values of other scripts. Use Start for that.

Hehe, kinda embarrassing I said it since I'm kinda hitler around here about just that... But just double-checked and it was actually Start()!

[ArenMook]

No difference trying your hierarchy.

1. using UnityEngine;
2.  
3. public class Test : MonoBehaviour
4. {
5.         void Start ()
6.         {
7.                 GetComponent<UIWidget>().alpha = 0f;
8.                 GetComponent<UIWidget>().alpha = 1f;
9.         }
10. }

[helmesjo]

No difference trying your hierarchy.

1. using UnityEngine;
2.  
3. public class Test : MonoBehaviour
4. {
5.         void Start ()
6.         {
7.                 GetComponent<UIWidget>().alpha = 0f;
8.                 GetComponent<UIWidget>().alpha = 1f;
9.         }
10. }

Well you should set it back to 1 "later on". That's maybe a little vague, but what I have is basically a set of screens, which set the Widget.alpha =0f; in start (this is in a custom component but on the actual "screen"-object) if they are not the "initial screen". Then, "later on" when I want to navigate to one of the other screens, I set the toScreen.alpha = 1f; and tween it in (and set fromScreen.alpha = 0f; when it's not visible anymore). In the example above, the hierarchy was for "toScreen". Makes sense?

[ArenMook]

Unfortunately I can't reproduce this on my end from your descriptions, so I will need a repro case to have a look at.

[helmesjo]

Unfortunately I can't reproduce this on my end from your descriptions, so I will need a repro case to have a look at.

Alright, I'll try to put up a repro as soon as I've got the time!