Live unwrap interaction changes unwrapping and ignores pinned vertices #75007

Open
opened 3 years ago by heijulien · 13 comments

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

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)
Poster

Added subscriber: @heijulien

Added subscriber: @heijulien
ankitm commented 3 years ago
Collaborator

Added subscriber: @ankitm

Added subscriber: @ankitm
ankitm commented 3 years ago
Collaborator

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

Changed status from 'Needs Triage' to: 'Needs User Info'
ankitm commented 3 years ago
Collaborator

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

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

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
ankitm commented 3 years ago
Collaborator

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

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

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

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

Added subscriber: @Chris_Blackbourn

Added subscriber: @Chris_Blackbourn

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.

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

This is the original UV layout:
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

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

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

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
Owner

Added subscriber: @ideasman42

Added subscriber: @ideasman42
Owner

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.

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 8 months ago
lichtwerk removed the
legacy module/Modeling
label 1 day ago
lichtwerk removed the
Interest/Modeling
label 1 day ago
Sign in to join this conversation.
No Label
Interest/Alembic
Interest/Animation & Rigging
Interest/Asset Browser
Interest/Asset Browser Project Overview
Interest/Audio
Interest/Automated Testing
Interest/Blender Asset Bundle
Interest/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
Interest/Eevee & Viewport
Interest/Freestyle
Interest/Geometry Nodes
Interest/Grease Pencil
Interest/ID Management
Interest/Images & Movies
Interest/Import/Export
Interest/Line Art
Interest/Masking
Interest/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
Interest/Python API
Interest/Render & Cycles
Interest/Render Pipeline
Interest/Sculpt, Paint & Texture
Interest/Text Editor
Interest/Translations
Interest/Triaging
Interest/Undo
Interest/USD
Interest/User Interface
Interest/UV Editing
Interest/VFX & Video
Interest/Video Sequencer
Interest/Virtual Reality
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
Module › Animation & Rigging
Module › Core
Module › Development Management
Module › Eevee & Viewport
Module › Grease Pencil
Module › Modeling
Module › Nodes & Physics
Module › Pipeline, Assets & IO
Module › Platforms, Builds, Tests & Devices
Module › Python API
Module › Render & Cycles
Module › Sculpt, Paint & Texture
Module › Triaging
Module › User Interface
Module › VFX & Video
Platform/FreeBSD
Platform/Linux
Platform/macOS
Platform/Windows
Priority › High
Priority › Low
Priority › Normal
Priority › Unbreak Now!
Status › Archived
Status › Confirmed
Status › Duplicate
Status › Needs Information from Developers
Status › Needs Information from User
Status › Needs Triage
Status › Resolved
Type › Bug
Type › Design
Type › Known Issue
Type › Patch
Type › Report
Type › To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#75007
Loading…
There is no content yet.