Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86
CPU: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Broken: version: 2.80rc2 (2.80 (sub 74), branch: master, commit date: 2019-07-18 14:52, hash: rB38d4483c6a51)
Short description of error
When rendering a mandelbulb volumetric thing on cycles using CPU and GPU, the two have very different ideas on how the scene should look like, making the individual tiles clearly visible.
(most tiles are GPU-rendered, note the stray red CPU-rendered tile to the left)
Potentially useful information
- T50193 may be the same bug; I opened a new one because that bug doesn't report differences within a single frame, and is from 2016.
- Since most of this object is endless math nodes, it may be some sort of floating-point thing that works differently on CPUs and GPUs.
- I was following this tutorial: https://www.youtube.com/watch?v=WSQFt1Nruns
- I noticed that some operations for which I expected single inputs (namely the sines) had two inputs. In the tutorial, the dude said the second input doesn't do anything, but then, that's from the alpha. Maybe taking a 0.5th sine of a value does something strange?