All armatures reset positions on linked collection when ctrl+z used on anything. Blender 2.80. Problem for production files! #60378

Closed
opened 4 years ago by JonathanMafi · 6 comments

System Information
Operating system: Linux Mint
Graphics card: GTX 780

Blender Version
Broken: 2.80, d59c4c9d61, 2018-12-05 03:23
Worked: 2.79, (somewhat of a comparison considering groups instead of collections....)

Short description of error
When a linked collection containing another linked and posed armature is in a scene and undo(ctrl+z) is used the armature pose resets its position.
The same scenario in Blender 2.79 using groups (instead of collections) does NOT have this behaviour.

NOTE: the reset is only temporary. If you save the file and reopen. the pose has restored its original position.

Exact steps for others to reproduce the error
In order to reproduce this behaviour you need at least TWO files. One to represent an asset and one an environment. A third file is used to link in the collection from the environment file. This reproduces standard production procedures where environments with linked assets would be linked into a shot.

Step 1:
Create a rig asset (one bone armature will do) and put in collection. Save file as asset file.
Step 2:
Create a second file and link in the asset collection. Proxy the asset rig and edit the pose into a new position. Save file.
Step 3:
Link in the environment file into a new file. Do anything else (e.g. create a plane and move it). Hit undo. The asset rig will reset its posed transforms.

asset_28_sample.blend
environment_28_sample.blend
shot_28_sample.blend

**System Information** Operating system: Linux Mint Graphics card: GTX 780 **Blender Version** Broken: 2.80, d59c4c9d61a, 2018-12-05 03:23 Worked: 2.79, (somewhat of a comparison considering groups instead of collections....) **Short description of error** When a linked collection containing another linked and posed armature is in a scene and undo(ctrl+z) is used the armature pose resets its position. The same scenario in Blender 2.79 using groups (instead of collections) does NOT have this behaviour. NOTE: the reset is only temporary. If you save the file and reopen. the pose has restored its original position. **Exact steps for others to reproduce the error** In order to reproduce this behaviour you need at least TWO files. One to represent an asset and one an environment. A third file is used to link in the collection from the environment file. This reproduces standard production procedures where environments with linked assets would be linked into a shot. Step 1: Create a rig asset (one bone armature will do) and put in collection. Save file as asset file. Step 2: Create a second file and link in the asset collection. Proxy the asset rig and edit the pose into a new position. Save file. Step 3: Link in the environment file into a new file. Do anything else (e.g. create a plane and move it). Hit undo. The asset rig will reset its posed transforms. [asset_28_sample.blend](https://archive.blender.org/developer/F6236253/asset_28_sample.blend) [environment_28_sample.blend](https://archive.blender.org/developer/F6236202/environment_28_sample.blend) [shot_28_sample.blend](https://archive.blender.org/developer/F6236201/shot_28_sample.blend)
Poster

Added subscriber: @JonathanMafi

Added subscriber: @JonathanMafi
JonathanMafi changed title from Armature resets position on linked collection when ctrl+z used. Blender 2.80. Problem for production files! to All armatures reset positions on linked collection when ctrl+z used on anything. Blender 2.80. Problem for production files! 4 years ago
Poster

Sorry can i ask why this was removed from project BF Blender: 2.8? Considering this problem only exists in 2.8? Is BF Blender: 2.8 only for crash reports?

Sorry can i ask why this was removed from project BF Blender: 2.8? Considering this problem only exists in 2.8? Is BF Blender: 2.8 only for crash reports?
ZedDB commented 4 years ago
Collaborator

Added subscriber: @ZedDB

Added subscriber: @ZedDB
mont29 was assigned by ZedDB 4 years ago
ZedDB commented 4 years ago
Collaborator

That tag was used when 2.79 was in the master branch. Now 2.8 is in the master branch, so now all 2.8 problems just have the "Blender" tag.

That tag was used when 2.79 was in the master branch. Now 2.8 is in the master branch, so now all 2.8 problems just have the "Blender" tag.
Collaborator

This issue was referenced by b21bd431e3

This issue was referenced by b21bd431e3a50c79d9db549254141fe7ffa311a7
mont29 commented 4 years ago
Owner

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
mont29 closed this issue 4 years 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
4 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

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