Page MenuHome

UV Editor Individual Origins not working for Edges, Vertices and Faces
Closed, ResolvedPublicTO DO


System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.41

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: rB26bd5ebd42e3
Worked: (optional)

Short description of error
[Please fill out a short description of the error here]
In the UV Editor the option to transform based on individual origins is not working for Edges, Vertices and Faces of the UV mesh, only for whole Islands.

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]
Add an Object (either something more complicated than a cube or alternatively a subdivided cube.
Select some connected vertices at one part of the UV mesh
Select some connected vertices at another part of the UV mesh which are not connected to the previously selected ones
Set the Pivot to "Individual Origins"
Rotate or scale to see that the rotation or scale uses the median point of the selected vertices rather than the individual origins of each vertex collection.

Event Timeline

Jacques Lucke (JacquesLucke) changed the task status from Needs Triage to Needs Information from User.Sun, Dec 29, 4:24 PM

Are you talking about the difference in behavior between these two examples?

This might be related, but it's not really what I meant.
What I'm talking about is the "transform individual origins" functionality as it works when editing meshes, but to have that same functionality in the UV Editor in a single UV island, for a number of connected vertices.
I hope the following screen capture clarifies it somewhat:
The 3D Viewport works with individual origins as I expect it, but the UV Editor does not.

Jacques Lucke (JacquesLucke) changed the task status from Needs Information from User to Needs Triage.Sun, Dec 29, 4:51 PM

I see, well this is exactly the issue that I meant as well.

I'm not sure if this is a bug or if it is supposed to work like that. Personally, I think the behavior you suggest makes more sense.

Campbell Barton (campbellbarton) changed the subtype of this task from "Report" to "To Do".Tue, Jan 14, 10:29 AM

The suggested behavior would be better, but this is working as intended, marking as TODO.