Unwanted merges of UV vertices, also makes importing FBX in mudbox fail. #44320

Closed
opened 2015-04-09 11:41:41 +02:00 by Przemyslaw Golab (SirPigeonz) · 25 comments

Blender Version
Broken: blender-2.74-12661de-win64

Short description of error

When moving identical islands that share vertices on the model to the same place on UV space Blender automatically merges those shared vertices.
This generates problems while editing UV (in other software too) and exports UVs like this to FBX, which makes importing to Mudbox fail (doesn't display correctly, and creates some artifacts on mesh).

Exact steps for others to reproduce the error
Open attached example blend: unwanted_uv_vertex_merge_problem.blend
You will see two identical islands, move one of them to exact position of the other (you can use incremental snap on X to do this here)

What happens:
Islands merge into one.

What should happen:
Island should share the same UV space but stay disconnected.

What should happen on FBX export:
They also should be separated just sharing the same UV space.

**Blender Version** Broken: blender-2.74-12661de-win64 **Short description of error** When moving identical islands that share vertices on the model to the same place on UV space Blender automatically merges those shared vertices. This generates problems while editing UV (in other software too) and exports UVs like this to FBX, which makes importing to Mudbox fail (doesn't display correctly, and creates some artifacts on mesh). **Exact steps for others to reproduce the error** Open attached example blend: [unwanted_uv_vertex_merge_problem.blend](https://archive.blender.org/developer/F160101/unwanted_uv_vertex_merge_problem.blend) You will see two identical islands, move one of them to exact position of the other (you can use incremental snap on X to do this here) What happens: Islands merge into one. What should happen: Island should share the same UV space but stay disconnected. What should happen on FBX export: They also should be separated just sharing the same UV space.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @SirPigeonz

Added subscriber: @SirPigeonz

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Antonis Ryakiotakis self-assigned this 2015-04-09 12:29:34 +02:00

This is currently not possible in blender. There is no notion of "UV islands", rather each face has its own uvs that are handled as shared if they are close together in UV space.

Closing as this is working as intended.

This is currently not possible in blender. There is no notion of "UV islands", rather each face has its own uvs that are handled as shared if they are close together in UV space. Closing as this is working as intended.

Sorry but intended doesn't mean correct. It makes a lot of troubles, especially when working with FBX that has no notion of UV Seams and rest of the team doesn't use Blender.

Maybe at least some work around so it will export to FBX properly?

Sorry but intended doesn't mean correct. It makes a lot of troubles, especially when working with FBX that has no notion of UV Seams and rest of the team doesn't use Blender. Maybe at least some work around so it will export to FBX properly?

Added subscriber: @mont29

Added subscriber: @mont29

Blender itself can't figure out what the UV islands would be in that case, but I'll just add @mont29 here in case he can figure out something. What could work in the whole island detection algorithm is to see if two faces have the same winding in UV space before attaching a face to an island.

Blender itself can't figure out what the UV islands would be in that case, but I'll just add @mont29 here in case he can figure out something. What could work in the whole island detection algorithm is to see if two faces have the same winding in UV space before attaching a face to an island.

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

Reopening, I think we could even support this kind of island detection in blender too.

Reopening, I think we could even support this kind of island detection in blender too.

Huge thanks. I'm really grateful for any even attempt of fixing this. :)

Huge thanks. I'm really grateful for any even attempt of fixing this. :)
Antonis Ryakiotakis removed their assignment 2015-04-09 16:15:50 +02:00
Bastien Montagne was assigned by Antonis Ryakiotakis 2015-04-09 16:15:50 +02:00

Added subscriber: @Psy-Fi

Added subscriber: @Psy-Fi

Made changes in master that allow selection of those islands inside blender. Leaving the exporter part to Bastien, though from brief look it seems as if this might not be possible and may need to be handled from importer side.

Made changes in master that allow selection of those islands inside blender. Leaving the exporter part to Bastien, though from brief look it seems as if this might not be possible and may need to be handled from importer side.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Alright, from what I can see FBX is just dump of per-face UV layer. This means that the issue is in the importer, not the exporter.

We had some small discussion with Bastien, looking if we can at least support custom seams, but looks like this is not possible either. I'm sorry but looks like you'll have to poke the teams of other software for proper support of such a feature.

If it's possible to export the same UV setup from another application and have Mudbox identify it as separate islands, then maybe we could mimic what the other software does, but from my understanding this is not possible.

Closing again.

Alright, from what I can see FBX is just dump of per-face UV layer. This means that the issue is in the importer, not the exporter. We had some small discussion with Bastien, looking if we can at least support custom seams, but looks like this is not possible either. I'm sorry but looks like you'll have to poke the teams of other software for proper support of such a feature. If it's possible to export the same UV setup from another application and have Mudbox identify it as separate islands, then maybe we could mimic what the other software does, but from my understanding this is not possible. Closing again.

Added subscribers: @ideasman42, @MarcClintDion

Added subscribers: @ideasman42, @MarcClintDion

This comment was removed by @MarcClintDion

*This comment was removed by @MarcClintDion*

It's just the behavior of the UV Image Editor selection tool that makes it seem as if the islands are attached.

By using face selection mode in the 3D Viewport and by pressing the 'l' key, you can select the individual islands and move them independently in the UV Image Editor.

It does feel like a flaw in the tool's behavior since it does seem as if some auto-merge function was being applied to the edges of the islands. It seems inconsistent that the interior faces are not moved simultaneously since that would make the grab tool useful for editing multiple islands at the same time, however, that's an implementation limit and not a bug.

The exact value for moving the right island over to the left Island is -160 pixels. Maybe the artifacts you are seeing are caused by your use of snapping tool instead of the precise value.
If you are off by even a pixel or two, it may be difficult to notice in the UV Image Editor but it would almost certainly cause artifacts along the seams when the model is textured and lit using normal maps.

I tested UE4 and the model looks fine. I also transferred the model and textures over to a stand-alone GLSL program and it look fine as well. merge.png

You are welcome to post problems that you have on Blender StackExchange, usually you don't have to wait long before receiving and answer and it's good to have feedback from more experienced artists when you run into problems like this.

If you do post a question on Blender-SE which turns out to be a bug, the people there will close the question and refer you here so you can file a report. Otherwise the bug-tracker can become overwhelmed with red-herrings. :)

http://blender.stackexchange.com/questions/

It's just the behavior of the UV Image Editor selection tool that makes it seem as if the islands are attached. By using face selection mode in the 3D Viewport and by pressing the 'l' key, you can select the individual islands and move them independently in the UV Image Editor. It does feel like a flaw in the tool's behavior since it does seem as if some auto-merge function was being applied to the edges of the islands. It seems inconsistent that the interior faces are not moved simultaneously since that would make the grab tool useful for editing multiple islands at the same time, however, that's an implementation limit and not a bug. The exact value for moving the right island over to the left Island is -160 pixels. Maybe the artifacts you are seeing are caused by your use of snapping tool instead of the precise value. If you are off by even a pixel or two, it may be difficult to notice in the UV Image Editor but it would almost certainly cause artifacts along the seams when the model is textured and lit using normal maps. I tested UE4 and the model looks fine. I also transferred the model and textures over to a stand-alone GLSL program and it look fine as well. ![merge.png](https://archive.blender.org/developer/F160321/merge.png) You are welcome to post problems that you have on Blender StackExchange, usually you don't have to wait long before receiving and answer and it's good to have feedback from more experienced artists when you run into problems like this. If you do post a question on Blender-SE which turns out to be a bug, the people there will close the question and refer you here so you can file a report. Otherwise the bug-tracker can become overwhelmed with red-herrings. :) http://blender.stackexchange.com/questions/

I don't see why the extra comments, the selection bug has been fixed in master.

Also, just a note selecting UV islands will not always work in 3D view - seams are not always present on the model, or seams may be different than what user has made on 3D view. In any case it works now.

Also, this is not strictly about unreal - user mentions marmoset and it may well be cooperation between other -editing- software that lose the island information. Final display will of course always be the same.

I don't see why the extra comments, the selection bug has been fixed in master. Also, just a note selecting UV islands will not always work in 3D view - seams are not always present on the model, or seams may be different than what user has made on 3D view. In any case it works now. Also, this is not strictly about unreal - user mentions marmoset and it may well be cooperation between other -editing- software that lose the island information. Final display will of course always be the same.

Added subscriber: @MauroPfister

Added subscriber: @MauroPfister

Sorry to bug you again about this, but I still experience a strange behavior of blender. If I snap a vertex of one island to the corresponding vertex on an other island (in 3D space, they belong to the same vertex), Blender welds them together. In that case it's not possible to select the islands separately using ctrl+L or island selection, no matter which sticky selection mode is used.
Is this a feature and if so, could it be turned off? If I deliberately wanted to merge two UV-islands I would use the weld tool.

To clarify my point, I attached a small example file:
unwanted_merge.blend

Blender Version: 8be4d76

Sorry to bug you again about this, but I still experience a strange behavior of blender. If I snap a vertex of one island to the corresponding vertex on an other island (in 3D space, they belong to the same vertex), Blender welds them together. In that case it's not possible to select the islands separately using ctrl+L or island selection, no matter which sticky selection mode is used. Is this a feature and if so, could it be turned off? If I deliberately wanted to merge two UV-islands I would use the weld tool. To clarify my point, I attached a small example file: [unwanted_merge.blend](https://archive.blender.org/developer/F196100/unwanted_merge.blend) Blender Version: 8be4d76

@ideasman42, this is the bug I was mentioning on that comment.

@ideasman42, this is the bug I was mentioning on that comment.

This issue was referenced by e2fa6663d3

This issue was referenced by e2fa6663d34b2e200c2a951a74050899c84ec2cf

This issue was referenced by bca4e9c81d

This issue was referenced by bca4e9c81d863ab5a5cbeaceeef9b0606d4f2fdb

Changed status from 'Resolved' to: 'Archived'

Changed status from 'Resolved' to: 'Archived'

Reverted this change since it causes #50970

Checking the report again and in overlapping the islands and you're in fact making 2x islands into one.
Since the UV's and vertices are connected.

Select linked operator can be made more advanced to handle cases like this. See: D2567

Reverted this change since it causes #50970 Checking the report again and in overlapping the islands and you're in fact making 2x islands into one. Since the UV's and vertices are connected. Select linked operator can be made more advanced to handle cases like this. See: [D2567](https://archive.blender.org/developer/D2567)
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
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
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
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
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
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 Info 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
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#44320
No description provided.