Cycles renders artifacts on CPU but not on GPU #50164

New Issue

Kai Kostack · 2016-12-03T10:32:49+01:00

Kai Kostack commented

2016-12-03 10:32:49 +01:00

During a project I noticed this strange shading effect which I wasn't able to "fix" by just tweaking settings. What's interesting about this is that it only occurs for CPU rendering and not for GPU (usually I would expect it the other way around).

Just load the blend file and render it with CPU and GPU to see the effect.

cycles-cpu-artifacts.blend

Tested with the official Blender build on Windows 7 64.

During a project I noticed this strange shading effect which I wasn't able to "fix" by just tweaking settings. What's interesting about this is that it only occurs for CPU rendering and not for GPU (usually I would expect it the other way around). ![cycles-cpu-artifacts.jpg](https://archive.blender.org/developer/F413543/cycles-cpu-artifacts.jpg) Just load the blend file and render it with CPU and GPU to see the effect. [cycles-cpu-artifacts.blend](https://archive.blender.org/developer/F413542/cycles-cpu-artifacts.blend) Tested with the official Blender build on Windows 7 64.

Kai Kostack commented

2016-12-03 10:32:49 +01:00

Changed status to: 'Open'

Kai Kostack commented

2016-12-03 10:32:49 +01:00

Added subscriber: @KaiKostack-3

blender-admin commented

2016-12-03 10:32:49 +01:00

#50452 was marked as duplicate of this issue

Lukas Stockner commented

2016-12-04 15:38:36 +01:00

Added subscriber: @LukasStockner

Lukas Stockner commented

2016-12-04 15:38:36 +01:00

I can't reproduce that on my local Linux build (a2ebc5), but it wouldn't be the first issue that only happens on one OS.

When you say "the official build", do you mean 2.78a or the latest buildbot?

I can't reproduce that on my local Linux build (a2ebc5), but it wouldn't be the first issue that only happens on one OS. When you say "the official build", do you mean 2.78a or the latest buildbot?

Kai Kostack commented

2016-12-04 16:03:38 +01:00

It can be reproduced with the official 2.78a release and todays buildbot version for Win64.

Scorpion81 has tested it on his Linux system as well and it appeared there too, afaik.

It can be reproduced with the official 2.78a release and todays buildbot version for Win64. Scorpion81 has tested it on his Linux system as well and it appeared there too, afaik.

Martin Felke commented

2016-12-04 16:23:18 +01:00

Added subscriber: @scorpion81

Martin Felke commented

2016-12-04 16:23:18 +01:00

Yes, I have been testing with CPU rendering on FM builds since 2.72.2, since 2.73 the FM builds are based on release builds, and for me this bug happened in every version since 2.73. It does not happen if you render on GPU, or if you disable "Cast Shadows" on the sun lamp (but then you have the same result as in 2.72.2 where no shadow was visible at all)
I use linux mint 17.3 btw, and a I7 2600 CPU, and a GTX 580.

Yes, I have been testing with CPU rendering on FM builds since 2.72.2, since 2.73 the FM builds are based on release builds, and for me this bug happened in every version since 2.73. It does not happen if you render on GPU, or if you disable "Cast Shadows" on the sun lamp (but then you have the same result as in 2.72.2 where no shadow was visible at all) I use linux mint 17.3 btw, and a I7 2600 CPU, and a GTX 580.

Sergey Sharybin commented

2016-12-09 14:23:32 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2016-12-09 14:23:32 +01:00

Does the issue happen if you apply Subsurf modifier with Simple subdivisions? What's your exact CPU?

Kai Kostack commented

2016-12-09 15:05:11 +01:00

1 subdivision:

2 subdivisions:

3 subdivisions:

Tested and confirmed on:
Intel® Core™ i7-980X Processor Extreme Edition
Intel® Core™ i7-3632QM Processor

1 subdivision: ![cycles-cpu-artifacts_subdiv1.jpg](https://archive.blender.org/developer/F416071/cycles-cpu-artifacts_subdiv1.jpg) 2 subdivisions: ![cycles-cpu-artifacts_subdiv2.jpg](https://archive.blender.org/developer/F416073/cycles-cpu-artifacts_subdiv2.jpg) 3 subdivisions: ![cycles-cpu-artifacts_subdiv3.jpg](https://archive.blender.org/developer/F416075/cycles-cpu-artifacts_subdiv3.jpg) Tested and confirmed on: Intel® Core™ i7-980X Processor Extreme Edition Intel® Core™ i7-3632QM Processor

marc dion commented

2016-12-11 02:03:22 +01:00

Added subscriber: @MarcClintDion

marc dion commented

2016-12-11 02:03:22 +01:00

I do see the artifacts with GPU rendering(GTX 965m), they are just much more faint.
The artifacts disappear when I separate the two pieces into two separate objects.
The artifacts disappear when I change the Z dimension from 0.0001061 to 0.0
The artifacts disappear when I change the dimensions from (1144.902, 1030.813, 0.0001061) to (1144.902, 1030.813, 1.0), this makes it look like a precision issue since the problem goes away as the very small z-dimension approaches the others in relative scale.

For me, the artifacts begin to clear up as the the z-value for 'Dimension' approaches 0.008.

Scaling the model down in size also clears up the artifacts.

I have no idea how to fix this code-wise for Blender, I just know how to avoid the issue. ->Try not to make your models too big with respect to Blenders visible grid and try not to move too far from the origin.

For Sergey :) Here's an article from Siggraph 2012 that goes into some detail about precision problems and solutions when dealing with large scenes.

http://www.humus.name/Articles/Persson_CreatingVastGameWorlds.pdf

1) I do see the artifacts with GPU rendering(GTX 965m), they are just much more faint. 2) The artifacts disappear when I separate the two pieces into two separate objects. 3) The artifacts disappear when I change the Z dimension from 0.0001061 to 0.0 4) The artifacts disappear when I change the dimensions from (1144.902, 1030.813, 0.0001061) to (1144.902, 1030.813, 1.0), this makes it look like a precision issue since the problem goes away as the very small z-dimension approaches the others in relative scale. For me, the artifacts begin to clear up as the the z-value for 'Dimension' approaches 0.008. Scaling the model down in size also clears up the artifacts. I have no idea how to fix this code-wise for Blender, I just know how to avoid the issue. ->Try not to make your models too big with respect to Blenders visible grid and try not to move too far from the origin. For Sergey :) Here's an article from Siggraph 2012 that goes into some detail about precision problems and solutions when dealing with large scenes. http://www.humus.name/Articles/Persson_CreatingVastGameWorlds.pdf

Sergey Sharybin self-assigned this 2016-12-12 09:59:16 +01:00

Sergey Sharybin commented

2016-12-12 09:59:16 +01:00

Can reproduce the issue on AVX kernel, the issue does not happen in AVX2 kernel.

Will have a closer look later.

Can reproduce the issue on AVX kernel, the issue does not happen in AVX2 kernel. Will have a closer look later.

Sergey Sharybin commented

2017-02-27 16:32:18 +01:00

Added subscribers: @NancyHellemons, @MaiLavelle