Cycles slow render start with GTX 2070 #60576
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#60576
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10
Graphics card: RTX 2070
Blender Version
Broken:
8ba86020cc
(but both 2.80 and 2.79 buildbots have the bugWorked:
Short description of error
When rendering some scenes, Cycles takes more than 2 minutes to start the first tile. It happens often on the classroom scene, some scene are not hit by the bug (like bmw and barcelona)
Exact steps for others to reproduce the error
Open the classroom scene (from https://download.blender.org/demo/test/cycles_benchmark_20160228.zip) with latest buildbots and hit F12. Most of the time, only the first render has the bug, the following ones are ok. The bug is random, so sometime it starts directly.
Added subscriber: @janb-1
Added subscriber: @brecht
I can't reproduce the problem.
regression - Cycles render very slow with latest buildbotsto Cycles slow render start with GTX 2070Added subscriber: @GavinScott
I saw something like this today (on current 2.80 build, Windows 10, Nvidia 1060 6GB)) based on the scene in this discussion about CPU+GPU tile differences:
https://blenderartists.org/t/gpu-rendering-issue-tiles-rendering-different-colours/1142774/18
The .blend in that thread, when opened in 2.80 and hitting F12, sits for 90 seconds at Rendering progress 0% with no rendering progress messages having been displayed at the top of the screen. Stdout contained:
GPUFrameBuffer: framebuffer status GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT
So I wonder if this is a timeout talking to the GPU for some reason? The same .blend starts the render pre-processing immediately in 2.79 builds ('a' and recent but not current) and does not produce the GL_ message.
I didn't test cpu rendering, it happens randomly also with GPU. I tried 10 times with CPU, it always started directly.
it says "updating shaders"
it's a new problem, it never happens on 2.79b, and I think something like november, the bug wasn't there (I remember benchmarking classroom around that time, but don't have a build anymore and it was with another GPU.)
Does it still happen with the latest builds?
Are you using a Threadripper or Ryzen CPU? We recently fixed an issue a bit like this for them.
just tested with todays build, the bug is still there when using cuda rendering and a i7 7700K.
Changed status from 'Open' to: 'Resolved'
the bug is gone since some weeks now, don't know why, but resolved.