Live unwrap interaction changes unwrapping and ignores pinned vertices #75007

New Issue

Julien Heimann · 2020-03-22T07:54:23+01:00

Julien Heimann commented

2020-03-22 07:54:23 +01:00

Blender Version
Broken: 2.79 - 2.83 (sub 10), commit date: 2020-03-19 13:43, hash: 42012493a8
Worked: Never

Short description of error
Grabbing and moving one of the pinned vertices seems to kind of reset the unwrap, even ignoring the pinned vertices.
Short video demonstration:
https://streamable.com/eesv3

Exact steps for others to reproduce the error

Unwrapped parts of an object.
Pinned some vertices in UV editor
enabled live unwrapping.

or

Open this file: LiveUnwrapPinFail.blend
Go to edit mode
Move pinned vertices.

In some cases it also just doesn't do anything at all:
https://streamable.com/ignig
Here is a file showing this other problem:
LiveUnwrapCube.blend

**Blender Version** Broken: 2.79 - 2.83 (sub 10), commit date: 2020-03-19 13:43, hash: `42012493a8` Worked: Never **Short description of error** Grabbing and moving one of the pinned vertices seems to kind of reset the unwrap, even ignoring the pinned vertices. Short video demonstration: https://streamable.com/eesv3 **Exact steps for others to reproduce the error** - Unwrapped parts of an object. - Pinned some vertices in UV editor - enabled live unwrapping. or - Open this file: [LiveUnwrapPinFail.blend](https://archive.blender.org/developer/F8426601/LiveUnwrapPinFail.blend) - Go to edit mode - Move pinned vertices. In some cases it also just doesn't do anything at all: https://streamable.com/ignig Here is a file showing this other problem: [LiveUnwrapCube.blend](https://archive.blender.org/developer/F8426597/LiveUnwrapCube.blend)

Julien Heimann commented

2020-03-22 07:54:23 +01:00

Added subscriber: @heijulien

Ankit Meel commented

2020-03-23 14:09:30 +01:00

Added subscriber: @ankitm

Ankit Meel commented

2020-03-23 14:09:30 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Ankit Meel commented

2020-03-23 14:09:30 +01:00

Please add a simple blend file to help redo the bug with steps to redo.

Julien Heimann commented

2020-03-24 07:36:07 +01:00

LiveUnwrapCube.blend
LiveUnwrapPinFail.blend
In both files just grab a pinned vertex in the UV editor and move it around, you should notice the same effect as in the videos and described above

