Rotating a UI element

What's the best way to rotate a UI element, namely a sprite?
I've tried adding a simple update rotation script to it, but the sprite stutters and jumps. I wonder if that's from the RectTransform trying to keep the position.

This is only for an updating circular arrow to show that something's busy.

Anyone know of a better way to achieve this?

 

Hi Tim, I'm using a simple

transform.Rotate(Vector3.forward *Time.deltaTime *100);

in an Update(). The problem is a very jerky rotation, with the center stuttering from one pixel to another. It is aligned 0.5, 0.5

 

Interesting, thanks Tim. So I need pixel perfect for the clarity of text and 9 sliced sprites, but not for rotation. Yes, I've tried it and unchecking pixel-perfect works perfectly for rotation.

What's the overhead of having a second Canvas just for the one or two items that need to be rotated, or is there a better method?

 

Nested? Ok, cool thanks Tim XD

Tried a nested canvas, and a couple of things are immediately noticeable. The nested canvas has no options for pixel-perfect, but does not seem to take on the pixel-perfect setting of the parent canvas.
For example, my main canvas is set to pixel-perfect, which causes jerky animation of UI elements; but the nested canvas which has no options for pixel-perfect, gives me smooth animation. Whilst it works for me, is this the intended behaviour for a nested canvas?

 

Um if it inherits then the solution you just suggested i.e. using a nested canvas for the rotation elements will break will it not? I mean the parent would be set to pixel perfect so the child would by default then inherit the pixel perfect setting when in fact you want it not to.
So isn't the only solution to expose the property on the nested canvas?

Ignore me if I'm missing something obvious it's been a long day.

 

bug reported: case 636781

@PeteD - I think they're planning to make the nested canvas inherit by default, and expose the parameter so that we can choose not to inherit (as I want to).

 

Fun with nested canvases begins when you need to process events on them, coz using default raycasting priority, nested canvas graphics always has priority over other children of parent canvas even if children are rendered on top due to transform order.
(all buttons are pressed as expected except of red one where click is intercepted by green button)

But having an ability to control pixel-perfect setting of nested canvas is a must for any layout with big scrolls or some moving parts.

 

Oh, I somehow thought it's a "by-design" behavior. I'll raise a bug soon.

 

@phil-Unity #638223