Lag reading viewport depth buffer in LookDev mode #68206

Closed
opened 2019-08-04 06:49:46 +02:00 by Jelle · 36 comments

System Information
Operating system: macOS Sierra version 10.12.6
Graphics card: Radeon Pro 55 2048 MB

Blender Version
Broken: ( 2.80 )
Worked: (optional) ( 2.80, 3325b19ee7, branch: blender 2.7, 2019-06-06 )

Short description of error

In LookDev mode, zooming is extremely choppy. This topic was adressed earlier and dismissed a hardware issue. But the problem did not exist in an earlier version, suggesting it probably could be a software related issue. Check the video beneath.

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file.

devlook slow zooming.mp4

**System Information** Operating system: macOS Sierra version 10.12.6 Graphics card: Radeon Pro 55 2048 MB **Blender Version** Broken: ( 2.80 ) Worked: (optional) ( 2.80, 3325b19ee7fd, branch: blender 2.7, 2019-06-06 ) **Short description of error** In LookDev mode, zooming is extremely choppy. This topic was adressed earlier and dismissed a hardware issue. But the problem did not exist in an earlier version, suggesting it probably could be a software related issue. Check the video beneath. **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file. [devlook slow zooming.mp4](https://archive.blender.org/developer/F7648239/devlook_slow_zooming.mp4)
Author

Added subscriber: @Jelleeey

Added subscriber: @Jelleeey

#89142 was marked as duplicate of this issue

#89142 was marked as duplicate of this issue

#73827 was marked as duplicate of this issue

#73827 was marked as duplicate of this issue

#63026 was marked as duplicate of this issue

#63026 was marked as duplicate of this issue

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

How are you zooming? Using the scroll wheel or by using the modifier key and dragging you mouse, or a different way?

How are you zooming? Using the scroll wheel or by using the modifier key and dragging you mouse, or a different way?
Author

Hi William,

I use the scroll wheel to zoom in and out.

Hi William, I use the scroll wheel to zoom in and out.

Is it also choppy when zooming using modifier+mouse-dragging?

Is it also choppy when zooming using modifier+mouse-dragging?
Author

Interesting. Using ctrl + mmb (drag) the zooming goes smooth.

Interesting. Using ctrl + mmb (drag) the zooming goes smooth.
Author

I found the problem. For some reason, unchecking this box in the keymap for zoom in / zoom out resolves the problem. I unchecked this also for the pan and orbit keymap, as i discovered it acts more responsive with this checkbox off. However, maybe it is still a good idea to resolve this weird bug.

EDIT: This solution is not valid as it creates a new problem where the autodepth and 'zoom to mouse position' features are not working anymore.

Screen Shot 2019-08-04 at 16.41.27.png

I found the problem. For some reason, unchecking this box in the keymap for zoom in / zoom out resolves the problem. I unchecked this also for the pan and orbit keymap, as i discovered it acts more responsive with this checkbox off. However, maybe it is still a good idea to resolve this weird bug. EDIT: This solution is not valid as it creates a new problem where the autodepth and 'zoom to mouse position' features are not working anymore. ![Screen Shot 2019-08-04 at 16.41.27.png](https://archive.blender.org/developer/F7648772/Screen_Shot_2019-08-04_at_16.41.27.png)
Campbell Barton was assigned by William Reynish 2019-08-04 16:49:33 +02:00

Added subscriber: @ideasman42

Added subscriber: @ideasman42

@ideasman42 Unsure how to triage this?

@ideasman42 Unsure how to triage this?
  • Do you have "Auto Depth" preference enabled?
  • Does this happen with Factory Settings loaded?

It's possible getting the depth under the cursor is slower in look-dev mode, this only happens once w/ Ctrl-MMB, for mouse wheel it happens on every event because zooming isn't a mode in that case and each event could be over a different surface.

- Do you have "Auto Depth" preference enabled? - Does this happen with [Factory Settings ](https://docs.blender.org/manual/en/dev/getting_started/configuration/defaults.html#loading-factory-settings) loaded? ---- It's possible getting the depth under the cursor is slower in look-dev mode, this only happens once w/ Ctrl-MMB, for mouse wheel it happens on every event because zooming isn't a mode in that case and each event could be over a different surface.
Author

In #68206#745186, @ideasman42 wrote:

  • Do you have "Auto Depth" preference enabled?
  • Does this happen with Factory Settings loaded?

It's possible getting the depth under the cursor is slower in look-dev mode, this only happens once w/ Ctrl-MMB, for mouse wheel it happens on every event because zooming isn't a mode in that case and each event could be over a different surface.

I have auto depth enabled and use the factory settings in both versions (working and not working versions). I understand now that the issue is related to the autodepth feature. I understand what you say about the wheel zoom, where it sees every scroll as an event where the autodepth has to be recalculated. However, this does not explain why this behavior is not present in the previous version ( 2.80, 3325b19ee7, branch: blender 2.7, 2019-06-06 ).

> In #68206#745186, @ideasman42 wrote: > - Do you have "Auto Depth" preference enabled? > - Does this happen with [Factory Settings ](https://docs.blender.org/manual/en/dev/getting_started/configuration/defaults.html#loading-factory-settings) loaded? > > > ---- > > It's possible getting the depth under the cursor is slower in look-dev mode, this only happens once w/ Ctrl-MMB, for mouse wheel it happens on every event because zooming isn't a mode in that case and each event could be over a different surface. I have auto depth enabled and use the factory settings in both versions (working and not working versions). I understand now that the issue is related to the autodepth feature. I understand what you say about the wheel zoom, where it sees every scroll as an event where the autodepth has to be recalculated. However, this does not explain why this behavior is not present in the previous version ( 2.80, 3325b19ee7fd, branch: blender 2.7, 2019-06-06 ).
Author

Is this issue still looked at?

Is this issue still looked at?
Author

I checked out the newest version (2.81 alpha ) and the lookdev mode performs well again.

EDIT: The issue still persists. Upon closer inspection it appears that the 2.81 alpha worked because the autodepth was turned off when I tried it. This was because the new build started up with the default user preferences.

I checked out the newest version (2.81 alpha ) and the lookdev mode performs well again. EDIT: The issue still persists. Upon closer inspection it appears that the 2.81 alpha worked because the autodepth was turned off when I tried it. This was because the new build started up with the default user preferences.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Author

Changed status from 'Resolved' to: 'Open'

Changed status from 'Resolved' to: 'Open'
Jelle reopened this issue 2019-09-23 09:40:10 +02:00
Author

In the 2.81 alpha this issue still appears (Version 2.81 (2.81 2019-09-12)) This issue is really annoying. Could someone please look into this?

In the 2.81 alpha this issue still appears (Version 2.81 (2.81 2019-09-12)) This issue is really annoying. Could someone please look into this?

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

I can confirm a slight delay in LookDev mode, it can be seen when placing the cursor too.

However the difference isn't much on my system, making profiler results not highlight the cause so easily. Marking this as TODO.

I can confirm a slight delay in LookDev mode, it can be seen when placing the cursor too. However the difference isn't much on my system, making profiler results not highlight the cause so easily. Marking this as TODO.
Campbell Barton changed title from Slow zooming in LookDev to Lag reading viewport depth buffer in LookDev mode 2020-01-13 12:17:54 +01:00
Campbell Barton removed their assignment 2020-01-13 12:17:54 +01:00

Removed subscriber: @ideasman42

Removed subscriber: @ideasman42

Added subscriber: @ThomasRadeke

Added subscriber: @ThomasRadeke
Added subscribers: @olyandros, @fclem, @jenkm, @ckohl_art, @Brunomendesgussoni, @iss, @John_Do, @AbidMaqbool, @WickedInsignia, @DanielPaul, @Mets, @lichtwerk, @brecht, @ideasman42
Added subscribers: @xan2622, @MichaelHermann, @HooglyBoogly, @thsampa, @Pasang

After a while, I checked this (and #73827) again and I can no longer reproduce it. (2.90.1 or 2.91 Beta) Maybe it got fixed somewhere along the way.?

After a while, I checked this (and #73827) again and I can no longer reproduce it. (2.90.1 or 2.91 Beta) Maybe it got fixed somewhere along the way.?

This comment was removed by @WickedInsignia

*This comment was removed by @WickedInsignia*

@Jelleeey can you redo this in 2.91 or current daily build? (2.92 alpha).

@Jelleeey can you redo this in 2.91 or current daily build? (2.92 alpha).

This issue is still present. I don't see any difference compared to previous versions.

This issue is still present. I don't see any difference compared to previous versions.

Just tried with 2.91.0 Beta, the lag is still present when Auto Depth is turned on.
I understand that re-using data you already have (depth buffer) is the preferred way to do things, but for zooming you're really just using one pixel of the entire buffer, right?
Wouldn't it be faster to do a single raycast to determine depth than to read a buffer that is only going to become bigger and bigger as monitor resolutions increase?
I'm using a 4K screen. When I resize my Blender window to be ~1/4th of the screen (e.g. Full HD), the lag is gone (or at least not noticable anymore).

Just tried with 2.91.0 Beta, the lag is still present when Auto Depth is turned on. I understand that re-using data you already have (depth buffer) is the preferred way to do things, but for zooming you're really just using one pixel of the entire buffer, right? Wouldn't it be faster to do a single raycast to determine depth than to read a buffer that is only going to become bigger and bigger as monitor resolutions increase? I'm using a 4K screen. When I resize my Blender window to be ~1/4th of the screen (e.g. Full HD), the lag is gone (or at least not noticable anymore).

I had bought a 4k monitor to use in Blender, but it was a waste of money, as I can't use 'Auto depth', I had to use my old full hd monitor.

I had bought a 4k monitor to use in Blender, but it was a waste of money, as I can't use 'Auto depth', I had to use my old full hd monitor.

OK, with the Viewport in Fullscreen on a 4K Monitor, I can also see the lag again.
@Brunomendesgussoni : For me, the workaround was to turn off Viewport Anti-Aliasing.

OK, with the Viewport in Fullscreen on a 4K Monitor, I can also see the lag again. @Brunomendesgussoni : For me, the workaround was to turn off Viewport Anti-Aliasing.
Author

In #68206#1047609, @ideasman42 wrote:
@Jelleeey can you redo this in 2.91 or current daily build? (2.92 alpha).

@ideasman42 For me the issue still persists in the newest build (2.92 alpha)

> In #68206#1047609, @ideasman42 wrote: > @Jelleeey can you redo this in 2.91 or current daily build? (2.92 alpha). @ideasman42 For me the issue still persists in the newest build (2.92 alpha)

Added subscriber: @2046411367

Added subscriber: @2046411367
Member

Added subscribers: @tonpix, @PratikPB2123

Added subscribers: @tonpix, @PratikPB2123

I believe this has long been fixed, especially with the new Metal backend. If not the issue can be reopened.

I believe this has long been fixed, especially with the new Metal backend. If not the issue can be reopened.
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2024-02-07 18:07:06 +01: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
13 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#68206
No description provided.