blender/blender
162
515
Fork 780
Code Issues 6.8k Pull Requests 929 Projects 19 Wiki Activity

Eevee Next rendering Black Frames in animations (4.2.3 and other Blender Versions with Eevee Next) #129588

New Issue
Open
opened 2024-10-30 14:03:50 +01:00 by Nicole Ruiz · 16 comments
Nicole Ruiz commented 2024-10-30 14:03:50 +01:00
Copy Link

Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: AMD Radeon RX 6600 ATI Technologies Inc. 4.6.0 Core Profile Context 24.10.1.241007

Broken: version: 4.2.3 LTS, branch: blender-v4.2-release, commit date: 2024-10-14 15:20, hash: 0e22e4fcea03
Worked: 3.6.5

Description:
I have an animation in blender, but when i start rendering it, sometimes out of nowhere, black frames start to get rendered. Like i make a 400 frames animation, and 10 frames or more are just solid black, but they are not next to each other or anything, it's just random what frames get black and which ones are normal, no matter what render settings i try.
This has happened to me in all the versions of Blender with Eevee Next. It also happens if i don't use Compositor or anything like that.
i've already made sure that the camera is not clipping into anything or something like that.

Steps:
I Open the scene in blender, then i compile the shaders in the Viewport Shading Rendered option, then i hit render animation. After waiting the frames to render completely (it takes less than a second to render each frame), some of them are black.

Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: AMD Radeon RX 6600 ATI Technologies Inc. 4.6.0 Core Profile Context 24.10.1.241007 Broken: version: 4.2.3 LTS, branch: blender-v4.2-release, commit date: 2024-10-14 15:20, hash: `0e22e4fcea03` Worked: 3.6.5 Description: I have an animation in blender, but when i start rendering it, sometimes out of nowhere, black frames start to get rendered. Like i make a 400 frames animation, and 10 frames or more are just solid black, but they are not next to each other or anything, it's just random what frames get black and which ones are normal, no matter what render settings i try. This has happened to me in all the versions of Blender with Eevee Next. It also happens if i don't use Compositor or anything like that. i've already made sure that the camera is not clipping into anything or something like that. Steps: I Open the scene in blender, then i compile the shaders in the Viewport Shading Rendered option, then i hit render animation. After waiting the frames to render completely (it takes less than a second to render each frame), some of them are black.
alley frames bug.png
257 KiB
alley frames bug.png
Nicole Ruiz added the
Status
Needs Triage
Severity
Normal
Type
Bug
 labels 2024-10-30 14:03:51 +01:00
Alaska commented 2024-10-30 14:08:38 +01:00
Member
Copy Link

I Open the scene in blender

Which scene? It seems you might of forgotten to attach a file.

> I Open the scene in blender Which scene? It seems you might of forgotten to attach a file.
Alaska added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2024-10-30 14:08:52 +01:00
Nicole Ruiz commented 2024-10-30 14:21:25 +01:00
Author
Copy Link

My bad, here is the scene

The problem doesn't just happen in this scene, it usually happens in most animations i've tried to render in Eevee Next.

My bad, here is the scene The problem doesn't just happen in this scene, it usually happens in most animations i've tried to render in Eevee Next.
asian alleyway for anim 1 packed.blend
138 MiB
Alaska added
Status
Needs Triage
 and removed
Status
Needs Information from User
 labels 2024-10-30 14:24:51 +01:00
Alaska commented 2024-10-31 05:58:44 +01:00
Member
Copy Link

I tested on all my major GPUs (NVIDIA RTX 4090, AMD RX 7800XT, Intel Arc A750, Apple M1 Pro)and could not reproduce the issue.

We have had reports of addons causing issues for some people. Could you try using factory settings to see if it helps:

  • Open Blender
  • Select from the top of Blender File -> Defaults -> Load Factory Settings to temporarily load factory settings
  • Test to see if the issue is there.

System Information
Operating system: Windows-10-10.0.26100-SP0 64 Bits
Graphics card: AMD Radeon RX 7800 XT ATI Technologies Inc. 4.6.0 Core Profile Context 24.9.1.240926
Graphics card: Intel(R) Arc(TM) A750 Graphics Intel 4.6.0 - Build 32.0.101.6129
Blender version: 4.2.3 LTS, branch: blender-v4.2-release, commit date: 2024-10-14 15:20, hash: 0e22e4fcea03

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 565.90
Blender version: 4.2.3 LTS, branch: blender-v4.2-release, commit date: 2024-10-14 15:20, hash: 0e22e4fcea03

