Camera lag with Auto Depth turned on #63026

Closed
opened 2019-03-27 21:08:31 +01:00 by Oliver Harries · 47 comments

System Information
Operating system: Windows 10 (1809)
Graphics card: GTX 1080

Blender Version
Broken: version: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: 211b6c29f7
Worked: Probably never

Short description of error
With Auto Depth active there is a lag by about one second until Blender reacts to my camera movements. With Auto Depth turned off the lag is gone.

Here is also a screen capture to illustrate the problem.
https://www.dropbox.com/s/xajkvcg3xawheqw/blender_28_autodepth_lag.mp4?dl=0{F6892502}

**System Information** Operating system: Windows 10 (1809) Graphics card: GTX 1080 **Blender Version** Broken: version: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: `211b6c29f7` Worked: Probably never **Short description of error** With Auto Depth active there is a lag by about one second until Blender reacts to my camera movements. With Auto Depth turned off the lag is gone. Here is also a screen capture to illustrate the problem. https://www.dropbox.com/s/xajkvcg3xawheqw/blender_28_autodepth_lag.mp4?dl=0{F6892502}
Author

Added subscriber: @olyandros

Added subscriber: @olyandros

#69357 was marked as duplicate of this issue

#69357 was marked as duplicate of this issue
Member

Added subscribers: @fclem, @ideasman42, @brecht, @lichtwerk

Added subscribers: @fclem, @ideasman42, @brecht, @lichtwerk
Member

Not sure if this can be considered a bug.

With Auto Depth a bunch of extra things have to be done (drawing ZBuff etc.) which might eat some performance on highres geometry...
Would ask @ideasman42 (maybe @fclem, @brecht as well?) if there is room for improvement here?

Not sure if this can be considered a bug. With `Auto Depth` a bunch of extra things have to be done (drawing ZBuff etc.) which might eat some performance on highres geometry... Would ask @ideasman42 (maybe @fclem, @brecht as well?) if there is room for improvement here?
Author

There is no lag with the same scene in 2.79 with or without Auto Depth. Also I notice much lower viewport performance (fps) in 2.80 compared to 2.79.

There is no lag with the same scene in 2.79 with or without Auto Depth. Also I notice much lower viewport performance (fps) in 2.80 compared to 2.79.

Closed as duplicate of #60043

Closed as duplicate of #60043

Let's first fix #60043 (macOS viewport lagging) and then see what the performance looks like for the various settings.

Let's first fix #60043 (macOS viewport lagging) and then see what the performance looks like for the various settings.

Changed status from 'Duplicate' to: 'Open'

Changed status from 'Duplicate' to: 'Open'

Wait, I confused this with another report..

Wait, I confused this with another report..

To me this kind of excessive lagging definitely sounds like a bug.

@olyandros, there have been recent changes in drawing of the depth buffer, could you verify if it's still an issue?

To me this kind of excessive lagging definitely sounds like a bug. @olyandros, there have been recent changes in drawing of the depth buffer, could you verify if it's still an issue?
Member

Added subscriber: @Mets

Added subscriber: @Mets
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Demeter Dzadik self-assigned this 2019-05-30 18:41:27 +02:00
Member

Closing because no info in over a week. Feel free to reopen.

Closing because no info in over a week. Feel free to reopen.

Added subscriber: @DanielPaul

Added subscriber: @DanielPaul

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

Unfortunately, this is still an issue, when eevee is used in a quite moderate scene with some shaders, the lag is clearly noticeable.
Deactivating auto depth feels much smoother, without any lag.

Unfortunately, this is still an issue, when eevee is used in a quite moderate scene with some shaders, the lag is clearly noticeable. Deactivating auto depth feels much smoother, without any lag.
Demeter Dzadik was unassigned by Daniel Paul 2019-08-29 15:23:43 +02:00
Clément Foucault was assigned by Daniel Paul 2019-08-29 15:23:43 +02:00
Member

Added subscribers: @WickedInsignia, @AbidMaqbool

Added subscribers: @WickedInsignia, @AbidMaqbool

Added subscriber: @Jelleeey

Added subscriber: @Jelleeey

Added subscriber: @John_Do

Added subscriber: @John_Do

Still an issue here on Blender 2.81 beta from 2019-10-12. I'm glad I've found this task, I've disabled auto-depth and it is smooth as usual.

Windows 10 1803
Threadripper 1950X
Titan X(p), 431.86

