2.8 Markers dont switch camera #63703

Closed
opened 2019-04-18 15:52:30 +02:00 by Viktor Johansson · 10 comments

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35

Blender Version
Broken: version: 2.80 (sub 57), branch: blender2.7, commit date: 2019-04-17 19:26, hash: b46245470f

Short description of error
Camera-markers don´t switch camera in some of the blender file´s scenes. Happened randomly when working, had to backtrack 4 files to get a working scene. In 2.79 it should just be to click the "lock cameras and layers" button.

Exact steps for others to reproduce the error
This file has one Scene that´s broken and one where it works.
MarkersDontWork.blend

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35 **Blender Version** Broken: version: 2.80 (sub 57), branch: blender2.7, commit date: 2019-04-17 19:26, hash: `b46245470f` **Short description of error** Camera-markers don´t switch camera in some of the blender file´s scenes. Happened randomly when working, had to backtrack 4 files to get a working scene. In 2.79 it should just be to click the "lock cameras and layers" button. **Exact steps for others to reproduce the error** This file has one Scene that´s broken and one where it works. [MarkersDontWork.blend](https://archive.blender.org/developer/F6957039/MarkersDontWork.blend)

Added subscriber: @Swespy

Added subscriber: @Swespy
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Do you know what caused this bug? Can you reproduce it in a new file?

Do you know what caused this bug? Can you reproduce it in a new file?

It´s not the first time, but all other times I just got back to a previous file and worked from there.
The file is originally created in 2.79 and worked fine for like a week in 2.8, then I think I just changed the compositing node outputs in every scene, then tried to render (Eevee) then I saw that no markers worked at all in the file.

But If I append the scene from an old file, then the markers work, so must be a scene specific thing I guess? Even if I take copy settings from the broken scene, it´s impossible to create new working markers and cameras.

But I don´t want to append in everything or copy paste because in this specific case there are 15 scenes in one blender file and linked data across them all.

How I did the file that I uploaded:
*Took the broken scene, deleted everything but the cameras
*Appended the same scene from a working blend file (still 2.8) and removed everything but the cameras.

Tried to compare the data in the file through the "Data API" tab, but in both scenes, blender knows the markers and camera bindings.

It´s not the first time, but all other times I just got back to a previous file and worked from there. The file is originally created in 2.79 and worked fine for like a week in 2.8, then I think I just changed the compositing node outputs in every scene, then tried to render (Eevee) then I saw that no markers worked at all in the file. But If I append the scene from an old file, then the markers work, so must be a scene specific thing I guess? Even if I take copy settings from the broken scene, it´s impossible to create new working markers and cameras. But I don´t want to append in everything or copy paste because in this specific case there are 15 scenes in one blender file and linked data across them all. How I did the file that I uploaded: *Took the broken scene, deleted everything but the cameras *Appended the same scene from a working blend file (still 2.8) and removed everything but the cameras. Tried to compare the data in the file through the "Data API" tab, but in both scenes, blender knows the markers and camera bindings.

Added subscriber: @hedgehog90-3

Added subscriber: @hedgehog90-3

I think I'm experiencing the same bug: #63697

For me it happened after deleting objects and/or scenes.

I think I'm experiencing the same bug: #63697 For me it happened after deleting objects and/or scenes.

In #63703#662768, @hedgehog90-3 wrote:
I think I'm experiencing the same bug: #63697

For me it happened after deleting objects and/or scenes.

Yeah, maybe I purged the file before saving, but not 100% on that!

But the scene data stills knows the markings and camera bindings in the "Data API" tab

> In #63703#662768, @hedgehog90-3 wrote: > I think I'm experiencing the same bug: #63697 > > For me it happened after deleting objects and/or scenes. Yeah, maybe I purged the file before saving, but not 100% on that! But the scene data stills knows the markings and camera bindings in the "Data API" tab

Added subscriber: @ZedDB

Added subscriber: @ZedDB

I'll go ahead and merge this in as the problem seems to be the same

I'll go ahead and merge this in as the problem seems to be the same

Closed as duplicate of #63697

Closed as duplicate of #63697
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#63703
No description provided.