Object disappared and glichted when switching between normal view and quad views #76216

Closed
opened 2020-04-29 09:15:53 +02:00 by Le Giang · 21 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.1 26.20.15029.20013

Blender Version
Broken: version: 2.83 (sub 15), branch: master, commit date: 2020-04-28 20:40, hash: 05274ca829
Worked: 2.82a

Short description of error
Object disappared when switching between normal view and quad views, doing this repeatedly can cause:

  • selection outline always draws
  • sometimes geometry disappears
  • sometimes other overlays disappear [grid, lights, camera, ...]
  • sometimes geometry draws as if in xray

Object glichted sometimes when switching between normal view and quad views in the view port if viewport aa set to 32

Exact steps for others to reproduce the error
Object disappared bug_report_3_1.gif

Object glichted bug_report_3_2.gif

Debug logs
Object disappared
blender_debug_output.txt
blender_system_info.txt

Object glichted
blender_debug_output.txt
blender_system_info.txt

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.1 26.20.15029.20013 **Blender Version** Broken: version: 2.83 (sub 15), branch: master, commit date: 2020-04-28 20:40, hash: `05274ca829` Worked: 2.82a **Short description of error** Object disappared when switching between normal view and quad views, doing this repeatedly can cause: - selection outline always draws - sometimes geometry disappears - sometimes other overlays disappear [grid, lights, camera, ...] - sometimes geometry draws as if in xray Object glichted sometimes when switching between normal view and quad views in the view port if viewport aa set to 32 **Exact steps for others to reproduce the error** Object disappared ![bug_report_3_1.gif](https://archive.blender.org/developer/F8500638/bug_report_3_1.gif) Object glichted ![bug_report_3_2.gif](https://archive.blender.org/developer/F8500670/bug_report_3_2.gif) **Debug logs** Object disappared [blender_debug_output.txt](https://archive.blender.org/developer/F8501090/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8501091/blender_system_info.txt) Object glichted [blender_debug_output.txt](https://archive.blender.org/developer/F8501092/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8501093/blender_system_info.txt)
Author

Added subscriber: @jangst.1024

Added subscriber: @jangst.1024
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member
> 20.4.1 There's a 20.4.2 available. https://www.amd.com/en/support/graphics/radeon-400-series/radeon-rx-400-series/radeon-rx-470
Author

In #76216#919862, @ankitm wrote:

20.4.1

There's a 20.4.2 available. https://www.amd.com/en/support/graphics/radeon-400-series/radeon-rx-400-series/radeon-rx-470

it's still happens in the lastest driver

> In #76216#919862, @ankitm wrote: >> 20.4.1 > There's a 20.4.2 available. https://www.amd.com/en/support/graphics/radeon-400-series/radeon-rx-400-series/radeon-rx-470 it's still happens in the lastest driver
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Please run Blender_debug_gpu.cmd, get the glitch & upload the two files it mentions.

Please run Blender_debug_gpu.cmd, get the glitch & upload the two files it mentions.
Author

In #76216#920072, @ankitm wrote:
Please run Blender_debug_gpu.cmd, get the glitch & upload the two files it mentions.

i attached the debug file in the task

> In #76216#920072, @ankitm wrote: > Please run Blender_debug_gpu.cmd, get the glitch & upload the two files it mentions. i attached the debug file in the task
Member

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'
Member

Added subscribers: @fclem, @lichtwerk

Added subscribers: @fclem, @lichtwerk
Member

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

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

Can confirm.

Caused by c476c36e40

Might need a kick to wpd->view_updated = true (similar to 133bf05b18, a6dd22d431, ed44bb902d, 02f7a6b2bd ...)

CC @fclem

Can confirm. Caused by c476c36e40 Might need a kick to `wpd->view_updated = true` (similar to 133bf05b18, a6dd22d431, ed44bb902d, 02f7a6b2bd ...) CC @fclem
Member

What I mean is:
P1363: T76216_snippet



diff --git a/source/blender/draw/engines/workbench/workbench_data.c b/source/blender/draw/engines/workbench/workbench_data.c
index 2e8119fca2f..c71676d24b1 100644
--- a/source/blender/draw/engines/workbench/workbench_data.c
+++ b/source/blender/draw/engines/workbench/workbench_data.c
@@ -214,6 +214,13 @@ void workbench_private_data_init(WORKBENCH_PrivateData *wpd)
     rv3d->rflag &= ~RV3D_GPULIGHT_UPDATE;
   }
 
