Several Cameras to different viewports #60756
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#60756
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?
Hello guys! Help me please? In 2.79 I can deactivate this buttons and see from dfferent cameras in viewports. But I can't find this option in 2.8
Added subscriber: @Kovalex
Added subscribers: @WilliamReynish, @lichtwerk
lock_camera_and_layers
is not exposed in the UI atm afaics.There have been some changes in 2.8 regarding layers / renderlayers and groups, see https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Layers
main window
(Window
>New Main Window
) and set the viewlayer there (you can choose in top right of your window)lock_camera_and_layers
is disabled (see issue above, it is not available atm...), checking on this...@WilliamReynish : am I right on this?
afaik this feature is currently missing in 2.8, Would be great to bring back somehow. Now Collection visibility is global for all viewports. We could but a toggle inside in the Viewport Collections popover to set this, so you can view different Collections for each viewport.
Added subscriber: @brecht
@brecht: What are you thinking about the 'unlock viewport' feature? Is this something you consider a priority to bring back for 2.8?
feature is intact (regarding local cameras), see
P897: #60756 snippet
(added to the sidebar
View
panel, you can then select a local camera per view)it should just be checked against the usage of layers and cleaned up (happy to do this if it is agreed to bring this back)
Ah ok. I guess it's more a design question then. Should we bring back support for per-viewport collections, and should they use the same toggle?
In a way per-viewport collections and per-viewport camera are fairly different, so I think it could make sense to just bring back that option as you suggest. We could call It 'Override Viewport Camera" ?
Later on, we could add a separate toggle inside the Collections visibility popover called Override Viewport Visibility.
@brecht? This is mostly a design issue re support for per-viewport collections. You ok with adding this for cameras for now at least?
viewlayer
[not collections] per view (since you set collections up for a viewlayer)?Let's add back this option is for the camera override only and rename it accordingly. Per-view collections visibility is something we can consider separately, it may not come back at all in this form.
Yes, it's normal for other softs that in any viewport you can select any camera by list.
This doesn't even need a "Use scene Camera" property really, we can just use the camera if it is set and remove the property. It would need a bit of versioning code to clear the camera is the option is off.
Ok great, so we add this back and call it Use Scene Camera, which can be disabled, as @lichtwerk suggests.
The per-view collections visibility can then be added as a separate feature later on.
@brecht Good point - that would be even smarter.
Still need to check a bit further, but we only have
v3d->camera
andscene->camera
.Then there is a bunch of code that keeps them in sync (check
v3d->scenelock
)v3d->scenelock
is also set inrna_SpaceView3D_lock_camera_and_layers_set
, so if we dont use this toggle anymore, we'd have to make sure all is still working as expected[check/update/remove all occurances of v3d->scenelock, or set scenelock appropriately somehow? wouldnt be sure when though...]
[also seems to be quite useful to quickly get your view back to the scene state?]
Or would that mean we'd set the
v3d->camera
to thescene->camera
automatically when it is cleared (X
button)?Still needs a bit of thinking... [ at least on my side ;) ]
Seems it is not trivial indeed, you can also just keep the boolean and we can simplify it later.
It would require refactoring the code so
v3d->camera
is not accessed directly throughout the code, but rather through a helper function that returns either the v3d or scene camera.This issue was referenced by
6100dc6a20
Changed status from 'Open' to: 'Resolved'