3DViewport is missing overlay. #95052

Closed
opened 2022-01-19 11:39:28 +01:00 by Guido · 36 comments

System Information
Operating system: macOS-12.1-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.101

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-19 09:28, hash: 71386c08f1
last version that worked: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-16 23:26, hash: 34d424fd64

Short description of error
Now blender opens up again after yesterday, but now 3dvieport shows no grid, selection... you just see the cube in a big empty.
In wireframe you'll see nothing, the other modes you'll see the cube but all without visuals like object type, gizmos...

Exact steps for others to reproduce the error

  • Click on the top Workspace tabs for the Shader Editor
  • Change to Solid view
  • Bug will change entire viewport to black
  • If you return to the Layout Workspace the viewport will also be black.

It doesn't happen with builds built on MacOS 12

**System Information** Operating system: macOS-12.1-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.101 **Blender Version** Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-19 09:28, hash: `71386c08f1` last version that worked: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-16 23:26, hash: 34d424fd64 **Short description of error** Now blender opens up again after yesterday, but now 3dvieport shows no grid, selection... you just see the cube in a big empty. In wireframe you'll see nothing, the other modes you'll see the cube but all without visuals like object type, gizmos... **Exact steps for others to reproduce the error** * Click on the top Workspace tabs for the Shader Editor * Change to Solid view * Bug will change entire viewport to black * If you return to the Layout Workspace the viewport will also be black. It doesn't happen with builds built on MacOS 12
Author

Added subscriber: @Nurb2Kea

Added subscriber: @Nurb2Kea

#95119 was marked as duplicate of this issue

#95119 was marked as duplicate of this issue

#95083 was marked as duplicate of this issue

#95083 was marked as duplicate of this issue

#95071 was marked as duplicate of this issue

#95071 was marked as duplicate of this issue
Author

Question: Are those builds getting tested in any kind (if it even starts up) before upload to git etc.., OR
how is it working with the daily builds? Is it automated !?

Question: Are those builds getting tested in any kind (if it even starts up) before upload to git etc.., OR how is it working with the daily builds? Is it automated !?
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Member

Hi Nurb2Kea!

Yes they are tested but not all developers have the same hardware as you have. So that is always tricky.
What is currently going on is that all GPU code is rewritten, but as the developers responsible for it doesn't own a Mac with a AMD GPU we need to rely on the community for testing platforms that we don't have. I will see if I can find someone who can lend me a similar Mac.

Hi Nurb2Kea! Yes they are tested but not all developers have the same hardware as you have. So that is always tricky. What is currently going on is that all GPU code is rewritten, but as the developers responsible for it doesn't own a Mac with a AMD GPU we need to rely on the community for testing platforms that we don't have. I will see if I can find someone who can lend me a similar Mac.
Author

I'm pretty sure any mac will have this issue.
Anyways, hope it's getting tested soon.

It's the 3 day's in a row that it isn't working. see https://developer.blender.org/T95039

I'm pretty sure any mac will have this issue. Anyways, hope it's getting tested soon. It's the 3 day's in a row that it isn't working. see https://developer.blender.org/T95039
Author

It's continueing on the following build:

downloaded from blender.org and compiled, both the same issue:

Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-20 00:43, hash: b7fe27314b

It's continueing on the following build: downloaded from blender.org and compiled, both the same issue: Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-20 00:43, hash: `b7fe27314b`
Member

Added subscribers: @CookItOff, @PratikPB2123

Added subscribers: @CookItOff, @PratikPB2123

I can confirm this is happening with M1 Mac. I didn’t notice in the last two builds as “Shader Editor Crash Bug” was just resolved and would allow me to enter that workspace.

Want to add that my steps to trigger a black viewport are a little different as noted in my bug report that has been merged with this one.

https://developer.blender.org/T95071

I can confirm this is happening with M1 Mac. I didn’t notice in the last two builds as “Shader Editor Crash Bug” was just resolved and would allow me to enter that workspace. Want to add that my steps to trigger a black viewport are a little different as noted in my bug report that has been merged with this one. https://developer.blender.org/T95071
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

