keyframed Boolean causes CUDA error #53490

New Issue

Marcin Twarowski · 2017-12-06T12:55:37+01:00

Marcin Twarowski commented

2017-12-06 12:55:37 +01:00

Win 10 and GTX1080, Win 7 and GTX970
Broken in 2.79 official and build 1802d14 (from 05.12.2017)

Open attached file. Hit F12. All should render correctly:

Now add a single keyframe in "Operation" in Boolean modifier:

To be sure you can save and restart the file, although that probably won't be neccessary. Now you can see that scrubbing the timeline has become really slow. Hit F12. On GTX1080 it either crashes to desktop (Blender stopped working) or spits this error:

CUDA launch failed in cuCtxSynchronize(), line 1372

On GTX970 it doesn't crash but renders incorrectly:

Remove the key frame, save and restart, all is back to normal.

CUDA_launch_failed.blend

Win 10 and GTX1080, Win 7 and GTX970 Broken in 2.79 official and build 1802d14 (from 05.12.2017) Open attached file. Hit F12. All should render correctly: ![CUDA_launch_failed_bug_01.jpg](https://archive.blender.org/developer/F1317789/CUDA_launch_failed_bug_01.jpg) Now add a single keyframe in "Operation" in Boolean modifier: ![CUDA_launch_failed_bug_02.jpg](https://archive.blender.org/developer/F1317855/CUDA_launch_failed_bug_02.jpg) To be sure you can save and restart the file, although that probably won't be neccessary. Now you can see that scrubbing the timeline has become really slow. Hit F12. On GTX1080 it either crashes to desktop (Blender stopped working) or spits this error: ``` CUDA launch failed in cuCtxSynchronize(), line 1372 ``` On GTX970 it doesn't crash but renders incorrectly: ![CUDA_launch_failed_gtx970.png](https://archive.blender.org/developer/F1317851/CUDA_launch_failed_gtx970.png) Remove the key frame, save and restart, all is back to normal. [CUDA_launch_failed.blend](https://archive.blender.org/developer/F1317872/CUDA_launch_failed.blend)

Marcin Twarowski commented

2017-12-06 12:55:37 +01:00

Changed status to: 'Open'

Marcin Twarowski commented

2017-12-06 12:55:37 +01:00

Added subscriber: @MarcinTwarowski

Sergey Sharybin commented

2017-12-06 17:50:40 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2017-12-06 17:50:40 +01:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2017-12-06 17:50:40 +01:00

Sergey Sharybin self-assigned this 2017-12-06 17:50:40 +01:00

Sergey Sharybin commented

2017-12-06 17:50:40 +01:00

Thanks for the report, but it seems to be more a limitation than a bug here.

The reason why playback is slow, is because even though the value of property never changes, there is no way for Blender to know that in advance, before actually evaluating the value. So what Blender sees is that there is something animated in the modifier stack, so the modifier stack gets re-evaluated.

Wrong render result on render is caused by motion blur. The issue with boolean modifier is that we can not really guarantee the order of verticies to be the same for every modifier evaluation. So what happens is that Cycles is confused by number of vertices to be the same, but order is different. This is not supported by motion blur.

Issues with CUDA is likely due to so called TDR, because the final topology gets corrupted, which makes every pixel to render really slow. See https://docs.blender.org/manual/en/dev/render/cycles/gpu_rendering.html#the-nvidia-opengl-driver-lost-connection-with-the-display-driver

Thanks for the report, but it seems to be more a limitation than a bug here. The reason why playback is slow, is because even though the value of property never changes, there is no way for Blender to know that in advance, before actually evaluating the value. So what Blender sees is that there is something animated in the modifier stack, so the modifier stack gets re-evaluated. Wrong render result on render is caused by motion blur. The issue with boolean modifier is that we can not really guarantee the order of verticies to be the same for every modifier evaluation. So what happens is that Cycles is confused by number of vertices to be the same, but order is different. This is not supported by motion blur. Issues with CUDA is likely due to so called TDR, because the final topology gets corrupted, which makes every pixel to render really slow. See https://docs.blender.org/manual/en/dev/render/cycles/gpu_rendering.html#the-nvidia-opengl-driver-lost-connection-with-the-display-driver

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

keyframed Boolean causes CUDA error #53490