- User Since
- Mar 27 2019, 8:04 PM (21 w, 3 d)
Thu, Aug 22
Constraints are also ignored by rigid body physics. Animations have been greatly restricted by the lack of physics capability.
May 2 2019
@Sebastian Parborg (zeddb) Material Output still supports rendering engine specific outputs.
@Sebastian Parborg (zeddb) In that case, should the displacement node be automatically added during conversion? If it's not supported, wouldn't it be better to add the displacement node only to the cycles material output and not to the eevee?
@Sebastian Parborg (zeddb) I can confirm that in the latest version, the issue remains --> hash 480a09a92f7f.
You may have been looking at the rendered version through cycles. Eevee rendered view or LookDev show an all black cube.
The teal color comes back if the added Displacement node is bypassed.
I am happy to supply any more information.
May 1 2019
Apr 29 2019
I can confirm this issue, materials work in cycles but in eevee, at certain angles, I also get these black pixels.
Apr 9 2019
I have found that this causes the Syncing memory to keep going up unbounded. On first render, memory peak is around 4000Mb, on the second it goes up to 8000Mb. This has completely killed my ability to render my scene.
Mar 30 2019
Mar 29 2019
I was able to reproduce the error with exactly the following. It only occurs when blender is running an external python script.