Objects have become randomly invisible in certain tabs #82443

Closed
opened 2020-11-05 20:07:38 +01:00 by Sebastien Larocque · 7 comments

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

Blender Version
Broken: version: 2.91.0 Beta, branch: master, commit date: 2020-11-04 19:21, hash: 29780b8101
Worked: Worked in all versions, but the problem seems to have appeared in version 2.9 and is sporadic.

Short description of error
Objects have become randomly invisible in certain tabs.

Exact steps for others to reproduce the error

  • Open the “ObjectVisibilityIssue.blend” file attached here.
  • The problem is present in the “Modeling” view. It is already open in the project file.
  • Normally, you would see the object “Sphere_Visible”, while the two others are hidden, but should be shown. Right there, there is a problem.
  • Select the object “Sphere_Problem1” or “Sphere_Problem2” in the Outliner. Move your mouse cursor over the 3D view and press the dot on the numeric keypad or use the menu View | Frame Selected. Nothing happens. It is as if the objects does not exist in that view.
  • Then select the Layout view (the tab) and you will see all the objects as they should have appeared in the Modeling view.
  • Note that the Default_Camera and Particle_Cube objects have the same problem with the selection.

Other information

I have not been able to reproduce this bug outside of my project. Therefore, I took my project and I stripped all the objects not related to the problem.

During the time that I got the problem, I was mainly working in the Compositing and Shading views and selecting and changing the visibility of the objects in the Outliners. I cannot tell exactly how the problem triggered. During my work, on many occasions, I found out that I could not focus on certain objects anymore (by using the dot on the numeric keypad). This is where I noticed that these problematic objects were not visible anymore in the view that I was working. I bypassed the problem by using another view. In this case, the Layout view was still working while I had problems in the Modeling view. Eventually, I had to reload the blend file without the UI to clear the problem and continue normally.

Loading the blend file and unchecking “Load UI” in the load dialog does a reset in the UI. That clears the problem. It appears to me that the problem is UI related.

I believe the problem has already disappeared once without a reason, but it came back later. I cannot tell why, but all other times when it happens, I needed to reload the file without the UI.

Beyond the fact that the object is not visible in a particular view, the selection functions related to the object are also not functional. For example, doing View | Frame Selected (dot on the numeric keypad) does not adjust the view to the object. Furthermore, the move gizmo widget is not even shown. It is really as if the object did not exist at all a the problematic view. However, in other views, we do not even notice there is a problem because it works correctly.

Although I keep resetting the UI by reloading the blend file and clearing the “Load UI” option, this problem keeps coming back without an apparent reason. You can validate the problem with the project file included, but reproducing the steps that lead to the problem is another story.

