Huge difference in render time between two almost similar frames #50978

Closed
opened 2017-03-17 15:51:11 +01:00 by Viktor · 14 comments

System Information
Windows 7 and Windows 10 (both were used).
GeForce GTX 860M and GeForce GTX 1070 8GB GDDR5 SLI (both were used)

Blender Version
Broken: (2.78c or 2.77 a)

Short description of error
Huge difference in render time between two almost similar frames

Exact steps for others to reproduce the error
chalk new14(FINALWITH NOISE REMOVE).blend
Go to my Blend file which contains scene with rigid body objects that are falling on the table and later particles start to emit and explode from those objects. At frame 91 - i am not able to render on GPU ( Error "Nvidia Windows Kernel Mode driver has stopped responding") . But at frame 92 - i am able to render on GPU very fast and with no errors. There are actually many such problematic frames. Frames 91 and 92 - given as good examples.

frame 91 looks like this on my computer - Безымянный.png

P.S. There is no reason for that error to appear at frame 91 because frame 92 is almost the same. Also all drivers are up to date and a lot i did to avoid that error. For example i tried to use different versions of Blender (2.78c and 2.77a), i tried to reinstall nvidia drivers and CUDA toolkit, used different versions of nvidia drivers. Tried to reinstall Windows7. I tried it on windows 7 and windows 10. Tried to render on different laptops. I also made some advised on "Microsoft Support "changes to the registry in "TdrDelay FILE" and also changed Nvidia driver settings where i enabled "prefer maximum performance" and switched off "VSync". I even tried to simplify the scene by removing all subdivision surface modifiers on a chalk pieces and remove textures from the table. Problem persists on many frames. One of them - frame 91. As a contrast - frame 92 for example, where no problems appeared.

**System Information** Windows 7 and Windows 10 (both were used). GeForce GTX 860M and GeForce GTX 1070 8GB GDDR5 SLI (both were used) **Blender Version** Broken: (2.78c or 2.77 a) **Short description of error** Huge difference in render time between two almost similar frames **Exact steps for others to reproduce the error** [chalk new14(FINALWITH NOISE REMOVE).blend](https://archive.blender.org/developer/F512100/chalk_new14_FINALWITH_NOISE_REMOVE_.blend) Go to my Blend file which contains scene with rigid body objects that are falling on the table and later particles start to emit and explode from those objects. At frame 91 - i am not able to render on GPU ( Error "Nvidia Windows Kernel Mode driver has stopped responding") . But at frame 92 - i am able to render on GPU very fast and with no errors. There are actually many such problematic frames. Frames 91 and 92 - given as good examples. frame 91 looks like this on my computer - ![Безымянный.png](https://archive.blender.org/developer/F512115/Безымянный.png) P.S. There is no reason for that error to appear at frame 91 because frame 92 is almost the same. Also all drivers are up to date and a lot i did to avoid that error. For example i tried to use different versions of Blender (2.78c and 2.77a), i tried to reinstall nvidia drivers and CUDA toolkit, used different versions of nvidia drivers. Tried to reinstall Windows7. I tried it on windows 7 and windows 10. Tried to render on different laptops. I also made some advised on "Microsoft Support "changes to the registry in "TdrDelay FILE" and also changed Nvidia driver settings where i enabled "prefer maximum performance" and switched off "VSync". I even tried to simplify the scene by removing all subdivision surface modifiers on a chalk pieces and remove textures from the table. Problem persists on many frames. One of them - frame 91. As a contrast - frame 92 for example, where no problems appeared.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @ViktorTar

Added subscriber: @ViktorTar

Added subscriber: @YAFU

Added subscriber: @YAFU

Hi.
Whenever you see this kind of strange problems related to slowness in certain frames or frame intervals, you should see if this is related to Motion Blur enabled.
I have seen other times Motion Blur cause these kind of problems. I do not know if this is due to a bug or just it is one of those known problems that usually have Motion Blur in Blender.

Hi. Whenever you see this kind of strange problems related to slowness in certain frames or frame intervals, you should see if this is related to Motion Blur enabled. I have seen other times Motion Blur cause these kind of problems. I do not know if this is due to a bug or just it is one of those known problems that usually have Motion Blur in Blender.
Author

Hi. But the motion blur is presented on a frame 92 as well,but i can successfully render that frame, so no problems there. Thats why i reported it. Because its not normal when you have all frames look similar but render time for one frame - 10 hours, for frame next to it - 8 minutes

Hi. But the motion blur is presented on a frame 92 as well,but i can successfully render that frame, so no problems there. Thats why i reported it. Because its not normal when you have all frames look similar but render time for one frame - 10 hours, for frame next to it - 8 minutes

Yes, it is. That's what I mean when I say I've seen this kind of problem before. So let's wait for what cycles developers say about this.

Yes, it is. That's what I mean when I say I've seen this kind of problem before. So let's wait for what cycles developers say about this.
Author

If its motion blur was causing those problems then i think it would be a big issue because a lot of people using motion blur to render animations and also it means it would be a lot of such bug reports and probably it would be fixed by now. But yes, lets wait what developers will say.

If its motion blur was causing those problems then i think it would be a big issue because a lot of people using motion blur to render animations and also it means it would be a lot of such bug reports and probably it would be fixed by now. But yes, lets wait what developers will say.
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Please try with a build from builder.blender.org/download

Please try with a build from builder.blender.org/download
Author

Cannot check. This Blender built crushes all the time as soon as i opening that my file all if i very quickly open that file and press F12, it renders for a few seconds and then crushes again.

Cannot check. This Blender built crushes all the time as soon as i opening that my file all if i very quickly open that file and press F12, it renders for a few seconds and then crushes again.

Added subscriber: @fablefox

Added subscriber: @fablefox
@ViktorTar Can provide the crash log if possible? https://docs.blender.org/manual/en/dev/troubleshooting/crash.html
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Aaron Carlisle self-assigned this 2017-05-16 21:03:07 +02:00
Member

Considering the slowdown is most likely from motion blur, which has been optimized for 2.79 and I can open the blend-file without it crashing I am going to close this report.

Considering the slowdown is most likely from motion blur, which has been optimized for 2.79 and I can open the blend-file without it crashing I am going to close this report.
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
4 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#50978
No description provided.