koobas.hobune.stream
Unity 5.2 Canvas component makes the position not to update
Hi, i just updated to unity 5.2 and i seem to have a problem with moving UI elements with Canvas component on them (for sorting purposes). I have 2 buttons that when starting the scene are bellow the screen and they start moving into the screen to their position using Tween. One of the buttons has a Canvas component on it and it doesn't update its position (graphically).The rect transform of the button is moving but not the graphic itself . The other button works perfectly because it has not canvas on it. (added 1 for testing and behaves just like the first one).
This issue happened just after updating to unity 5.2. Anyone has an answer for this?
Thanks, Andrei F.
I am having the same issue since i updated to Unity 5.2. Strangely, it isn't happening with every canvas in my scene. Happening with 5.2.0f3 & 5.2.1f1.
Note that i'm using padding ( left / right anchor offset values ) to move my canvas.
The canvas I have is added by me for sorting override purposes. Still happening in unity 5.2.1 Still waiting for unity not to mess up everything...
Having the same issue, it's pretty annoying. What I am doing until this issue is fixed is setting the graphic dirty any time the object moves. Not ideal so hopefully its fixed soon.
Settings my canvas to pixel perfect fixed it for me.
Some of my canvas were using pixel perfect while other where inheriting from the top level one. Setting the top level to pixel perfect and inherit on every children fixed my transition issues.
Still is a Unity UI issue imo.
Happened to me too, I realized I had a weird Canvas element (which I hadn't added) inside an element of my Canvas hierarchy.
1- I had a main panel with a Canvas component. 2- A child of it with "another" Canvas component, which I had not added. 3- The rest of my hierarchy.
Also note that the "other" canvas element, was different to the parent one, it had less variables to choose from in it for some reason.
I just removed that intermediate element and kept the rest. Things started to move properly again. Check if you have any weird elements in your hierarchy that you do not remember adding... Still, no clue why Unity 5.2 would have done that.
