Page MenuHome

Only one strand visible when display amount of child hair particles is above a certain number
Closed, ResolvedPublic

Description

System Information
Operating system: macOS 10.14.2 Mojave
Graphics card: AMD Radeon R9 M370X 2048MB + Intel Iris Pro 1536MB

Blender Version
Broken: 2.80, 351f537fa83, 2018-12-15

Short description of error
Only one hair strand visible in OpenGL and Eevee views when using child hairs (affects both simple and interpolated) when the display amount goes above a 16 in my case. This is for strand hair shape type. However when the strand hair type is set to strip, the problem occurs when the display amount is over 8. The render amount in Eevee seems to be affected as well when I hit the render button. This does not affect Cycles rendering.

display amount set to 16
display amount set to 17

Exact steps for others to reproduce the error
In a new blend file, simply add a particle system to the default cube and set the emitter type to hair. Then scroll down to the children panel and select either simple or interpolated, and then increase the display amount until all the hairs disappear and you're left with one strand. Then try decreasing the amount until they all show up again, and then in the render settings, change the hair shape type to strip and they all disappear except one.

Event Timeline

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 30.Jan 23 2019, 5:15 PM

I can not reproduce this on my end. I've tried up to 3000 in display amount and they still didn't disappear.

Could you see if you still get this problem with the latest blender beta?

I downloaded the latest beta build today and the problem still persists. It seems the more parent particles I have as well, the less children particles it takes before they all disappear except for that one strand.

I'm guessing this is a OSX issue. Does it happen with both the intel/AMD GPU?

Can you attach the output of --debug-gpu when you reproduce this error?

Does --debug-gpu-force-workarounds solve it?

Also --debug-gpu-force-workarounds doesn't solve the issue for me.

Sebastian Parborg (zeddb) raised the priority of this task from 30 to Normal.