Still an issue here on Blender 2.81 beta from 2019-10-12. I'm glad I've found this task, I've disabled auto-depth and it is smooth as usual. Windows 10 1803 Threadripper 1950X Titan X(p), 431.86

Added subscriber: @iss

Added subscriber: @iss

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

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

I have not been able to reproduce this issue. Even in 2.81a

Please try the latest daily build: https://builder.blender.org/download/

If the problem persists, please let us know so we can re-open the report. Don't forget to mention the specific version you tested again.

I have not been able to reproduce this issue. Even in 2.81a Please try the latest daily build: https://builder.blender.org/download/ If the problem persists, please let us know so we can re-open the report. Don't forget to mention the specific version you tested again.

Added subscriber: @Brunomendesgussoni

Added subscriber: @Brunomendesgussoni

I think it is important for people to say what resolution they are using, because here I have a lot of problems with resolutions higher than 1080p with AUTO_DEPTH.
4k is unusable!!!!

I think it is important for people to say what resolution they are using, because here I have a lot of problems with resolutions higher than 1080p with AUTO_DEPTH. 4k is unusable!!!!

Please re-open. Still experiencing issue in 2.83.
An extra half-a-second before a middle click will register to rotate the view. This happens with meshes of ANY size, regardless of sculpting or not, and most predominantly in EEVEE and Material Preview for me. I don't really seem to experience it in Workbench. Performance dips when edit mode is used in either of the aforementioned views.
Reaction is instant with Auto-depth off.

As per Bruno's request, please note I am using a 1440p monitor.
This is also FAR more noticeable on a tablet than a mouse, with middle-click mapped to one of the pen buttons. This may be essential, since I imagine testers may be using a mouse.

My specs:
Nvidia GTX 1080
Intel i7 6700
16GB RAM
Dell UP2516D monitor running at 1440p
Wacom Intuos Pro Medium

Please re-open. Still experiencing issue in 2.83. An extra half-a-second before a middle click will register to rotate the view. This happens with meshes of ANY size, regardless of sculpting or not, and most predominantly in EEVEE and Material Preview for me. I don't really seem to experience it in Workbench. Performance dips when edit mode is used in either of the aforementioned views. Reaction is instant with Auto-depth off. As per Bruno's request, please note I am using a 1440p monitor. **This is also FAR more noticeable on a tablet than a mouse, with middle-click mapped to one of the pen buttons.** This may be essential, since I imagine testers may be using a mouse. My specs: Nvidia GTX 1080 Intel i7 6700 16GB RAM Dell UP2516D monitor running at 1440p Wacom Intuos Pro Medium

In #63026#961529, @WickedInsignia wrote:
Please re-open. Still experiencing issue in 2.83.
An extra half-a-second before a middle click will register to rotate the view. This happens with meshes of ANY size, regardless of sculpting or not, and most predominantly in EEVEE and Material Preview for me. I don't really seem to experience it in Workbench. Performance dips when edit mode is used in either of the aforementioned views.
Reaction is instant with Auto-depth off.

As per Bruno's request, please note I am using a 1440p monitor.
This is also FAR more noticeable on a tablet than a mouse, with middle-click mapped to one of the pen buttons. This may be essential, since I imagine testers may be using a mouse.

My specs:
Nvidia GTX 1080
Intel i7 6700
16GB RAM
Dell UP2516D monitor running at 1440p
Wacom Intuos Pro Medium

This sounds more like issue in #77509. If it's not, please make new report if you require special hardware

> In #63026#961529, @WickedInsignia wrote: > Please re-open. Still experiencing issue in 2.83. > An extra half-a-second before a middle click will register to rotate the view. This happens with meshes of ANY size, regardless of sculpting or not, and most predominantly in EEVEE and Material Preview for me. I don't really seem to experience it in Workbench. Performance dips when edit mode is used in either of the aforementioned views. > Reaction is instant with Auto-depth off. > > As per Bruno's request, please note I am using a 1440p monitor. > **This is also FAR more noticeable on a tablet than a mouse, with middle-click mapped to one of the pen buttons.** This may be essential, since I imagine testers may be using a mouse. > > My specs: > Nvidia GTX 1080 > Intel i7 6700 > 16GB RAM > Dell UP2516D monitor running at 1440p > Wacom Intuos Pro Medium This sounds more like issue in #77509. If it's not, please make new report if you require special hardware

