The Render Region Border gizmo only appears if a camera is selected or if there is no active object #81543

Open
opened 2020-10-08 15:46:47 +02:00 by Dinar Kurmakov · 7 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-10-07 21:43, hash: d8fcd8a316

Short description of error
The UI control elements of the 'Render Region' only appear if the camera is selected or if there is no camera or active object in the scene (by deleting an object, for example).

Exact steps for others to reproduce the error

  1. Create new file and delete all objects in scene.
  2. Draw Render Region border (View --> View Regions --> Render Region or press CTRL+B).
  3. By dragging UI controls adjust Render Region border size.
  4. Add couple of objects to scene and draw Render Region border - UI controls aren't active now.
  5. Delete one of the objects and adjust Render Region border size.
**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-10-07 21:43, hash: `d8fcd8a316` **Short description of error** The UI control elements of the 'Render Region' only appear if the camera is selected or if there is no camera or active object in the scene (by deleting an object, for example). <video src="https://archive.blender.org/developer/F8967912/DGSu5HJRQg.mp4" constrols></video> **Exact steps for others to reproduce the error** 1. Create new file and delete all objects in scene. 2. Draw Render Region border (View --> View Regions --> Render Region or press CTRL+B). 3. By dragging UI controls adjust Render Region border size. 4. Add couple of objects to scene and draw Render Region border - UI controls aren't active now. 5. Delete one of the objects and adjust Render Region border size.
Author

Added subscriber: @d1nar

Added subscriber: @d1nar
Member
Added subscribers: @HooglyBoogly, @WilliamReynish, @JulianEisel, @ideasman42, @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Well, in order to see the controls, you need to select the Camera (same as the the scene Camera).
[check in code is a bit weak, so if there is no camera as well as no active object, both are the some (NULL) and you will also see the controls]

This was a conscious choice, see 3311505fd0. So this is not a bug.
Tbh, I dont think this is the best choice though either.

  • it is not very obvious having to select the camera [in Camera view this might be easier to grasp, but in free perspective view this is less obvious]
  • OTOH, it might still be useful to "not have the border always in the way, stealing mouse clicks from regular usage"

Will also think about a better way to do this [not sure how to solve this best, maybe @WilliamReynish, @HooglyBoogly or @JulianEisel have an idea here?]
(could just add a button in the corner to enable/disable controls, but this is also not very elegant)
If we dont find a better solution, I would even think that showing it always is better than only showing it when the camera is selected.

CC @ideasman42

Well, in order to see the controls, you need to select the Camera (same as the the scene Camera). [check in code is a bit weak, so if there is no camera as well as no active object, both are the some (NULL) and you will also see the controls] This was a conscious choice, see 3311505fd0. So this is not a bug. Tbh, I dont think this is the best choice though either. - it is not very obvious having to select the camera [in Camera view this might be easier to grasp, but in free perspective view this is less obvious] - OTOH, it might still be useful to "not have the border always in the way, stealing mouse clicks from regular usage" Will also think about a better way to do this [not sure how to solve this best, maybe @WilliamReynish, @HooglyBoogly or @JulianEisel have an idea here?] (could just add a button in the corner to enable/disable controls, but this is also not very elegant) If we dont find a better solution, I would even think that showing it always is better than only showing it when the camera is selected. CC @ideasman42
Philipp Oeser changed title from Render Region UI elements bug to Improve Render Region Border UI (show/hide the control gizmo) 2020-10-08 18:42:34 +02:00
Member

I agree it's quite weird to tie the visibility to the camera selection, since the border works in the viewport you might not even care about the camera at that point.

I agree that it's not so bad to always leave the gizmos on. You can always clear the border if they get annoying.

We could put a setting here if people really want a way to turn them off:
F8968884

I agree it's quite weird to tie the visibility to the camera selection, since the border works in the viewport you might not even care about the camera at that point. I agree that it's not so bad to always leave the gizmos on. You can always clear the border if they get annoying. We could put a setting here if people really want a way to turn them off: ![F8968884](https://archive.blender.org/developer/F8968884/image.png)
Brecht Van Lommel added this to the Render & Cycles project 2023-02-07 19:08:06 +01:00
Germano Cavalcante changed title from Improve Render Region Border UI (show/hide the control gizmo) to The Render Region Border gizmo only appears if a camera is selected or if there is no active object 2024-02-14 19:47:05 +01:00

I also notice before but didn't think about reporting it. Yet I bumped into it again and didn't remember I had to have a camera active. This makes no sense, since the region render of the 3dview is not connected to any camera.

I would opt of either a gizmo setting or a setting below the "render region" checkbox. Something like "show manipulator" "show handles".

A new user will never know this behavior or workflow.

I also notice before but didn't think about reporting it. Yet I bumped into it again and didn't remember I had to have a camera active. This makes no sense, since the region render of the 3dview is not connected to any camera. I would opt of either a gizmo setting or a setting below the "render region" checkbox. Something like "show manipulator" "show handles". A new user will never know this behavior or workflow.

Why not add it to the Gizmo menu, here it already shows other gizmos.

Currently the region render also shows weird behavior if we compared 3dv region vs camera region. Notice how different they behave when toggle overlays ON?OFF

Why not add it to the Gizmo menu, here it already shows other gizmos. Currently the region render also shows weird behavior if we compared 3dv region vs camera region. Notice how different they behave when toggle overlays ON?OFF
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 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#81543
No description provided.