System Information
Operating system: macOS-14.6.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M1 Pro 1.2
Blender version: 4.2.3 LTS, branch: blender-v4.2-release, commit date: 2024-10-14 15:20, hash: 0e22e4fcea03

I tested on all my major GPUs (NVIDIA RTX 4090, AMD RX 7800XT, Intel Arc A750, Apple M1 Pro)and could not reproduce the issue. We have had reports of addons causing issues for some people. Could you try using factory settings to see if it helps: - Open Blender - Select from the top of Blender `File -> Defaults -> Load Factory Settings` to temporarily load factory settings - Test to see if the issue is there. **System Information** Operating system: Windows-10-10.0.26100-SP0 64 Bits Graphics card: AMD Radeon RX 7800 XT ATI Technologies Inc. 4.6.0 Core Profile Context 24.9.1.240926 Graphics card: Intel(R) Arc(TM) A750 Graphics Intel 4.6.0 - Build 32.0.101.6129 Blender version: 4.2.3 LTS, branch: blender-v4.2-release, commit date: 2024-10-14 15:20, hash: `0e22e4fcea03` **System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 565.90 Blender version: 4.2.3 LTS, branch: blender-v4.2-release, commit date: 2024-10-14 15:20, hash: `0e22e4fcea03` **System Information** Operating system: macOS-14.6.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M1 Pro 1.2 Blender version: 4.2.3 LTS, branch: blender-v4.2-release, commit date: 2024-10-14 15:20, hash: `0e22e4fcea03`
Alaska added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2024-10-31 05:59:23 +01:00
Nicole Ruiz commented 2024-10-31 09:08:19 +01:00
Author
Copy Link

I've tried this with the scene i've sent and it seems to work, but when i tried the same thing on other scene and now, while most the frames are okay, now a frame came out in a weird color (but with the compositing on it for some reason)

(Previous frame - broken frame - next frame)

Attaching ,blend file just in case

I've tried this with the scene i've sent and it seems to work, but when i tried the same thing on other scene and now, while most the frames are okay, now a frame came out in a weird color (but with the compositing on it for some reason) (Previous frame - broken frame - next frame) Attaching ,blend file just in case
imagen.png
842 KiB
asian alleyway for anim 2 packed.blend
137 MiB
alley rain test 1 door out_0058.png
2.2 MiB
alley rain test 1 door out_0056.png
2.2 MiB
alley rain test 1 door out_0057.png
1.7 MiB
Screenshot 2024-10-31 045305.png
805 KiB
imagen.png alley rain test 1 door out_0058.png alley rain test 1 door out_0056.png alley rain test 1 door out_0057.png Screenshot 2024-10-31 045305.png
Alaska commented 2024-10-31 13:43:09 +01:00
Member
Copy Link

I think it might be a compositing issue.

When I was testing with asian alleyway for anim 1 packed.blend earlier I had a weird compositing issue on one of my computers (I was trying to track down what was causing it so I could create a seperate bug report for it). And since you're using a similar/the same compositor setup in this file I think it might be related.

Does the issue occur if you turn off compositing?

I think it might be a compositing issue. When I was testing with `asian alleyway for anim 1 packed.blend` earlier I had a weird compositing issue on one of my computers (I was trying to track down what was causing it so I could create a seperate bug report for it). And since you're using a similar/the same compositor setup in this file I think it might be related. Does the issue occur if you turn off compositing?
Nicole Ruiz commented 2024-10-31 16:38:01 +01:00
Author
Copy Link

Okay, after some testing, it seems that turning off the compositing fixed the colors, i'm going to run some more tests and see if the black renders disappear also in other animations and renders.

Now that i remember, some of my compositing setups that involve glare nodes or similar node groups to get that glow effect in emission materials used to make the render output a black image in 4.1/4.2, but i don't remember how to replicate the effect, it just sort of happened out of nowhere when using GPU compositing and node groups and changing values.
And maybe that could be why some of the renders became just black images, since blender failed to calculate something in the compositing step, i think it could have something to do with glare nodes or blur nodes working inside node groups, but i could be wrong.

