Joining with an object scaled to zero on one axis will make geometry disappear #80077

Closed
opened 2020-08-24 13:32:56 +02:00 by Lachlan Audas · 9 comments

System Information
Operating system: platform: Linux, Debian 9 AMD 64
Graphics card: VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 650 Ti] (rev a1)

Blender Version
version: 2.83.5, branch: master, commit date: 2020-08-19 06:07, hash: c2b144df39, type: Release
build date: 2020-08-19, 06:05:02

Short description of error
Join dose not work correctly in some case,

Exact steps for others to reproduce the error
There is a empty "plain box" around the Objects to Join, and shows up the join bug.

( Using shift select ) Select the Cube first then s001-#def-active-grp_curve_.007 and, (in object mode of course) Press Control J, and the Cube Disappears!
Change order of selection and Cube dose not disappear IE:
Select the s001-#def-active-grp_curve_.007 then the Cube and, (in object mode of course) Press Control J, and it works!

Attach files, and system info file from blender

Lachlan

case_join2v6_fence.blend

system-info.txt

**System Information** Operating system: platform: Linux, Debian 9 AMD 64 Graphics card: VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 650 Ti] (rev a1) **Blender Version** version: 2.83.5, branch: master, commit date: 2020-08-19 06:07, hash: c2b144df395f, type: Release build date: 2020-08-19, 06:05:02 **Short description of error** Join dose not work correctly in some case, **Exact steps for others to reproduce the error** There is a empty "plain box" around the Objects to Join, and shows up the join bug. ( Using shift select ) Select the **Cube** first then **s001-#def-active-grp_curve_.007** and, (in object mode of course) Press Control J, and the Cube Disappears! Change order of selection and Cube dose not disappear IE: Select the **s001-#def-active-grp_curve_.007** then the **Cube** and, (in object mode of course) Press Control J, and it works! Attach files, and system info file from blender Lachlan [case_join2v6_fence.blend](https://archive.blender.org/developer/F8808151/case_join2v6_fence.blend) [system-info.txt](https://archive.blender.org/developer/F8808152/system-info.txt)
Author

Added subscriber: @lachlanA

Added subscriber: @lachlanA
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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

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

Can confirm, not sure this is a bug though.

First of all, I think we are talking about objects Cube and s001-#def-active-grp_curve_.007 here? (report was misleading in saying Cube and Vert.001 -- this combination doesnt really have that problem)
The s001-#def-active-grp_curve_.007 object has a Z-scale of zero, which is taken into account after joining for the joined object.
If you select the other way around, the Cube Z-scale of 1 is taken into account after joining for the joined object - and this works well.

So the object doesnt really disappear, it is just not showing with a Z-scale of zero ;) -- I know this sounds weird.
It is not entirely clear to me if this happens in drawing code, but at least 2.79 behaved the same. (so it might as well be in actual modeling code...), it cannot be reproduced with scaling Z to zero after joining.

So as a workaround, just apply scale on s001-#def-active-grp_curve_.007 first, then joining should work no matter in which order selection happened.

Will keep as Known Issue for now.

Can confirm, not sure this is a bug though. First of all, I think we are talking about objects `Cube` and `s001-#def-active-grp_curve_.007` here? (report was misleading in saying `Cube` and `Vert.001` -- this combination doesnt really have that problem) The `s001-#def-active-grp_curve_.007` object has a Z-scale of zero, which is taken into account after joining for the joined object. If you select the other way around, the `Cube` Z-scale of 1 is taken into account after joining for the joined object - and this works well. So the object doesnt really disappear, it is just not showing with a Z-scale of zero ;) -- I know this sounds weird. It is not entirely clear to me if this happens in drawing code, but at least 2.79 behaved the same. (so it might as well be in actual modeling code...), it cannot be reproduced with scaling Z to zero after joining. So as a workaround, just apply scale on `s001-#def-active-grp_curve_.007` first, then joining should work no matter in which order selection happened. Will keep as Known Issue for now.
Philipp Oeser changed title from Join dose not work correctly in some case. to Joining with an object scaled to zero on one axis will make geometry disappear 2020-08-24 14:33:12 +02:00
Author

Thanks Philipp,

I'm no Blender expert, I'm just learning fact. So was very confusing for the old 63 year brain LOL. Thanks for the good work around. And for you quick help!

lachlan

Thanks Philipp, I'm no Blender expert, I'm just learning fact. So was very confusing for the old 63 year brain LOL. Thanks for the good work around. And for you quick help! lachlan

This issue was referenced by dedab68dcc

This issue was referenced by dedab68dcce0f2880f0678e7cfa80e0261b0de72

This issue was referenced by 5eb7aa5ebb

This issue was referenced by 5eb7aa5ebba9cf6a88e0433ac679ad8f810c5c47

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Campbell Barton self-assigned this 2020-08-25 06:42:25 +02:00

@lichtwerk agree this borderline bug/limitation, however I checked on supporting it and found it's possible to prevent the single degenerate axis from interfering with transforming object data on other axes.

@lachlanA be assured these kinds of issues impact users of all ages :) There is now a fix in master that handles the situation more gracefully, although we can't prevent the zero-scale from flattening the objects that are joined, so a warning is shown as well.

@lichtwerk agree this borderline bug/limitation, however I checked on supporting it and found it's possible to prevent the single degenerate axis from interfering with transforming object data on other axes. @lachlanA be assured these kinds of issues impact users of all ages :) There is now a fix in master that handles the situation more gracefully, although we can't prevent the zero-scale from flattening the objects that are joined, so a warning is shown as well.
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
4 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#80077
No description provided.