Copy Pasting does not respect layers. #48057

Closed
opened 7 years ago by candreacchio · 17 comments

System Information
Windows 7 x64 gtx 580

Blender Version
Broken: b0a7e77
Worked: ad6b7c0

Short description of error
Copy pasting no longer honors the layer it was on for all objects. This is not too much of a problem as we will need to copy and paste with greater care to make sure objects are staying on the same layers... however, it is a significant problem when dealing with dupligroups. the original object also ends up on the layer visible. This should not be the case, as we have a layer dedicated to these objects which shouldnt be rendered but are referenced at rendertime.

Exact steps for others to reproduce the error

  1. open attached blend file
  2. copy the object on layer two (empty with dupligroup)
  3. open new blend file and delete everything
  4. make sure only layer 1 is active
  5. paste
  6. notice how layer one now contains the empty as well as the dupligroup

What is expected (ideally)
layer one would not contain any objects, layer 2 would have the empty and layer 10 would have the mesh

What would also be fine
layer one would contain the empty and layer 10 would have the mesh

copypaste.blend

**System Information** Windows 7 x64 gtx 580 **Blender Version** Broken: b0a7e77 Worked: ad6b7c0 **Short description of error** Copy pasting no longer honors the layer it was on for all objects. This is not too much of a problem as we will need to copy and paste with greater care to make sure objects are staying on the same layers... however, it is a significant problem when dealing with dupligroups. the original object also ends up on the layer visible. This should not be the case, as we have a layer dedicated to these objects which shouldnt be rendered but are referenced at rendertime. **Exact steps for others to reproduce the error** 1. open attached blend file 2. copy the object on layer two (empty with dupligroup) 3. open new blend file and delete everything 4. make sure only layer 1 is active 5. paste 6. notice how layer one now contains the empty as well as the dupligroup What is expected (ideally) layer one would not contain any objects, layer 2 would have the empty and layer 10 would have the mesh What would also be fine layer one would contain the empty and layer 10 would have the mesh [copypaste.blend](https://archive.blender.org/developer/F300822/copypaste.blend)
Poster

Changed status to: 'Open'

Changed status to: 'Open'
Poster

Added subscriber: @candreacchio

Added subscriber: @candreacchio

Added subscriber: @sindra1961

Added subscriber: @sindra1961

I can not reproduce this here.
Windows 10 Pro 64bits
Blender 2.77 (sub 0), commit date: 2016-04-04 23:20, hash: 9c952bb

I suggest that you try the latest buildbot version.

I can not reproduce this here. Windows 10 Pro 64bits Blender 2.77 (sub 0), commit date: 2016-04-04 23:20, hash: 9c952bb I suggest that you try the latest buildbot version.
Poster

I have just tried with 9c952bb and have found that it still has the problem

What layers is the empty ending up on and what layer is the mesh ending up on?

I have just tried with 9c952bb and have found that it still has the problem What layers is the empty ending up on and what layer is the mesh ending up on?
Poster

I have also reset my user prefs to see if there was a conflict with a plugin, still an issue

I have also reset my user prefs to see if there was a conflict with a plugin, still an issue

1.open attached file. and copy object.
copypaste.png
2.restart blender
copypaste2.png
3.delete all objects
copypaste3.png
4.paste
copypaste4.png

1.open attached file. and copy object. ![copypaste.png](https://archive.blender.org/developer/F300825/copypaste.png) 2.restart blender ![copypaste2.png](https://archive.blender.org/developer/F300827/copypaste2.png) 3.delete all objects ![copypaste3.png](https://archive.blender.org/developer/F300829/copypaste3.png) 4.paste ![copypaste4.png](https://archive.blender.org/developer/F300831/copypaste4.png)
Poster

Correct, you also are experiencing the issue.

The dupligroup mesh should NOT be on layer 1. it should be on layer 10.

Ideally the empty should also not be on layer 1, it should be on layer 2... but i can see the argument for making it on layer one.

The dupligroup mesh should NOT be moved between layers, this will result in the dupligroup mesh being on the wrong layer and be visible in renders when it should not be.

Correct, you also are experiencing the issue. The dupligroup mesh should NOT be on layer 1. it should be on layer 10. Ideally the empty should also not be on layer 1, it should be on layer 2... but i can see the argument for making it on layer one. The dupligroup mesh should NOT be moved between layers, this will result in the dupligroup mesh being on the wrong layer and be visible in renders when it should not be.

Because it is pasted on chosen layer, I think that this is right.

Because it is pasted on chosen layer, I think that this is right.
Poster

But thats the thing... the dupligroup actual objects (not empties referencing the dupligroup) should not be rendered, so moving them onto a layer which is renderable is is unintuitive.

But thats the thing... the dupligroup actual objects (not empties referencing the dupligroup) should not be rendered, so moving them onto a layer which is renderable is is unintuitive.

I do not know whether there is a document about copy&paste.
It will be recognized whether this is a bug if there is it.

I do not know whether there is a document about copy&paste. It will be recognized whether this is a bug if there is it.
Sergey commented 7 years ago
Owner

Added subscriber: @Sergey

Added subscriber: @Sergey
Sergey commented 7 years ago
Owner

There's an option called "Active Layer" which was added in 4ef918d which was added on artists requests. f you disable that option then you'll have old behavior.

There's an option called "Active Layer" which was added in 4ef918d which was added on artists requests. f you disable that option then you'll have old behavior.
mont29 commented 7 years ago
Owner

Added subscriber: @mont29

Added subscriber: @mont29
mont29 commented 7 years ago
Owner

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
mont29 closed this issue 7 years ago
mont29 self-assigned this 7 years ago
mont29 commented 7 years ago
Owner

We could switch those new options to OFF by default, but then we’d have different defaults for copy/paste and append/link, which would be bad too… Also, those settings should be 'remembered' after being set the first time, so think we can keep things as they are. Not a bug in any case.

We could switch those new options to OFF by default, but then we’d have different defaults for copy/paste and append/link, which would be bad too… Also, those settings should be 'remembered' after being set the first time, so think we can keep things as they are. Not a bug in any case.
Poster

Thanks, I did not know about that option.

Would it be possible to control the default value via the user prefs (or via python?)

EDIT: you can change the hotkeys default setting in the user prefs... go into input, search for paste selection, expand options, disable active layer

Thanks, I did not know about that option. Would it be possible to control the default value via the user prefs (or via python?) EDIT: you can change the hotkeys default setting in the user prefs... go into input, search for paste selection, expand options, disable active layer
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
4 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

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