ObjectVisibilityIssue.blend

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06 **Blender Version** Broken: version: 2.91.0 Beta, branch: master, commit date: 2020-11-04 19:21, hash: `29780b8101` Worked: Worked in all versions, but the problem seems to have appeared in version 2.9 and is sporadic. **Short description of error** Objects have become randomly invisible in certain tabs. **Exact steps for others to reproduce the error** * Open the “ObjectVisibilityIssue.blend” file attached here. * The problem is present in the “Modeling” view. It is already open in the project file. * Normally, you would see the object “Sphere_Visible”, while the two others are hidden, but should be shown. Right there, there is a problem. * Select the object “Sphere_Problem1” or “Sphere_Problem2” in the Outliner. Move your mouse cursor over the 3D view and press the dot on the numeric keypad or use the menu View | Frame Selected. Nothing happens. It is as if the objects does not exist in that view. * Then select the Layout view (the tab) and you will see all the objects as they should have appeared in the Modeling view. * Note that the Default_Camera and Particle_Cube objects have the same problem with the selection. **Other information** I have not been able to reproduce this bug outside of my project. Therefore, I took my project and I stripped all the objects not related to the problem. During the time that I got the problem, I was mainly working in the Compositing and Shading views and selecting and changing the visibility of the objects in the Outliners. I cannot tell exactly how the problem triggered. During my work, on many occasions, I found out that I could not focus on certain objects anymore (by using the dot on the numeric keypad). This is where I noticed that these problematic objects were not visible anymore in the view that I was working. I bypassed the problem by using another view. In this case, the Layout view was still working while I had problems in the Modeling view. Eventually, I had to reload the blend file without the UI to clear the problem and continue normally. Loading the blend file and unchecking “Load UI” in the load dialog does a reset in the UI. That clears the problem. It appears to me that the problem is UI related. I believe the problem has already disappeared once without a reason, but it came back later. I cannot tell why, but all other times when it happens, I needed to reload the file without the UI. Beyond the fact that the object is not visible in a particular view, the selection functions related to the object are also not functional. For example, doing View | Frame Selected (dot on the numeric keypad) does not adjust the view to the object. Furthermore, the move gizmo widget is not even shown. It is really as if the object did not exist at all a the problematic view. However, in other views, we do not even notice there is a problem because it works correctly. Although I keep resetting the UI by reloading the blend file and clearing the “Load UI” option, this problem keeps coming back without an apparent reason. You can validate the problem with the project file included, but reproducing the steps that lead to the problem is another story. [ObjectVisibilityIssue.blend](https://archive.blender.org/developer/F9211693/ObjectVisibilityIssue.blend)

Added subscriber: @SebBlender

Added subscriber: @SebBlender

Added subscriber: @deadpin

Added subscriber: @deadpin

This is because your "Modeling" tab is set to "local view" link and so is focusing just on Sphere_Visible:
local.png

Hit / to exit local view and then re-center your view to see all the objects.

This is because your "Modeling" tab is set to "local view" [link ](https://docs.blender.org/manual/en/dev/editors/3dview/navigate/local_view.html) and so is focusing just on Sphere_Visible: ![local.png](https://archive.blender.org/developer/F9211929/local.png) Hit `/` to exit local view and then re-center your view to see all the objects.

Thanks, that works! Although I used the / quite often, I never saw this possibility in my project. Therefore, this is not a bug, at least in the code, but in the design, it is another thing.

Following that, I would like to bring a suggestion. Blender is a particular software in terms of UI. Since 2.8, it is more standard and easier to use. Its unique design may confuse people sometimes. I’m probably not alone to have encountered that.

I suggest that you make it clearer when the local view is used. There are two examples that I want to highlight.

  1. In edit mode, it appears obvious because the icon menu at the left changes and some other visual cues as well.

  2. In the Unity game engine, the play mode has confused many developers. They were doing modifications and they lost their modifications once returning to the normal mode. To make things more obvious, Unity has introduced a feature that turned all the interface of the editor to a different color. That way, it was obvious that Unity was in play mode.

Furthermore, I would like to add that I got confused a few times when editing locally in other projects. After a while, I did not remember that I was still in the local view and I was wondering why it did nothing when clicking the other objects in the Outliner. It was not a major problem, but more a glitch in the user experience. Now that I know that, I’m more aware.

To come back to this problem that I reported above, I never suspected this possibility because I never thought that I entered the local view. My reference of entering the local view is sometimes more in my head than what I see on the screen. I must have entered the local view accidentally. The original project had objects of the space with stars and the view looked like the space. The objects were either small or extremely large. I was working mainly in render mode. Nothing so obvious to notice an object being isolated.

Here is some solution to this design issue.

  • It makes no sense to be able to continue to select other objects in the Outliner if I’m in the local view. That allows me to change some properties of these objects in the panels just underneath. This is a mixed design.
  • Even in edit mode, I’m still able to select other objects and it appears to me pretty similar to the local view design in terms of problems.
  • Whether it is the local view or edit mode, it should disable other possibilities not related and that can confuse the user. In many UI from other software, the notion of “grayed out” menu or link is common.

Do you think, you could add that (making the local view and more obvious) as a task to modify the UI?

Thanks, that works! Although I used the / quite often, I never saw this possibility in my project. Therefore, this is not a bug, at least in the code, but in the design, it is another thing. Following that, I would like to bring a suggestion. Blender is a particular software in terms of UI. Since 2.8, it is more standard and easier to use. Its unique design may confuse people sometimes. I’m probably not alone to have encountered that. I suggest that you make it clearer when the local view is used. There are two examples that I want to highlight. 1. In edit mode, it appears obvious because the icon menu at the left changes and some other visual cues as well. 2. In the Unity game engine, the play mode has confused many developers. They were doing modifications and they lost their modifications once returning to the normal mode. To make things more obvious, Unity has introduced a feature that turned all the interface of the editor to a different color. That way, it was obvious that Unity was in play mode. Furthermore, I would like to add that I got confused a few times when editing locally in other projects. After a while, I did not remember that I was still in the local view and I was wondering why it did nothing when clicking the other objects in the Outliner. It was not a major problem, but more a glitch in the user experience. Now that I know that, I’m more aware. To come back to this problem that I reported above, I never suspected this possibility because I never thought that I entered the local view. My reference of entering the local view is sometimes more in my head than what I see on the screen. I must have entered the local view accidentally. The original project had objects of the space with stars and the view looked like the space. The objects were either small or extremely large. I was working mainly in render mode. Nothing so obvious to notice an object being isolated. Here is some solution to this design issue. * It makes no sense to be able to continue to select other objects in the Outliner if I’m in the local view. That allows me to change some properties of these objects in the panels just underneath. This is a mixed design. * Even in edit mode, I’m still able to select other objects and it appears to me pretty similar to the local view design in terms of problems. * Whether it is the local view or edit mode, it should disable other possibilities not related and that can confuse the user. In many UI from other software, the notion of “grayed out” menu or link is common. Do you think, you could add that (making the local view and more obvious) as a task to modify the UI?
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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

Changed status from 'Needs Triage' to: 'Archived'
Philipp Oeser self-assigned this 2020-11-06 10:09:02 +01:00
Member

I suggest that you make it clearer when the local view is used

Here is some solution to this design issue.

Thanks for the report, feedback is always welcome, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.
For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

> I suggest that you make it clearer when the local view is used > Here is some solution to this design issue. Thanks for the report, feedback is always welcome, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
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#82443
No description provided.