Can't redo on Intel HD 6000 macos 12.1 or AMD Radeon Pro 5300M macos 11.x with blender-3.1.0-alpha+master.b7fe27314b25-darwin.x86_64-release.dmg

Can't redo on Intel HD 6000 macos 12.1 or AMD Radeon Pro 5300M macos 11.x with `blender-3.1.0-alpha+master.b7fe27314b25-darwin.x86_64-release.dmg`

Added subscriber: @Steve-Hanff

Added subscriber: @Steve-Hanff

Same here on the M1 Pro with OsX 12.1

Same here on the M1 Pro with OsX 12.1
Member

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

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

confirming due to multiple reports

confirming due to multiple reports
Member

Can someone add a screenshot. I wasn't able to reproduce it a mac m1. Will try tomorrow on another mac. But a screenshot might point me into the correct direction where to look.

Can someone add a screenshot. I wasn't able to reproduce it a mac m1. Will try tomorrow on another mac. But a screenshot might point me into the correct direction where to look.

In #95052#1292046, @Jeroen-Bakker wrote:
Can someone add a screenshot. I wasn't able to reproduce it a mac m1. Will try tomorrow on another mac. But a screenshot might point me into the correct direction where to look.

I’m not at my machine right now but these are the steps.
•Click on the top Workspace tabs for the Shader Editor
•Change to Solid view
•Bug will change entire viewport to black
•If you return to the Layout Workspace the viewport will also be black.

> In #95052#1292046, @Jeroen-Bakker wrote: > Can someone add a screenshot. I wasn't able to reproduce it a mac m1. Will try tomorrow on another mac. But a screenshot might point me into the correct direction where to look. I’m not at my machine right now but these are the steps. •Click on the top Workspace tabs for the Shader Editor •Change to Solid view •Bug will change entire viewport to black •If you return to the Layout Workspace the viewport will also be black.

sure here you go, this is how mine looks after switching to the shading tab and back.
In wireframe mode it is completely black and in material preview it looks ok.
Screenshot 2022-01-20 at 21.09.35.png
Screenshot 2022-01-20 at 21.11.10.png

