Cycles Optix rendering slows down on second tile #75955
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#75955
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: 1x Nvidia RTX 2080 Ti
Blender Version
Broken: Blender 2.82a
Worked: every previous version
When I render on Optix sometimes (50% times) rendering goes extremely slow after rendering the first tile of render
This is happening to me only on hudge scenes like 1,44GB. And this is not happening every time but quite often ( 50% of times )
To Explain that let's just assume that we have an interior scene which has nothing special in it ( I know that optix is not working with AO shader and branched path tracing)
and expected time of rendering goes from 1 hour up to 15 hours or even 20 hours
I know that you might say that not every tile is rendering with the same speed but that is not an issue. When I restart PC or sometimes when I restart blender or sometimes when I prerender scene for something like 1 minute with material override option enabled render goes in the correct way. What I mean by that is that:
As I wrote before this happens to me only on complicated hudge scenes but my work consits only those type of scenes ( I'm interior designer)
I have this problem since the first release of blender with optix rendering. I,ve also checked tenperatures on my GPU and nothing goes above 66 degrees.
Here is my file but it is quite large 1,44 GB:
poznań restauracja zmiany evee zmiany ewa textury small.blend
For me it is hude deal if my render goes 1 hour or 15 hours so pls help me :)
Added subscriber: @sohoha
#75954 was marked as duplicate of this issue
Added subscribers: @pmoursnv, @brecht
Changed status from 'Needs Triage' to: 'Needs User Info'
Can you run
blender_debug_log.cmd
included with Blender, do the render, and attach the resulting logs here? This will include more detailed info about what Cycles is doing.Does this happen when rendering with CUDA instead of Optix?
Maybe it's running out of GPU memory somewhere and then falling back to slower CPU memory.
Rendering on cuda sometimes also crashes but this is less often than on Optix
Here is debug log:
blender_debug_output.txt
blender_system_info.txt
I've also found out that doing prerender with material override option enabled with simple principled BSDF helps 100% of times. But I have no idea what is causing that behaviour.
This is probably the issue:
In general
__texture_info
andRenderBuffers
should not be allocated in host memory because it's too slow. Instead moving more__tex_image
to the host should be preferred.Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Problem is still ongoing. I've made two render logs. One is correct with remaining render time around 1h. Second one is with crash I've described above and it's remaining time is around 150 hours. All settings are the same except for number of objets in the scene which for Right render scen is smaller. I know that you may say that crash ocurs according to number of objects in the scene however it is not that simple because Sometimes it can crash on one scene and next time it may go perfectly smoth with next render
blender right optix render.rar
blender wrong optix render.rar
Here is the scene
poznań restauracja zmiany evee zmiany ewa8 textury small temp to render3.blend
Added subscriber: @iss
Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
@sohoha I am looking at older reports, According to comments in D7426 this should be resolved already. Can you confirm this?
Added subscriber: @lichtwerk
Changed status from 'Needs User Info' to: 'Archived'
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information.