Render time going crazy! #58207
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#58207
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?
Operating system: Windows 10
Graphics card: Nvidia Geforce GTX 960
CPU: i7 860
Broken:
3ed0d5b4d4
so I've been rendering with cycles in the newest 2.8 build, and been enjoying it a lot. BUT I set my pc to render overnight and set the samples to be done rendering about 13 hours later (as it said in the REMAINING text at the top bare when rendering) then when I checked the morning after it was at like "150 hours left." I then took some time to figure out what was happening. So i stopped the render, and just started the render over again to check. after about 5 minutes it started going 2 minutes up each second
I started the render in cycles, and experimented with tile size, and set it to 32 (rendering with CPU) and the samples to about 5000. I hit render, and the time goes up 1-2 minutes per seconds. Then tried with other projects, and the same thing happened. Then blender is crashing when rendering with GPU...
The weird part is that I am able to render the whole thing in 2.7(what i also ended up with) both with cpu and gpu
Based on the default startup or an attached .blend file (as simple as possible).
Added subscriber: @mattismoel
Added subscriber: @brecht
Thanks for the report, but we need a .blend and steps to redo the issue.
The render time estimation is not exact, it is based on the tiles rendered so far. But if later tiles are slower to render, the estimated time is adjusted. If it's failing in some case we need a way to redo it.
ooops...blend file coming in a sec
marsvehicle.blend
Added subscriber: @Alaska
@mattismoel
I don't know if this will make much of a difference, but are you able to include textures in your blend file so we have identical test setups?
At the moment I'm unable to reproduce the issue reported, however I'm only 6 minutes into the render:
System Specs:
CPU: Ryzen 5 2600 (Used for rendering)
GPU: RX 570 4GB
OS: Windows 10 Home 64bit
Blender Version: Blender 2.8 beta
26d5a3625e
I'm roughly 8 hours into the render of the scene with the missing textures. I'm 48% complete and the estimation lists another ~8 hours until completion (The original prediction was ~2 hours. This has extended due to the fact that the original estimation based on the rendering of the sky, but not to the 150 hours you were reporting). I'm using the same system as before:
CPU: Ryzen 5 2600 (Used for this render)
GPU: RX 570 4GB
OS: Windows 10 Home 64bit
Blender Version: Blender 2.8 beta
26d5a3625e
I'll let this finish over night. If I face any issues I'll leave a response. If nothing occurs, then I'll conclude that the issue may be on your end.
On that topic, are you able to list what CPU you're using? You said you were using it in the render tests that experienced issues. This may be related to the recent adjustments to Threadripper scheduling and may be why I don't experience the issue on my Ryzen. It's also possible the issue is with your textures, the version of Blender used and enhancements in recent commits, or possibly something else like malware taking up system resources while Blender is in use. I'd recommend you check the malware option. To do so, follow the steps below:
@brecht
I've rendered the scene (it was missing textures so the test wasn't identical) and the total time of render was roughly 15 hours on my Ryzen 5 2600. I believe the issue may be on the users end (E.G. Other programs using the CPU, overheating and thermal throttling on the CPU, etc) but more testing would need to be done to ensure this isn't the case. I'll leave this task with you.
Changed status from 'Open' to: 'Archived'
As far as I know GPU render crashes should be fixed since this was reported.
Regarding the time estimation, it's not very smart but there is not that much we can do. In this file it starts in the center of the render where there is nothing, so based on those first tiles the estimate is for it to render much faster, then as it encounters slower tiles it adjusts the estimation.
We could try to improve this once, though it's not obviously a good idea to change the tile order just to get a better time estimation.