sure here you go, this is how mine looks after switching to the shading tab and back. In wireframe mode it is completely black and in material preview it looks ok. ![Screenshot 2022-01-20 at 21.09.35.png](https://archive.blender.org/developer/F12813370/Screenshot_2022-01-20_at_21.09.35.png) ![Screenshot 2022-01-20 at 21.11.10.png](https://archive.blender.org/developer/F12813380/Screenshot_2022-01-20_at_21.11.10.png)
Author

In #95052#1292098, @Steve-Hanff wrote:
sure here you go, this is how mine looks after switching to the shading tab and back.
In wireframe mode it is completely black and in material preview it looks ok.
Screenshot 2022-01-20 at 21.09.35.png
Screenshot 2022-01-20 at 21.11.10.png

ditto ! On latest Intel MAC !

> In #95052#1292098, @Steve-Hanff wrote: > sure here you go, this is how mine looks after switching to the shading tab and back. > In wireframe mode it is completely black and in material preview it looks ok. > ![Screenshot 2022-01-20 at 21.09.35.png](https://archive.blender.org/developer/F12813370/Screenshot_2022-01-20_at_21.09.35.png) > ![Screenshot 2022-01-20 at 21.11.10.png](https://archive.blender.org/developer/F12813380/Screenshot_2022-01-20_at_21.11.10.png) ditto ! On latest Intel MAC !

Added subscriber: @Franfairline

Added subscriber: @Franfairline

I have the same issue on my Macbook M1 with the last version 3.1

Only if set to Solid or Wireframe when switching between Shading and previous tab

I have the same issue on my Macbook M1 with the last version 3.1 Only if set to Solid or Wireframe when switching between Shading and previous tab
Author

Continuing with build: Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-20 22:26, hash: 5fca280c80

Continuing with build: Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-20 22:26, hash: `5fca280c80`
Member

@Nurb2Kea please don't comment on all broken builds This isn't helpful and will only make it harder for me to extract useful messages from noise. Today I will be working on this task.

Looking at the images provided it seems that The color management merge shader isn't doing what it should be doing.

I wasn't able to reproduce it on a first gen M1 with my own builds, but I was able to reproduce it with builds downloaded from the buildbot (steps to reproduce is to switch to solid mode in the shader workflow). I don't get it when starting Blender from scratch. IIRC buildbot uses a different MacOS.

Screenshot 2022-01-21 at 07.59.14.png

system-info.txt

#94900 (Sequencer Window background is shows green) might be related and is better reproduceable. If that doesn't solve it the next step would be to check the differences of the colour management shaders. After that would see if I can get access to a buildbot similar machine.

@Nurb2Kea please don't comment on all broken builds This isn't helpful and will only make it harder for me to extract useful messages from noise. Today I will be working on this task. Looking at the images provided it seems that The color management merge shader isn't doing what it should be doing. I wasn't able to reproduce it on a first gen M1 with my own builds, but I was able to reproduce it with builds downloaded from the buildbot (steps to reproduce is to switch to solid mode in the shader workflow). I don't get it when starting Blender from scratch. IIRC buildbot uses a different MacOS. ![Screenshot 2022-01-21 at 07.59.14.png](https://archive.blender.org/developer/F12814023/Screenshot_2022-01-21_at_07.59.14.png) [system-info.txt](https://archive.blender.org/developer/F12814024/system-info.txt) #94900 (Sequencer Window background is shows green) might be related and is better reproduceable. If that doesn't solve it the next step would be to check the differences of the colour management shaders. After that would see if I can get access to a buildbot similar machine.
Jeroen Bakker changed title from 3DViewport is missing visuals . No grid, selections,...to see to 3DViewport is missing overlay. 2022-01-21 07:39:32 +01:00
Author

First you tell that you relay on user testing, than you don't want updates on it.
Makes no sense, BUT explains why it took soo long to understand what's the issue.

That the following build isn't working is more important than someone telling he got the same problem...
And why are dev's taking on tasks, that they can't test/proofe it on a mac/linux mashine, not even a remote machine to test on...

Makes me sick of getting asked for help and after days of nothing happen from dev side, you'll end up as 'noise' comment.
And in your case I wouldn't talk so loud about 'useful'. Your help so far wasn't useful at all, but time consuming.

Thanks in advance

First you tell that you relay on user testing, than you don't want updates on it. Makes no sense, BUT explains why it took soo long to understand what's the issue. That the following build isn't working is more important than someone telling he got the same problem... And why are dev's taking on tasks, that they can't test/proofe it on a mac/linux mashine, not even a remote machine to test on... Makes me sick of getting asked for help and after days of nothing happen from dev side, you'll end up as 'noise' comment. And in your case I wouldn't talk so loud about 'useful'. Your help so far wasn't useful at all, but time consuming. Thanks in advance
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

@Nurb2Kea : help testing is always welcome (but please: also tone down a bit, we try to keep respect of each others work if possible).
The task has been confirmed, now someone is working on it, so it will remain broken until further notice, if resolved though, there'll be an automatic message here.

@Nurb2Kea : help testing is always welcome (but please: also tone down a bit, we try to keep respect of each others work if possible). The task has been confirmed, now someone is working on it, so it will remain broken until further notice, if resolved though, there'll be an automatic message here.
Jeroen Bakker self-assigned this 2022-01-21 12:13:46 +01:00

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

Added subscriber: @Memento

Added subscriber: @Memento

This issue was referenced by 93065a67c6

This issue was referenced by 93065a67c664240bf1df3b303623292b41daf066

This issue was referenced by 5e51a5e8a4

This issue was referenced by 5e51a5e8a4847c4f42ca44e260b82d08fda7f051
Member

Added subscriber: @Kent-Davis

Added subscriber: @Kent-Davis

I wanted to note that I’m not getting this to happen anymore on the latest build Jan 22 (1f026a3db9) but I don’t see a “Resolved” indicator for this task.

Thanks

I wanted to note that I’m not getting this to happen anymore on the latest build Jan 22 (1f026a3db909) but I don’t see a “Resolved” indicator for this task. Thanks
Member

Yes. I added a work around, but still need to split this task in multiple to reflect the current state

Yes. I added a work around, but still need to split this task in multiple to reflect the current state
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
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
11 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#95052
No description provided.