Parented camera not animated when switching view with markers and collection is disabled #104002
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#104002
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01
Blender Version
Broken: version: 3.5.0 Alpha, branch: master, commit date: 2023-01-19 11:07, hash:
320757bc61
Broken: version: 3.4.1
Broken: version: 2.83.9
Worked: probably never
Short description of error
In a scene with multiple cameras and markers used to switch between them, if the collection containing the cameras is disabled (hidden with the monitor icon) and the cameras have an animated parent, only the camera active at the start of playback will be animated. The animation works fine when the collection is shown.
Exact steps for others to reproduce the error
bug_report_marker_cam_anim.blend
Open the attached blend file
Play the animation
Show the Cams collection and play
When the collection is hidden:
When the collection is shown:
Added subscriber: @pioverfour
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Confirmed'
Similar to #103886 (Local Camera doesn't allow animation of camera from excluded collection)
This bug was fixed some time between 3.6 and 4.0.
Thanks. I'll change the milestone then (need to find if this was actually a fix or improved during refactor)
I bisected to
e623d07362
, so actually a fix.Thanks :D
I'll add this in backporting list.
Pratik Borhade referenced this issue2024-03-11 10:36:54 +01:00
Done.
Actually I’m not sure the backport would work on its own since the commit references !110139, which looks more involved.
I can confirm that the issue is not fixed in 3.6 with only
e623d07362
applied. It is fixed after applyingb248295530
as well.Thanks. I don't think we can backport
b248295530
so I'll just removee623d07362
from the list.Actually,
e623d07362
has been backported already to 3.3 / 3.6@lichtwerk ^
@Sergey : I had
e623d07362
on the backport list (and backport already happened). Does it harm having that in without actually havingb248295530
in as well?You either need both or none of the commits. Having either of them and not the other makes the dependency graph nodes and relations builder asymmetric, likely causing console noise, and potentially even crashes.
So since
b248295530
ontop gave non-trivial conflicts, I also reverted the backport ofe623d07362
in the LTS branch now