One UV map destroyed when two objects joined #37182

Closed
opened 9 years ago by tea_monster · 12 comments

%%%--- Windows 7 64 ---

- 2.69 RC2 and 3 ---


- When have two objects with separate UV maps. If you Cntrl J to join the objects. one of the objects looses it's UV map and all the uv verts default on top of each other into the lower left hand corner. The original object's UV Map remains intact. Behaviour does not occur in 2.68---


- Open the file, select the head, then select the body and Cntrl J to join them to one object. Go into edit mode and check out the UV map of the body. ---

%%%

%%%--- Windows 7 64 --- - 2.69 RC2 and 3 --- - When have two objects with separate UV maps. If you Cntrl J to join the objects. one of the objects looses it's UV map and all the uv verts default on top of each other into the lower left hand corner. The original object's UV Map remains intact. Behaviour does not occur in 2.68--- - Open the file, select the head, then select the body and Cntrl J to join them to one object. Go into edit mode and check out the UV map of the body. --- %%%
Poster

Changed status to: 'Open'

Changed status to: 'Open'
mont29 commented 9 years ago
Owner

%%%This is a new feature, all CD layers (UVmaps, vertex colors, vertex groups, etc.) are now merged by names. If you do not want that, just rename some of your uvmaps. Not a bug, closing.%%%

%%%This is a new feature, all CD layers (UVmaps, vertex colors, vertex groups, etc.) are now merged by names. If you do not want that, just rename some of your uvmaps. Not a bug, closing.%%%
mont29 commented 9 years ago
Owner

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
mont29 closed this issue 9 years ago
Poster

%%%That is ridiculous. So if I want to join two objects together I've got to hunt through all the properties of the two objects and try and find out if somewhere they have the same names? Even though by default they are bound to unless they have been manually changed?

This will needlessly complicate just about every workflow out there. Supposed I've got a crowd scene with 30 characters in it. Each one will have a default 'uvmap' name. So now, if I want to join these into one object, I now have to go through all of these objects and rename the UV map to something unique? That is insane and seriously breaks workflow from previous versions. %%%

%%%That is ridiculous. So if I want to join two objects together I've got to hunt through all the properties of the two objects and try and find out if somewhere they have the same names? Even though by default they are bound to unless they have been manually changed? This will needlessly complicate just about every workflow out there. Supposed I've got a crowd scene with 30 characters in it. Each one will have a default 'uvmap' name. So now, if I want to join these into one object, I now have to go through all of these objects and rename the UV map to something unique? That is insane and seriously breaks workflow from previous versions. %%%
Owner

%%%@Tea: It's the other way around. If all the objects' uv maps have the same name (which they will unless you manually changed them) they will all be merged smoothly into a single UVMap layer.%%%

%%%@Tea: It's the other way around. If all the objects' uv maps have the same name (which they will unless you manually changed them) they will all be merged smoothly into a single UVMap layer.%%%

Added subscriber: @jonim8or

Added subscriber: @jonim8or

I suggest reopening this bug because I think there's a misunderstanding.
I encountered the bug described in the original post. (and to me the rest of the discussion seems to be missing the point of the original bug)
reproducing the bug is a bit tricky, which is why the attached file from tea_monster might not work.

I consistently get this bug when I do the following steps:
0) open blender in an empty scene

  1. create a cube (or any other mesh primitive)
  2. go to edit mode and unwrap the cube (for this bug the kind of unwrapping does not really matter)
  3. go back to object mode and duplicate the cube (using shift-d)
  4. go to edit mode, and unwrap the second cube in a different way (so it has different uvs)
  5. go back to object mode, Shift-select the first cube, and press Ctrl+J
  6. in edit mode, the uvs of one of the two cubes appear as expected, the uvs of the other have gone to the lower-left corner of the uv layer. There is still only one UV layer, called "UVMap" (as it was in each of the two cubes before joining)

When I ctrl-Z until just before the join, and then join again, it works as expected (both cubes keep their UV layout). So there is something weird and buggy and inconsistent going on.

I suggest reopening this bug because I think there's a misunderstanding. I encountered the bug described in the original post. (and to me the rest of the discussion seems to be missing the point of the original bug) reproducing the bug is a bit tricky, which is why the attached file from tea_monster might not work. I consistently get this bug when I do the following steps: 0) open blender in an empty scene 1) create a cube (or any other mesh primitive) 2) go to edit mode and unwrap the cube (for this bug the kind of unwrapping does not really matter) 3) go back to object mode and duplicate the cube (using shift-d) 4) go to edit mode, and unwrap the second cube in a different way (so it has different uvs) 5) go back to object mode, Shift-select the first cube, and press Ctrl+J 6) in edit mode, the uvs of one of the two cubes appear as expected, the uvs of the other have gone to the lower-left corner of the uv layer. There is still only one UV layer, called "UVMap" (as it was in each of the two cubes before joining) When I ctrl-Z until just before the join, and then join again, it works as expected (both cubes keep their UV layout). So there is something weird and buggy and inconsistent going on.

Added subscriber: @MaleneThyssen

Added subscriber: @MaleneThyssen

Yep i get this one too.

Trying to join two different meshes - but keeping their individual materials and uvmaps - blender joins the meshes on ctrl + j

But one mesh looses its UVmap. It just collapses to a point in the lower left corner.
The material carries over though
I cant get it to work if i try do the ctrl + z trick suggested over here.
All meshes, materials and textures have unique names.
I tried renaming all the uvmaps to unique names too - but with no change in the problem
The objects that shows this behavior has been copied from another mesh now deleted in the scene.

Its a pain in the *** having to unwrap everything again - and making the textures again too just because i want to join meshes. Are you sure this really is intended behavior and not a bug?

Yep i get this one too. Trying to join two different meshes - but keeping their individual materials and uvmaps - blender joins the meshes on ctrl + j But one mesh looses its UVmap. It just collapses to a point in the lower left corner. The material carries over though I cant get it to work if i try do the ctrl + z trick suggested over here. All meshes, materials and textures have unique names. I tried renaming all the uvmaps to unique names too - but with no change in the problem The objects that shows this behavior has been copied from another mesh now deleted in the scene. Its a pain in the *** having to unwrap everything again - and making the textures again too just because i want to join meshes. Are you sure this really is intended behavior and not a bug?
mont29 commented 9 years ago
Owner

@jonim8or You did not revive the right bug… :P

Will merge this one into #37577.

@jonim8or You did not revive the right bug… :P Will merge this one into #37577.
mont29 commented 9 years ago
Owner

Changed status from 'Archived' to: 'Duplicate'

Changed status from 'Archived' to: 'Duplicate'
mont29 commented 9 years ago
Owner

✘ Merged into #37577.

✘ Merged into #37577.
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#37182
Loading…
There is no content yet.