Viewport redraws unnecessarily after each selection when using Eevee in look-dev or rendered modes #75204

New Issue

Jesse Yurkovich · 2020-03-30T06:33:51+02:00

Jesse Yurkovich commented

2020-03-30 06:33:51 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66

Blender Version
Broken: version: 2.83 (sub 11), branch: master, commit date: 2020-03-29 21:36, hash: a103d09df4
Broken: version: 2.83 (sub 10), branch: master, commit date: 2020-03-21 20:58, hash: 9e8afa8817
Worked: n/a

Short description of error
The viewport will unnecessarily redraw each time a selection change occurs when using Eevee's rendered mode or look-dev mode. This does not occur with the Cycles Rendered viewport.

Exact steps for others to reproduce the error
Load the attached .blend
badredraws.blend

Contains a default cube, a ground plane, and 1 large radius light (to make it obvious that things are redrawing)
Go into look-dev or rendered modes with Eevee as the render engine
Select each object in the scene and notice that the viewport redraws each time a new selection is made (obvious due to the flickering of the shadows)
If switched to cycles rendered mode, selection changes do not cause re-rendering

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66 **Blender Version** Broken: version: 2.83 (sub 11), branch: master, commit date: 2020-03-29 21:36, hash: `a103d09df4` Broken: version: 2.83 (sub 10), branch: master, commit date: 2020-03-21 20:58, hash: `9e8afa8817` Worked: n/a **Short description of error** The viewport will unnecessarily redraw each time a selection change occurs when using Eevee's rendered mode or look-dev mode. This does not occur with the Cycles Rendered viewport. **Exact steps for others to reproduce the error** Load the attached .blend [badredraws.blend](https://archive.blender.org/developer/F8436294/badredraws.blend) - Contains a default cube, a ground plane, and 1 large radius light (to make it obvious that things are redrawing) - Go into look-dev or rendered modes with Eevee as the render engine - Select each object in the scene and notice that the viewport redraws each time a new selection is made (obvious due to the flickering of the shadows) - If switched to cycles rendered mode, selection changes do not cause re-rendering

Jesse Yurkovich commented

2020-03-30 06:33:51 +02:00

Added subscriber: @deadpin

Jeroen Bakker commented

2020-03-30 08:17:35 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2020-03-30 08:17:35 +02:00

Cycles has a own copy of the scene and synchronizes this when no differences is found it will continue rendering from the same it was at. EEVEE and workbench doesn't have this mechanism and a redraw of the 3d viewport will just do a redraw.

Adding similar technique to EEVEE and workbench would increase memory need. I'm not sure if we want to this kind of optimizations due the drawbacks (performance, memory, complexity) it may have. I would not categorize this as a bug, as the current code works as designed. If we want to solve this for the draw engines we need to come up with a better implementation. for example selection will not trigger a full redraw, but only a redraw of the overlay. This is currently not supported and needs to be designed/developed from scratch.

Cycles has a own copy of the scene and synchronizes this when no differences is found it will continue rendering from the same it was at. EEVEE and workbench doesn't have this mechanism and a redraw of the 3d viewport will just do a redraw. Adding similar technique to EEVEE and workbench would increase memory need. I'm not sure if we want to this kind of optimizations due the drawbacks (performance, memory, complexity) it may have. I would not categorize this as a bug, as the current code works as designed. If we want to solve this for the draw engines we need to come up with a better implementation. for example selection will not trigger a full redraw, but only a redraw of the overlay. This is currently not supported and needs to be designed/developed from scratch.

Ankit Meel commented

2020-03-30 08:36:50 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2020-03-30 08:36:50 +02:00

#73992 (Every click updates the cycles viewport render. It not happen in previous versions.) this report says the opposite: while using cycles, a click (that selects an object) the scene updates.

edit: this report is still correct though, wasn't trying to close. Just link possibly related reports

#73992 (Every click updates the cycles viewport render. It not happen in previous versions.) this report says the opposite: while using cycles, a click (that selects an object) the scene updates. edit: this report is still correct though, wasn't trying to close. Just link possibly related reports

Richard Antalik commented

2020-03-30 10:31:43 +02:00

Added subscriber: @iss

Richard Antalik commented

2020-03-30 10:31:43 +02:00

If switched to cycles rendered mode, selection changes do not cause re-rendering

Checked out a103d09df4 and I can not reproduce this. Should we investigate this if it really happens (change report to "missing update")?

>If switched to cycles rendered mode, selection changes do not cause re-rendering Checked out `a103d09df4` and I can not reproduce this. Should we investigate this if it really happens (change report to "missing update")?

Germano Cavalcante commented

2020-03-31 19:24:19 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-03-31 19:24:19 +02:00

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

Germano Cavalcante commented

2020-03-31 19:24:19 +02:00

Given @Jeroen-Bakker's comment, I intended to mark this as a known issue.
But I was unable to replicate the behavior described for Cycles.
I tested it in different versions. Is there anything missing in the description?

Given @Jeroen-Bakker's comment, I intended to mark this as a known issue. But I was unable to replicate the behavior described for Cycles. I tested it in different versions. Is there anything missing in the description?

Jesse Yurkovich commented

2020-03-31 19:33:04 +02:00

A known issue is fine I guess albeit a bit unfortunate.

Cycles does not have the problem in my tests at least. It was only mentioned as a comparison against Eevee. Given what jbakker has said though, if you do find a time where cycles re-renders the viewport, during just a selection change, that should be filed as a different bug.

A known issue is fine I guess albeit a bit unfortunate. Cycles does _not_ have the problem in my tests at least. It was only mentioned as a comparison against Eevee. Given what jbakker has said though, if you do find a time where cycles re-renders the viewport, during just a selection change, that should be filed as a different bug.

Germano Cavalcante commented

2020-03-31 20:28:08 +02:00

Ah I can confirm Cycles' behavior! (before I was testing in edit mode, my mistake)
This can be resolved sometime as the code constantly changes.
But it is not really considered a bug as it works as designed.

Ah I can confirm Cycles' behavior! (before I was testing in edit mode, my mistake) This can be resolved sometime as the code constantly changes. But it is not really considered a bug as it works as designed.

Germano Cavalcante commented

2020-03-31 20:28:38 +02:00

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

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Viewport redraws unnecessarily after each selection when using Eevee in look-dev or rendered modes #75204