+  /* FIXME: This reproduce old behavior when workbench was separated in 2 engines.
+   * But this is a workaround for a missing update tagging. */
+  if ((rv3d != NULL) && (rv3d->viewlock_quad & RV3D_VIEWLOCK_INIT)) {
+    wpd->view_updated = true;
+    rv3d->viewlock_quad &= ~RV3D_VIEWLOCK_INIT;
+  }
+
   if (!v3d || (v3d->shading.type == OB_RENDER && BKE_scene_uses_blender_workbench(scene))) {
     /* FIXME: This reproduce old behavior when workbench was separated in 2 engines.
      * But this is a workaround for a missing update tagging from operators. */

(but of course, we shouldnt be messing with RV3D_VIEWLOCK_INIT like that...)

What I mean is: [P1363: T76216_snippet](https://archive.blender.org/developer/P1363.txt) ``` diff --git a/source/blender/draw/engines/workbench/workbench_data.c b/source/blender/draw/engines/workbench/workbench_data.c index 2e8119fca2f..c71676d24b1 100644 --- a/source/blender/draw/engines/workbench/workbench_data.c +++ b/source/blender/draw/engines/workbench/workbench_data.c @@ -214,6 +214,13 @@ void workbench_private_data_init(WORKBENCH_PrivateData *wpd) rv3d->rflag &= ~RV3D_GPULIGHT_UPDATE; } + /* FIXME: This reproduce old behavior when workbench was separated in 2 engines. + * But this is a workaround for a missing update tagging. */ + if ((rv3d != NULL) && (rv3d->viewlock_quad & RV3D_VIEWLOCK_INIT)) { + wpd->view_updated = true; + rv3d->viewlock_quad &= ~RV3D_VIEWLOCK_INIT; + } + if (!v3d || (v3d->shading.type == OB_RENDER && BKE_scene_uses_blender_workbench(scene))) { /* FIXME: This reproduce old behavior when workbench was separated in 2 engines. * But this is a workaround for a missing update tagging from operators. */ ``` (but of course, we shouldnt be messing with RV3D_VIEWLOCK_INIT like that...)
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Member

Seems like 2 tickets in one. The glitch has been reported already so I assume this ticket is about the tagging...

I wasn't able to reproduce the quad view tagging issue on latest build. @lichtwerk do think this is a platform specific problem? If so I can try building this configuration. Just wanna check before spending much time building the configuration.

Tested myself on Linux AMD Vega64 and Windows Intel

Seems like 2 tickets in one. The glitch has been reported already so I assume this ticket is about the tagging... I wasn't able to reproduce the quad view tagging issue on latest build. @lichtwerk do think this is a platform specific problem? If so I can try building this configuration. Just wanna check before spending much time building the configuration. Tested myself on Linux AMD Vega64 and Windows Intel
Member

In #76216#926675, @Jeroen-Bakker wrote:
Seems like 2 tickets in one. The glitch has been reported already so I assume this ticket is about the tagging...

Mind sharing which the other report is?

I wasn't able to reproduce the quad view tagging issue on latest build. @lichtwerk do think this is a platform specific problem? If so I can try building this configuration. Just wanna check before spending much time building the configuration.

Cannot tell (I only have access to this one machine...) And I still have it on
System Information
Operating system: Linux-5.5.13-200.fc31.x86_64-x86_64-with-fedora-31-Thirty_One 64 Bits
Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64
version: 2.90 (sub 0), branch: master, commit date: 2020-05-08 03:43, hash: b4d50d3f07

> In #76216#926675, @Jeroen-Bakker wrote: > Seems like 2 tickets in one. The glitch has been reported already so I assume this ticket is about the tagging... Mind sharing which the other report is? > I wasn't able to reproduce the quad view tagging issue on latest build. @lichtwerk do think this is a platform specific problem? If so I can try building this configuration. Just wanna check before spending much time building the configuration. Cannot tell (I only have access to this one machine...) And I still have it on **System Information** Operating system: Linux-5.5.13-200.fc31.x86_64-x86_64-with-fedora-31-Thirty_One 64 Bits Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64 version: 2.90 (sub 0), branch: master, commit date: 2020-05-08 03:43, hash: `b4d50d3f07`
Member

@lichtwerk, seem that other tickets are for Intel and NVidia. perhaps we just split these tickets.

@lichtwerk, seem that other tickets are for Intel and NVidia. perhaps we just split these tickets.
Member

But other tickets are specifically about quadview? Which other reports are these? [I have no other glitches]

But other tickets are specifically about quadview? Which other reports are these? [I have no other glitches]
Member

I was able to reproduce this issue but only on Windows. I did reproduce it on Intel and multiple AMD cards.

I was able to reproduce this issue but only on Windows. I did reproduce it on Intel and multiple AMD cards.

I was able to reproduce on Nvidia GTX960 + Windows.

I was able to reproduce on Nvidia GTX960 + Windows.

This issue was referenced by a1363f74bf

This issue was referenced by a1363f74bf168279e5b8eb0fede000513a5d919a

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Clément Foucault self-assigned this 2020-05-11 17:54:24 +02:00
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
6 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#76216
No description provided.