Unexpected black frames or frame regions when using holodut materials #48943

Closed
opened 2016-07-25 12:01:52 +02:00 by Tobiasz Karoń · 9 comments

I'm working on a typographic animation where I use a lot of objects with holdout shader to mask out different parts of the scene when they shouldn't be visible.

When I render the animation, some parts of it produce black frames, or contain black rectangular shapes that I didn't intend to appear. The blackouts are consistent between the renders.
I tried moving verticies of the holdout objects, flipping normals - chaning the BVH setting of the scene - that didn't help. Sometimes rotating the holdout objects slightly makes the blackouts go away, sometimes adding a Solidify modifier helps, but I wasn't able to get rid of all of the artifacts.

For example frame 224 of the animation renders like this:

music.png

But in the viewport Cycles preview it looks as expected:

screen music.png

There is a plane with a holdout material present there, that's used to hide one part of the "MUSIC" text. The black shape in the final render is somehow dependant on that plane - this might be a good trace to find out what causes th, ese artifacts.

Here's the blend file: S&MfG cleaned up.blend

Here's some renders of the animation to inspect the problem:

https://youtu.be/D3GcyVX1YaA - normal animation render
https://youtu.be/fn8_xHDG8ns - with wireframe overlay
https://youtu.be/ErL30EzYh7s - with wireframe slowed down 4 times

You can see how the last part of the videos are completely messed up - the cartoonish explosion scene is completely messed up with the blackout frames.

I'm working on a typographic animation where I use a lot of objects with holdout shader to mask out different parts of the scene when they shouldn't be visible. When I render the animation, some parts of it produce black frames, or contain black rectangular shapes that I didn't intend to appear. The blackouts are consistent between the renders. I tried moving verticies of the holdout objects, flipping normals - chaning the BVH setting of the scene - that didn't help. Sometimes rotating the holdout objects slightly makes the blackouts go away, sometimes adding a Solidify modifier helps, but I wasn't able to get rid of all of the artifacts. For example frame 224 of the animation renders like this: ![music.png](https://archive.blender.org/developer/F328274/music.png) But in the viewport Cycles preview it looks as expected: ![screen music.png](https://archive.blender.org/developer/F328276/screen_music.png) There is a plane with a holdout material present there, that's used to hide one part of the "MUSIC" text. The black shape in the final render is somehow dependant on that plane - this might be a good trace to find out what causes th, ese artifacts. Here's the blend file: [S&MfG cleaned up.blend](https://archive.blender.org/developer/F328269/S_MfG_cleaned_up.blend) Here's some renders of the animation to inspect the problem: https://youtu.be/D3GcyVX1YaA - normal animation render https://youtu.be/fn8_xHDG8ns - with wireframe overlay https://youtu.be/ErL30EzYh7s - with wireframe slowed down 4 times You can see how the last part of the videos are completely messed up - the cartoonish explosion scene is completely messed up with the blackout frames.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @TobiaszunfaKaron

Added subscriber: @TobiaszunfaKaron
Tobiasz Karoń changed title from Some frames of the animation are blacked out to Some frames of the animation are blacked out when using holdout objects in the scene 2016-07-25 13:05:33 +02:00
Tobiasz Karoń changed title from Some frames of the animation are blacked out when using holdout objects in the scene to Random black frames or frame regions when using holodut materials 2016-07-25 13:08:20 +02:00
Tobiasz Karoń changed title from Random black frames or frame regions when using holodut materials to Unexpected black frames or frame regions when using holodut materials 2016-07-25 13:08:57 +02:00

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

We cannot accept this form of bug report. We need all the infos, that we ask you for, in here. Please edit your post and provide all the information.

We cannot accept this form of bug report. We need all the infos, that we ask you for, in here. Please edit your post and provide all the information.
Author

In #48943#383238, @ThomasDinges wrote:
We cannot accept this form of bug report. We need all the infos, that we ask you for, in here. Please edit your post and provide all the information.

Thanks fro the notice. I've written a report, let me know if you need more information.

> In #48943#383238, @ThomasDinges wrote: > We cannot accept this form of bug report. We need all the infos, that we ask you for, in here. Please edit your post and provide all the information. Thanks fro the notice. I've written a report, let me know if you need more information.

When rendering frame 224 the background is transparent during render and then gets black in the background, which is due to Compositing though. Not sure what the issue is exactly?

When rendering frame 224 the background is transparent during render and then gets black in the background, which is due to Compositing though. Not sure what the issue is exactly?

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Brecht Van Lommel self-assigned this 2016-07-27 00:42:46 +02:00

I can reproduce the bug in the 2.77 release but not anymore in a recent build from:
https://builder.blender.org/download/

The issue seems similar to e.g. #48538 which was confirmed to be fixed in recent builds. So I'm going to assume this is already resolved unless you find the problem is still there in a recent builds.

I can reproduce the bug in the 2.77 release but not anymore in a recent build from: https://builder.blender.org/download/ The issue seems similar to e.g. #48538 which was confirmed to be fixed in recent builds. So I'm going to assume this is already resolved unless you find the problem is still there in a recent builds.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#48943
No description provided.