Page MenuHome

Cycles not rendering tail
Closed, ArchivedPublic

Description

Using : Blender-2.92.0-d4330ae70be6-macOS (Jan 10)

  1. Top two screen shots show tail in Shader and Material view while being Rendered.



  1. Strange labored render of horse's "tail" area.

Top photo: during render look at where main render is working while it still has dots around where the tail should have been. Render engine hung for 2 minutes over the tail area before proceeding normally, until it came up the right side back toward the missing tail Again engine was hung for about 30 seconds shown in the middle photo

Middle photo: hung render engine nearing missing tail. See where dots stopped at right edge.

Bottom photo: Above missing tail and render dots still calculating, look above at the numbers for Samples 81/128. All tiles have completed but each "Sample" each took 1 sec. of time to finalize the render AFTER the render looked completed. Nothing changed in the render during this extra time.

Event Timeline

Alaska (Alaska) changed the task status from Needs Triage to Needs Information from User.Jan 13 2021, 7:14 AM
Alaska (Alaska) added a subscriber: Alaska (Alaska).

On the tail you have the diameter scale of the tail set to "0" and as a result the tail is infinitely thin which means it is invisible. It can be adjusted back to a non-zero value here while the tail object is selected:

As for why EEVEE/Material preiview is showing the tail, that is because you have EEVEE set to render hair using the strand method which does not take into consideration hair width/diameter.

Above missing tail and render dots still calculating, look above at the numbers for Samples 81/128. All tiles have completed but each "Sample" each took 1 sec. of time to finalize the render AFTER the render looked completed. Nothing changed in the render during this extra time.

That is because you have activated a denoiser and it is denoising those tiles.

Robert Guetzkow (rjg) closed this task as Archived.EditedJan 13 2021, 10:08 AM

Thank you for your report. Unfortunately, it seem that the issue is caused by misconfiguration in your scene and not a bug in Blender.

If you need help learning or using Blender, please post a question on one of our community websites, for instance Blender's StackExchange, blenderartists.org or the #support channel on Blender chat. The bug tracker is only for bug reports.

In case you believe that you've found a bug, please create a new bug report through Help > Report a Bug in Blender. We expect all bug reports to follow the submission template. Please provide system information (operating system, GPU, graphics driver version), affected Blender version, previous Blender version that worked properly, a short and precise description of the issue, a description of the expected behavior, step by step instructions to reproduce it and, if relevant, a minimal .blend file that showcases the problem.