Page MenuHome

Blender 2.8 Eevee fails to render images correctly after hundreds of frames are rendered on modern Intel integrated graphics
Open, Waiting for Developer to ReproducePublic

Description

System Information (Not working)
Operating system: Zorin OS 15 (based on Ubuntu 18.10 Bionic)
Graphics card: Intel® HD Graphics 620 (Kaby Lake GT2)
Processor: Intel® Core™ i3-7020U CPU @ 2.30GHz × 4 (64-bit)
Memory: 8 GB

System Information (Working)
Operating system: Zorin OS 15 (based on Ubuntu 18.10 Bionic)
Graphics card: Intel® HD Graphics 3000/Intel® Sandybridge Mobile
Processor: Intel® Core™ i5-2520M CPU @ 2.50GHz × 4 (64-bit)
Memory: 8 GB

Blender Version
Blender 2.80 Release Candidate 2

Short description of error
When I render on my system it will get hundreds of frames in then it will start to export images that look as though the "transparent" option is set in the film render setting making all sky transparent. Then, objects render as entirely black and sometimes are transparent. Does this rendering as any format for me. My computer also becomes nearly unusable when this happens and I'm guessing RAM and/or CPU usage go up a ton.

Exact steps for others to reproduce the error

  1. Open provided .blend
  2. Render to desired directory
  3. Once rendering for several hundred frames (for me: frame 245-300), Blender should begin exporting black images with transparent world background

Works as expected on Intel HD Graphics 3000 (Intel® Core™ i5-2520M) with same OS and RAM

Open attached .blend file. On system with similar specs, open the provided .blend file. Set the output directory and let the system render. Wasted about an hour or so before I got here. After it happens, the system will likely begin to output images like the one described around frame 245-300. This bug also plagued older versions of 2.80 on an Intel i5 6520M (Intel HD graphics 3000) but seems to work fine now. My system was in a room with no AC so I suspect heat could've potentially played a factor.

Note: If you don't have the world texture, use this one:

What my PC outputted:

What it should look like (rendered on other PC):

Details

Type
Bug

Event Timeline

This is a serious issue and I've replicated it twice on this PC.

Germano Cavalcante (mano-wii) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Jul 22 2019, 4:43 PM

Can you simplify the steps? The steps here don't help much to identify the problem and are time consuming. There are also several other bugs on the list to pay attention to.

Good to know :)

Germano Cavalcante (mano-wii) raised the priority of this task from Needs Information from User to Waiting for Developer to Reproduce.Jul 22 2019, 8:25 PM

Oops, I got it wrong (the description that was fixed)

If anyone else with my exact specs and Linux (preferably Ubuntu 18.10) can confirm, that'd be great!

Has anyone at the Blender Foundation figured out the cause of this? It is actually a super old bug that seems to be non-existent on older Intel GPUs but present on newer ones. :-/

Haven't had the same issue on 2.80 release.