Linking is Broken when an asset is used in multiple "new" scenes in a blender session #70483

Closed
opened 2019-10-03 17:04:09 +02:00 by rob silvestri · 6 comments

V2.8
2019-09-05
Windows Operating System

Bug:
When working with multiple scenes in the same blender session, If you link the same asset into multiple (New or Full copy)scenes , the geometry does not follow the armature. It matches the position of the original scene it was linked into. Ideally we would like to have multiple scenes with in the same session, in some cases containing the same assets but treating the scenes completely independently of each other.

Link a character asset into a scene. Build a proxy
Create a new scene and link the same character into the scene. Build the proxy.
Move the armature and you will see that the geometry does not follow the proxy in the new scene.

V2.8 2019-09-05 Windows Operating System Bug: When working with multiple scenes in the same blender session, If you link the same asset into multiple (New or Full copy)scenes , the geometry does not follow the armature. It matches the position of the original scene it was linked into. Ideally we would like to have multiple scenes with in the same session, in some cases containing the same assets but treating the scenes completely independently of each other. Link a character asset into a scene. Build a proxy Create a new scene and link the **same** character into the scene. Build the proxy. Move the armature and you will see that the geometry does not follow the proxy in the new scene.
Author

Added subscriber: @Silves

Added subscriber: @Silves

Added subscriber: @Josephbburg

Added subscriber: @Josephbburg

What Blender version are you using? In 2.81, proxies are being improved and phased out by the new override system. Try the same thing using overrides, see if that fixes the problem.

I'm almost certain that what you're describing is a known limitation of proxies- you need to use different actions for the same proxy object/armature if you want to do what you're doing with proxies. I can't find a list of limitations but it's been known for a long time that proxies don't support multiple instances in a .blend file. Overrides solve that and more.

Since the feature's not fully documented yet, maybe open a devtalk thread and ping someone that's worked on the feature. Then come back here and let us know if it's still causing a problem. I can't test it now, but if you mention me over there (@josephbburg is my handle on devtalk) I'll get back to you, since this feature is interesting to me.

What Blender version are you using? In 2.81, proxies are being improved and phased out by the new override system. Try the same thing using overrides, see if that fixes the problem. I'm almost certain that what you're describing is a known limitation of proxies- you need to use different actions for the same proxy object/armature if you want to do what you're doing with proxies. I can't find a list of limitations but it's been known for a long time that proxies don't support multiple instances in a .blend file. Overrides solve that and more. Since the feature's not fully documented yet, maybe open a devtalk thread and ping someone that's worked on the feature. Then come back here and let us know if it's still causing a problem. I can't test it now, but if you mention me over there (@josephbburg is my handle on devtalk) I'll get back to you, since this feature is interesting to me.

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2019-10-03 20:38:45 +02:00

@Josephbburg said it pretty much all.

@Josephbburg said it pretty much all.
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
3 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#70483
No description provided.