Crushed Velvet Eevee render problems in Cycles #75258

New Issue

Dave Wilson · 2020-04-01T01:42:34+02:00

Dave Wilson commented

2020-04-01 01:42:34 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75

Blender Version
Broken: version:

2.93.0 Alpha, branch: master, commit date: 2021-01-24 23:16, hash: cf6d17a6aa
2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: 375c7dc4ca
Worked: ?

Short description of error
The Crushed Velvet material from the Material Library does not render properly with Cycles when setting the device to GPU.

Exact steps for others to reproduce the error

Load the simplified material attached below
Set the render device to CPU and render. The output should be all black

Set the render device to GPU and render.. Depending whether you have only GPU(s) activated in the preferences or also CPU(s) you should see one of the following. When only GPU(s) are enabled you should get a proper render. When CPU(s) are also enabled you should get dark render tiles that are rendered on the CPUs.

VelvetTestSimplified2.blend

Original description:
I'm attaching the .blend file I used to test this issue. I'm not even sure this is a bug or simply me not being overly familiar with materials yet, but it feels like a bug. An dit may be a Blender bug and nothing to do with this add-on. Obviously, this material renders fine in Eevee, but it also renders fine in Cycles when using CPU to render, but has major artifacts when using GPU to render. I've attached a render to show what I'm getting in case you don't experience it.

The steps I took to get here are,

Basically, I have a default scene I use to do my modeling or as a start point. It's very basic. I was experiencing this issue in another project I was working on and noticed it went away when I changed the material on one object.

I loaded up my basic start file
selected the sphere
Scrolled down to the Material Library VX panel in the Material Properties tab
Loaded the Sample Library
Chose the Crushed Velvet Eevee material and clicked Apply to Selected

That's it. I had initially thought it was simply a problem rendering in Cycles but for my first render, I forgot to switch from CPU to GPU and noticed it rendered fine. So I did a few more tests and it renders fine with CPU every time, but not with GPU.

VelvertTest.blend

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75 **Blender Version** Broken: version: - 2.93.0 Alpha, branch: master, commit date: 2021-01-24 23:16, hash: `cf6d17a6aa` - 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: `375c7dc4ca` Worked: ? **Short description of error** The *Crushed Velvet* material from the *Material Library* does not render properly with Cycles when setting the device to *GPU*. **Exact steps for others to reproduce the error** - Load the simplified material attached below - Set the render device to *CPU* and render. The output should be all black # Set the render device to *GPU* and render.. Depending whether you have only GPU(s) activated in the preferences or also CPU(s) you should see one of the following. When only GPU(s) are enabled you should get a proper render. When CPU(s) are also enabled you should get dark render tiles that are rendered on the CPUs. [VelvetTestSimplified2.blend](https://archive.blender.org/developer/F9598498/VelvetTestSimplified2.blend) --- Original description: I'm attaching the .blend file I used to test this issue. I'm not even sure this is a bug or simply me not being overly familiar with materials yet, but it feels like a bug. An dit may be a Blender bug and nothing to do with this add-on. Obviously, this material renders fine in Eevee, but it also renders fine in Cycles when using CPU to render, but has major artifacts when using GPU to render. I've attached a render to show what I'm getting in case you don't experience it.![Velvet.png](https://archive.blender.org/developer/F8440059/Velvet.png) The steps I took to get here are, Basically, I have a default scene I use to do my modeling or as a start point. It's very basic. I was experiencing this issue in another project I was working on and noticed it went away when I changed the material on one object. - I loaded up my basic start file - selected the sphere - Scrolled down to the Material Library VX panel in the Material Properties tab - Loaded the Sample Library - Chose the Crushed Velvet Eevee material and clicked Apply to Selected That's it. I had initially thought it was simply a problem rendering in Cycles but for my first render, I forgot to switch from CPU to GPU and noticed it rendered fine. So I did a few more tests and it renders fine with CPU every time, but not with GPU. [VelvertTest.blend](https://archive.blender.org/developer/F8440058/VelvertTest.blend)

Dave Wilson commented

2020-04-01 01:42:34 +02:00

Added subscriber: @Durghan

Robert Guetzkow commented

2021-01-26 11:40:12 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2021-01-26 11:40:12 +01:00

The problem appears to be that transmission is non-zero, the IOR is zero and there is subsurface scattering. This results in a black output on CPU but not on GPU. Below is a simplified file with a simplified material where the settings of the Principled BSDF are at the default except for the Subsurface, IOR and Transmission.

VelvetTestSimplified2.blend

This is an edge case as even with an IOR slightly above zero it renders properly on both.

The problem appears to be that transmission is non-zero, the IOR is zero and there is subsurface scattering. This results in a black output on CPU but not on GPU. Below is a simplified file with a simplified material where the settings of the Principled BSDF are at the default except for the *Subsurface*, *IOR* and *Transmission*. [VelvetTestSimplified2.blend](https://archive.blender.org/developer/F9598492/VelvetTestSimplified2.blend) This is an edge case as even with an IOR slightly above zero it renders properly on both.

Robert Guetzkow commented

2021-01-26 11:41:08 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Robert Guetzkow commented

2021-01-26 11:50:47 +01:00

My edit should perhaps be a new separate report as I've noticed that the original report had the problem in reverse, works fine on CPU but not with GPU.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Crushed Velvet Eevee render problems in Cycles #75258