The symptoms are different between the two cases. In that case, the whole performance is dropped. In our case, there is a significant delay between the click and the viewport rotating that isn't present with Auto Depth turned off, with performance being otherwise unaffected.
The delay is also definitely present with a mouse, although less noticeable due to the precise nature and response of a drawing tablet.
Regardless, this issue is not resolved and needs to be reopened.

It should also be mentioned that a drawing tablet is not a laptop trackpad. The task you listed concerns trackpads exclusively.

I would be happy to open another task for a hardware-specific bug, although this hardly seems required when it isn't tablet-specific.
If developers deem my case different enough to that of the OPs to open another task, I would be happy to do that.

The symptoms are different between the two cases. In that case, the whole performance is dropped. In our case, there is a significant delay between the click and the viewport rotating that isn't present with Auto Depth turned off, with performance being otherwise unaffected. **The delay is also definitely present with a mouse**, although less noticeable due to the precise nature and response of a drawing tablet. Regardless, this issue is not resolved and needs to be reopened. It should also be mentioned that a drawing tablet ***is not*** a laptop trackpad. The task you listed concerns trackpads *exclusively*. I would be happy to open another task for a hardware-specific bug, although this hardly seems required when it isn't tablet-specific. If developers deem my case different enough to that of the OPs to open another task, I would be happy to do that.

@WickedInsignia Do you experience lag only in some cases, like high poly count or even with default cube?

@WickedInsignia Do you experience lag only in some cases, like high poly count or even with default cube?

The initial lag does not seem to increase with higher poly counts, or scenes with more objects of a high density after some quick testing.
It is only apparent in the Render and Material Preview viewmodes, not in Solid or Wireframe.

I should also note there are noticeable lag spikes with Auto-Depth turned on while rotating/panning/zooming. The initial lag however is the most noticeable and most relevant to this case.

The initial lag does not seem to increase with higher poly counts, or scenes with more objects of a high density after some quick testing. It is only apparent in the Render and Material Preview viewmodes, not in Solid or Wireframe. I should also note there are noticeable lag spikes with Auto-Depth turned on while rotating/panning/zooming. The initial lag however is the most noticeable and most relevant to this case.

I have checked on 4K display as have been suggested, and I have been able to create delay with very dense model, but rotating with auto depth was still faster than zooming in/out.
So far I see Nvidia GPU as common denominator here.

@WickedInsignia before I reopen, can you check if this happens when you click on File > Defaults > Load Factory Settings and turn auto depth on afterwards?

I have checked on 4K display as have been suggested, and I have been able to create delay with very dense model, but rotating with auto depth was still faster than zooming in/out. So far I see Nvidia GPU as common denominator here. @WickedInsignia before I reopen, can you check if this happens when you click on File > Defaults > Load Factory Settings and turn auto depth on afterwards?

Yes, I can confirm it still occurs after loading factory defaults, and solely the Auto Depth option to "on".
It should be noted this issue is apparent on both my 1440p and 1080p monitors.

Yes, I can confirm it still occurs after loading factory defaults, and solely the Auto Depth option to "on". It should be noted this issue is apparent on both my 1440p and 1080p monitors.

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

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

Since there is no record of any developer confirming this, I am setting to "Needs developer to reproduce".

Since there is no record of any developer confirming this, I am setting to "Needs developer to reproduce".

Auto_Depth_Lag_Test_File.blend
I have attached a scene that is showing up the issue very clearly. Although it is still present in a default scene, a little more mesh data seems to make it more present.
Rotate the scene in Solid view, then switch into Material Preview or Render and rotate the scene again. There will be a noticeable lag at the start of each camera movement using either mouse or Wacom graphics tablet.
This is apparent on my hardware as of 2.83.1
"Orbit around selection", "Auto Depth" and "Auto Perspective" are on.

Would be interested to see if anyone can recreate the issue.