Okay, after some testing, it seems that turning off the compositing fixed the colors, i'm going to run some more tests and see if the black renders disappear also in other animations and renders. Now that i remember, some of my compositing setups that involve glare nodes or similar node groups to get that glow effect in emission materials used to make the render output a black image in 4.1/4.2, but i don't remember how to replicate the effect, it just sort of happened out of nowhere when using GPU compositing and node groups and changing values. And maybe that could be why some of the renders became just black images, since blender failed to calculate something in the compositing step, i think it could have something to do with glare nodes or blur nodes working inside node groups, but i could be wrong.
Nicole Ruiz commented 2024-11-01 09:30:29 +01:00
Author
Copy Link

I ran some more testing, and with a different node setup in the compositing, and for a frame, it seems to get bugged again.
Without the compositing on, it seems to render like normal.

I attach the new blend file, with the new compositing setup, and both animations with and without the compositing activated.

I ran some more testing, and with a different node setup in the compositing, and for a frame, it seems to get bugged again. Without the compositing on, it seems to render like normal. I attach the new blend file, with the new compositing setup, and both animations with and without the compositing activated.
alley rain green tint0001-0250.mp4
7.0 MiB
asian alleyway for anim 1 green.blend
137 MiB
alley rain green tint0001-0250.mp4
12 MiB
Nicole Ruiz commented 2024-11-01 13:50:10 +01:00
Author
Copy Link

After running some tests in different scenes with really simple compositing setups, it seems that it's 100% a compositing issue

I'm running tests to see if it may be caused for using GPU as the Compositing device. So instead using CPU as compositing device.

I ran the same scene, first with the GPU (it produced some black frames), then i restarted blender and opened the scene, then used the CPU as the compositing device and rendered the same animation 4 times in a row to see if any black or weird color frames came out, but all of them came out perfectly.

I used the same node setup in both, just a lens distortion and a filter soften node.

Update: The CPU compositing also seems to show the same errors, but with CPU, the frames are not solid black, they are just darker, like the exposure or brightness of the image went down

After running some tests in different scenes with really simple compositing setups, it seems that it's 100% a compositing issue I'm running tests to see if it may be caused for using GPU as the Compositing device. So instead using CPU as compositing device. I ran the same scene, first with the GPU (it produced some black frames), then i restarted blender and opened the scene, then used the CPU as the compositing device and rendered the same animation 4 times in a row to see if any black or weird color frames came out, but all of them came out perfectly. I used the same node setup in both, just a lens distortion and a filter soften node. Update: The CPU compositing also seems to show the same errors, but with CPU, the frames are not solid black, they are just darker, like the exposure or brightness of the image went down
alley rain test 1 GPU.mp4
3.2 MiB
alley rain test 4 CPU.mp4
3.2 MiB
compositor setup GPU CPU.png
196 KiB
compositor setup GPU CPU.png
Alaska commented 2024-11-02 15:12:52 +01:00
Member
Copy Link

Thank you for running all these tests. However I am still personally unable to reproduce the issue.
In the meantime can you double check with Blender 4.3 to see if it also has the issue? https://builder.blender.org/download/daily/

I will ask if others on the triaging team can reproduce the issue.

Thank you for running all these tests. However I am still personally unable to reproduce the issue. In the meantime can you double check with Blender 4.3 to see if it also has the issue? https://builder.blender.org/download/daily/ I will ask if others on the triaging team can reproduce the issue.
Alaska added
Status
Needs Triage
 and removed
Status
Needs Information from User
 labels 2024-11-02 15:13:07 +01:00
Nicole Ruiz commented 2024-11-03 15:19:11 +01:00
Author
Copy Link

I've done some testing with different scenes and compositing setups, and it seems to work with no issues in 4.3.

I tried the scenes i've sent before and also some more longer animations with the compositing setup I usually use and it seems to be working fine.

I've done some testing with different scenes and compositing setups, and it seems to work with no issues in 4.3. I tried the scenes i've sent before and also some more longer animations with the compositing setup I usually use and it seems to be working fine.
Pratik Borhade commented 2024-11-04 07:33:46 +01:00
Member
Copy Link

Hi, checking asian alleyway for anim 1 green.blend from #129588 (comment)
I don't see any difference inn CPU/GPU compositor results. But the render output is indeed different in case of "with and without compositor". Is that an issue? 🤔
Looks like we have moved from original reported issue.