[LiveUnwrapCube.blend](https://archive.blender.org/developer/F8426597/LiveUnwrapCube.blend) [LiveUnwrapPinFail.blend](https://archive.blender.org/developer/F8426601/LiveUnwrapPinFail.blend) In both files just grab a pinned vertex in the UV editor and move it around, you should notice the same effect as in the videos and described above

Ankit Meel commented

2020-03-24 07:43:39 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Germano Cavalcante commented

2020-03-24 14:58:18 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Chris Blackbourn commented

2022-05-04 08:30:56 +02:00

Added subscriber: @Chris_Blackbourn

Chris Blackbourn commented

2022-05-04 08:30:56 +02:00

Repro in debugger.

This appears to be two seperate issues.

LiveUnwrapPinFail.blend has three islands and only one seam. When Live Unwrap is enabled, all three islands are merged into one island. During the merge, some of the pinned UVs are forced to be identical, and the number of pinned verts drops from 6 down to 4. After this merge occurs, the feature seems to be working as designed, even though it is unlikely what the user originally intended.
As a work around, the user can select "Seams From Islands" before activating Live Unwrap.
More discussion is required for a correct fix in this situation.

For the second unrelated issue, LiveUnwrapCube.blend, the cube has two pinned vertices and no boundaries or seams. The current unwrap solver cannot unwrap a mesh like this because the problem is "underconstrained", so instead it ignores the mesh completely.
In this circumstance, it might be possible to add additional constraints to the solver to get a solve. I will investigate this solution to see if it is possible.
In the mean time, the user can add or remove a pin, or, (by co-incidence) adding a seam or boundary by using "Seams From Islands" will also avoid this issue.

Repro in debugger. This appears to be two seperate issues. LiveUnwrapPinFail.blend has three islands and only one seam. When Live Unwrap is enabled, all three islands are merged into one island. During the merge, some of the pinned UVs are forced to be identical, and the number of pinned verts drops from 6 down to 4. After this merge occurs, the feature seems to be working as designed, even though it is unlikely what the user originally intended. As a work around, the user can select "Seams From Islands" before activating Live Unwrap. More discussion is required for a correct fix in this situation. For the second unrelated issue, LiveUnwrapCube.blend, the cube has two pinned vertices and no boundaries or seams. The current unwrap solver cannot unwrap a mesh like this because the problem is "underconstrained", so instead it ignores the mesh completely. In this circumstance, it might be possible to add additional constraints to the solver to get a solve. I will investigate this solution to see if it is possible. In the mean time, the user can add or remove a pin, or, (by co-incidence) adding a seam or boundary by using "Seams From Islands" will also avoid this issue.

Chris Blackbourn commented

2022-05-06 01:37:56 +02:00

Update on the second issue, LiveUnwrapCube.blend, with two pinned vertices and no boundaries or seams.

This is the original UV layout:

Live unwrap currently excludes these charts (i.e. UV-Islands) as they have no boundary. This is the current behavior, from a UI perspective, it appears to the user like the "Live-Unwrap" is not changing the interaction.

If we remove this limitation, we obtain the following degenerate result:

This next proof of concept code change shows it is possible to get a non-degenerate result by adding additional constrains to the LSCM solver:

Note that this is not a "good" unwrapping, it's simply an existence proof to show that the LSCM solver can still produce an output given this set of inputs by adding additional constraints to push against.

One option would be to find additional constraints which produce an unwrapping which is "useful", even if the mapping itself is not "good".

Another option might be to special case the "2 - pin" case in the same we special case the single-pin case. For example, we could generalise the single-pin case to perform a rotation like so:

A third option might be to attempt to temporarily add additional (boundary) constraints, but this might not work for all inputs.

There might be more options for a fix too..

Are there any technical artists want to chip in with their preferred interaction here?

*Edit: Grammar

Update on the second issue, LiveUnwrapCube.blend, with two pinned vertices and no boundaries or seams. This is the original UV layout: ![image.png](https://archive.blender.org/developer/F13053921/image.png) Live unwrap currently excludes these charts (i.e. UV-Islands) as they have no boundary. This is the current behavior, from a UI perspective, it appears to the user like the "Live-Unwrap" is not changing the interaction. If we remove this limitation, we obtain the following degenerate result: ![image.png](https://archive.blender.org/developer/F13053923/image.png) This next proof of concept code change shows it is possible to get a non-degenerate result by adding additional constrains to the LSCM solver: ![image.png](https://archive.blender.org/developer/F13053925/image.png) Note that this is not a "good" unwrapping, it's simply an existence proof to show that the LSCM solver can still produce an output given this set of inputs by adding additional constraints to push against. One option would be to find additional constraints which produce an unwrapping which is "useful", even if the mapping itself is not "good". Another option might be to special case the "2 - pin" case in the same we special case the single-pin case. For example, we could generalise the single-pin case to perform a rotation like so: ![image.png](https://archive.blender.org/developer/F13053930/image.png) A third option might be to attempt to temporarily add additional (boundary) constraints, but this might not work for all inputs. There might be more options for a fix too.. Are there any technical artists want to chip in with their preferred interaction here? *Edit: Grammar

Campbell Barton commented

2022-05-13 03:09:56 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2022-05-13 03:09:56 +02:00

Checking: LiveUnwrapPinFail.blend as far as I can see, unwrapping in the UV editor should calculate seams based on existing islands, running "seams from islands" then unwrapping works as expected here.

Checking: `LiveUnwrapPinFail.blend` as far as I can see, unwrapping in the UV editor should calculate seams based on existing islands, running "seams from islands" then unwrapping works as expected here.

Chris Blackbourn commented

2022-06-16 00:04:20 +02:00

LiveUnwrapPinFail.blend is fixed by e6e9f1ac5a

LiveUnwrapCube.blend is now #98240

`LiveUnwrapPinFail.blend` is fixed by e6e9f1ac5a2dae42dc523 `LiveUnwrapCube.blend` is now #98240

Chris Blackbourn self-assigned this 2022-06-18 02:05:42 +02:00

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Live unwrap interaction changes unwrapping and ignores pinned vertices #75007