[Auto_Depth_Lag_Test_File.blend](https://archive.blender.org/developer/F8651087/Auto_Depth_Lag_Test_File.blend) I have attached a scene that is showing up the issue very clearly. Although it is still present in a default scene, a little more mesh data seems to make it more present. Rotate the scene in Solid view, then switch into Material Preview or Render and rotate the scene again. There will be a noticeable lag at the start of each camera movement using either mouse or Wacom graphics tablet. This is apparent on my hardware as of 2.83.1 "Orbit around selection", "Auto Depth" and "Auto Perspective" are on. Would be interested to see if anyone can recreate the issue.

Added subscriber: @ThomasRadeke

Added subscriber: @ThomasRadeke

I am experiencing viewport lag, too, that seems to be connected to having Auto Depth enabled and using a 4K screen.
When using the mouse wheel to zoom, it is noticably laggier than when Auto Depth is disabled but there is no lag when using ctrl+MMB to zoom - probably because the wheel is making many small zoom requests which trigger a depth query each time, as opposed to ctrl+MMB zooming, which only queries once.
I first started noticing this when updating from 2.83.1 to .2 and I noticed it on Windows 7, 10 and several versions of Linux Mint and three different computers.

I am experiencing viewport lag, too, that seems to be connected to having Auto Depth enabled and using a 4K screen. When using the mouse wheel to zoom, it is noticably laggier than when Auto Depth is disabled but there is no lag when using ctrl+MMB to zoom - probably because the wheel is making many small zoom requests which trigger a depth query each time, as opposed to ctrl+MMB zooming, which only queries once. I first started noticing this when updating from 2.83.1 to .2 and I noticed it on Windows 7, 10 and several versions of Linux Mint and three different computers.

Added subscriber: @ckohl_art

Added subscriber: @ckohl_art

This comment was removed by @Brunomendesgussoni

*This comment was removed by @Brunomendesgussoni*

Don't know where your comment went @Brunomendesgussoni but you're correct.
Lag is heavily reduced in October 2nd build of 2.91, in both Rendered and Material Preview.
It does indeed seem to be around a 75%+ reduction. Still noticing the tiniest hitch in very fast flicky movements on a tablet, but there is a negligible difference between performance of all viewports now.

Great work team!! Really appreciate this issue getting some love!

Don't know where your comment went @Brunomendesgussoni but you're correct. Lag is heavily reduced in October 2nd build of 2.91, in both Rendered and Material Preview. It does indeed seem to be around a 75%+ reduction. Still noticing the tiniest hitch in very fast flicky movements on a tablet, but there is a negligible difference between performance of all viewports now. Great work team!! Really appreciate this issue getting some love!

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Since I can't reproduce this, Is this still an issue? can you compare this to behavior on machines that did not have this bug?

Or does anybody have reason why this report should not be closed?

Since I can't reproduce this, Is this still an issue? can you compare this to behavior on machines that did not have this bug? Or does anybody have reason why this report should not be closed?

Added subscriber: @jenkm

Added subscriber: @jenkm

I guess this can be merged with #68206.

It depends very much on the size of the viewport. So, at highDPI it's four times slower. It in the Material Preview, but not in Solid. I don't know how it works but it seems strange to calculate the depth of the entire viewport in full resolution for operations such as viewport rotating. I think this can be significantly optimized.

Also when you use the middle mouse button it is not so noticeable because there is a physical click and pause before you start moving the mouse. With the tablet (or trackpad on Mac) this is more noticeable.

I guess this can be merged with #68206. It depends very much on the size of the viewport. So, at highDPI it's four times slower. It in the Material Preview, but not in Solid. I don't know how it works but it seems strange to calculate the depth of the entire viewport in full resolution for operations such as viewport rotating. I think this can be significantly optimized. Also when you use the middle mouse button it is not so noticeable because there is a physical click and pause before you start moving the mouse. With the tablet (or trackpad on Mac) this is more noticeable.

in the Material Preview, but not in Solid.

For me, the lag is noticeable in Solid mode, too. It used to be lightning-fast a few versions ago, but now zooming feels laggy.
Maybe I should note that all of my affected computers have 4K screens and nVidia cards (happens on a 1070 and a 2080 Super).

Richard, if you don't have a 4K screen, you might be able to reproduce this by setting a 4K virtual resolution.

> in the Material Preview, but not in Solid. For me, the lag is noticeable in Solid mode, too. It used to be lightning-fast a few versions ago, but now zooming feels laggy. Maybe I should note that all of my affected computers have 4K screens and nVidia cards (happens on a 1070 and a 2080 Super). Richard, if you don't have a 4K screen, you might be able to reproduce this by setting a 4K virtual resolution.

Yes I think this is the same issue. I am also not sure if there is room for improvement there is, so I will probably just merge these reports and let others decide whether this could be closed.

Yes I think this is the same issue. I am also not sure if there is room for improvement there is, so I will probably just merge these reports and let others decide whether this could be closed.

Closed as duplicate of #68206

Closed as duplicate of #68206
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
14 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#63026
No description provided.