Page MenuHome

Holes in hair particles - rendering issue
Closed, DuplicatePublic

Description

System Information
Operating system: Windows 10
Graphics card: NVIDIA RTX 2080 super

Blender Version
Broken: 2.92.0
Worked: also tried with 2.93

Short description of error
Holes in hair when rendering image or animation. Not in the viewport

Exact steps for others to reproduce the error
create a mesh and parent it to an armature. Weight paint a section of it. Add hair particles (1500) with interpolated children (100) and assign the density to the vertex group. Set clump to 0.7. Add hair dynamics and collision to mesh. If I start render I see these holes appear. Every frame they change number, shape and position on the hair and sometimes don't appear on the first frame of the animation. See images below.

Test File:

Event Timeline

Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Needs Information from User.Apr 19 2021, 2:23 PM

Mind sharing an example .blend file where this happens?

If I delete all animation keyframes and the armature those holes don't show up in the final render.

It must be a problem seen only in Cycles because I rendered using the workbench and could not reproduce it.

Btw, the scenario described is too time consuming for us to track down, we require the bug reporter to narrow down the problem.
Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.

Yes, the problem exists only rendering with cycles. I'm sure it is related to the animation, hair dynamics and children (simple and interpolated).

Philipp Oeser (lichtwerk) changed the task status from Needs Information from User to Needs Triage.May 21 2021, 1:58 PM
Omar Emara (OmarSquircleArt) changed the task status from Needs Triage to Needs Information from User.Feb 24 2022, 11:37 AM

Does the issue happen even with motion blur off? We have had similar reports related to motion blur and hair.
And does it only happen with GPU rendering or does it also happen when doing CPU rendering?

I'll consider this to be the same problem as T95305, as it apparently only occurs with Cycles and GPU.
So I'll merge the reports