Drop in rendering performance if result in image window set to stereo 3D #53290

Closed
opened 2017-11-10 13:42:41 +01:00 by Zsolt Stefan · 10 comments

System Information
Windows 7 Pro
NVidia Quadro P6000

Blender Version
Broken: 2.79, also more recent daily builds.

Short description of error
When rendering a stereo image (or even more when rendering a stereo panorama), and showing the results in the image editor in 3D (enable the button with the anaglyph glasses on it), Blender slows down to a crawl. CPU usage does not reach 100%, hovers around 30%. If I instead start rendering and minimize the window, then it renders fast, and uses 100% CPU. Or if I leave Blender open, and disable the 3D results view, but just display either the left or right side, then it also renders fast.

With increasing geometry and increasing resolution, the effect is more pronounced. I noticed this in a production scene that I started to render over night. When I came the next day, it had rendered for 13 hours, but still wasn't done with the first eye. Then I minimized the window, and so it finished the left eye and then did the right eye, all in about the next 1,5 hours. That means a tenfold decrease in performance!

Exact steps for others to reproduce the error
I have a simple blend file attached. It is set to a high resolution. Stereo_rendering_bug_01.blend

  • Hit render, leave window open, note the time. I get about 8 Minutes with my faster PC.
  • Then disable the 3D results view in the header of the image editor (button with the red/cyan glasses), render again. I get 2 minutes.

Setting the resolution to 50% renders faster, the difference is smaller, but still there (50% more time).

**System Information** Windows 7 Pro NVidia Quadro P6000 **Blender Version** Broken: 2.79, also more recent daily builds. **Short description of error** When rendering a stereo image (or even more when rendering a stereo panorama), and showing the results in the image editor in 3D (enable the button with the anaglyph glasses on it), Blender slows down to a crawl. CPU usage does not reach 100%, hovers around 30%. If I instead start rendering and minimize the window, then it renders fast, and uses 100% CPU. Or if I leave Blender open, and disable the 3D results view, but just display either the left or right side, then it also renders fast. With increasing geometry and increasing resolution, the effect is more pronounced. I noticed this in a production scene that I started to render over night. When I came the next day, it had rendered for 13 hours, but still wasn't done with the first eye. Then I minimized the window, and so it finished the left eye and then did the right eye, all in about the next 1,5 hours. That means a tenfold decrease in performance! **Exact steps for others to reproduce the error** I have a simple blend file attached. It is set to a high resolution. [Stereo_rendering_bug_01.blend](https://archive.blender.org/developer/F1117095/Stereo_rendering_bug_01.blend) - Hit render, leave window open, note the time. I get about 8 Minutes with my faster PC. - Then disable the 3D results view in the header of the image editor (button with the red/cyan glasses), render again. I get 2 minutes. Setting the resolution to 50% renders faster, the difference is smaller, but still there (50% more time).
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @ZsoltStefan

Added subscriber: @ZsoltStefan

Added subscriber: @brecht

Added subscriber: @brecht

Confirmed.

Workaround for now is to enable User Preferences > Images Draw Method > GLSL.

Confirmed. Workaround for now is to enable User Preferences > Images Draw Method > GLSL.

Added subscriber: @dfelinto

Added subscriber: @dfelinto

@brecht is this bug still around in 2.8? We no longer have this option (User Preferences > System > Image Draw Method) since the OpenGL migration.

@brecht is this bug still around in 2.8? We no longer have this option (User Preferences > System > Image Draw Method) since the OpenGL migration.

It's in Viewport > Textures now, which is not a great place. But I expect the same bug is still there.

The ideal solution would be to improve the image drawing to take the best of all approaches, because they all have performance issues in some cases.

It's in Viewport > Textures now, which is not a great place. But I expect the same bug is still there. The ideal solution would be to improve the image drawing to take the best of all approaches, because they all have performance issues in some cases.

Hm the issues seems even worse in 2.80 (tried with a patch to circunvent #58142). But it may be due to #60775.

Hm the issues seems even worse in 2.80 (tried with a patch to circunvent #58142). But it may be due to #60775.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Brecht Van Lommel self-assigned this 2019-05-18 13:17:28 +02:00

We now default to GLSL in most cases, so I'll consider this resolved.

We now default to GLSL in most cases, so I'll consider this 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
3 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#53290
No description provided.