Hi, checking `asian alleyway for anim 1 green.blend` from https://projects.blender.org/blender/blender/issues/129588#issuecomment-1328382 I don't see any difference inn CPU/GPU compositor results. But the render output is indeed different in case of "with and without compositor". Is that an issue? 🤔 Looks like we have moved from original reported issue.
Nicole Ruiz commented 2024-11-04 14:29:34 +01:00
Author
Copy Link

The issue was that in 4.1/4.2, when rendering animations with the compositing on, it would render black frames when the compositing was on (and sometimes even when the compositing wasn't on too). I tried to see if it was a problem with GPU compositing, so i did some tests with CPU compositing, but it was the same.

This problem happens randomly in my animations ever since i've started using eevee next for animations. In past blender versions, this problem didn't happened (and now i'm 4.3 beta to see if it solved the problem)

The issue was that in 4.1/4.2, when rendering animations with the compositing on, it would render black frames when the compositing was on (and sometimes even when the compositing wasn't on too). I tried to see if it was a problem with GPU compositing, so i did some tests with CPU compositing, but it was the same. This problem happens randomly in my animations ever since i've started using eevee next for animations. In past blender versions, this problem didn't happened (and now i'm 4.3 beta to see if it solved the problem)
Pratik Borhade commented 2024-11-05 04:38:42 +01:00
Member
Copy Link

@OmarEmaraDev hi, do you remember fixing any similar bug in 4.3 but not backported to 4.2?

@OmarEmaraDev hi, do you remember fixing any similar bug in 4.3 but not backported to 4.2?
Omar Emara commented 2024-11-05 09:15:22 +01:00
Member
Copy Link

@PratikPB2123 Not as far as I know. Are we sure that this is a GPU compositing issue? The update in this comment seems to indicate that the issue might exist in CPU as well, albeit different in behavior.

@PratikPB2123 Not as far as I know. Are we sure that this is a GPU compositing issue? The update in this [comment](https://projects.blender.org/blender/blender/issues/129588#issuecomment-1328501) seems to indicate that the issue might exist in CPU as well, albeit different in behavior.
Pratik Borhade commented 2024-11-05 10:27:51 +01:00
Member
Copy Link

Are we sure that this is a GPU compositing issue

Referring to #129588 (comment), this is an issue on both CPU?GPU compositor: I tried to see if it was a problem with GPU compositing, so i did some tests with CPU compositing, but it was the same.

> Are we sure that this is a GPU compositing issue Referring to https://projects.blender.org/blender/blender/issues/129588#issuecomment-1330421, this is an issue on both CPU?GPU compositor: `I tried to see if it was a problem with GPU compositing, so i did some tests with CPU compositing, but it was the same.`
Richard Antalik commented 2024-11-20 02:56:53 +01:00
Member
Copy Link

I wasn't able to reproduce this issue.

I wasn't able to reproduce this issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Interest
Alembic

  
Interest
Animation & Rigging

  
Interest
Asset System
Asset datablocks, libraries, browser and shelf

  
Interest
Audio

  
Interest
Automated Testing

  
Interest
Blender Asset Bundle

  
Interest
BlendFile

  
Interest
Code Documentation
Code comments, Python/RNA API descriptions

  
Interest
Collada

  
Interest
Compatibility
Backward and forward compatibility

  
Interest
Compositing

  
Interest
Core

  
Interest
Cycles

  
Interest
Dependency Graph

  
Interest
Development Management

  
Interest
EEVEE

  
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
Viewport & EEVEE

  
Interest
Virtual Reality

  
Interest
Vulkan

  
Interest
Wayland
Wayland windowing on Unix

  
Interest
Workbench

  
Interest: X11

Xorg/X11 windowing

  
Legacy
Asset Browser Project

Archived

  
Legacy
Blender 2.8 Project

Archived

  
Legacy
Milestone 1: Basic, Local Asset Browser

Archived

  
Legacy
OpenGL Error

Archived

  
Meta
Good First Issue

  
Meta
Papercut

  
Meta
Retrospective

  
Meta
Security
Related to security, see policy: https://developer.blender.org/docs/handbook/bug_reports/vulnerability_reports/

  
Module
Animation & Rigging

  
Module
Core

  
Module
Development Management

  
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

  
Module
Viewport & EEVEE

  
Platform
FreeBSD

  
Platform
Linux

  
Platform
macOS

  
Platform
Windows

  
Severity
High

  
Severity
Low

  
Severity
Normal

  
Severity
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

Archived

  
Type
Report

Archived

  
Type
To Do

No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
5 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#129588
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?