Black material + render view with heavy scene + fog #76253

New Issue

Robert S · 2020-04-30T09:02:02+02:00

Robert S commented

2020-04-30 09:02:02 +02:00

System Information
Operating system: Windows 10
Graphics card: 1080 ti

Blender Version
Broken: 2.82.7
Worked: 2.82.7

Short description of error

Scene was working normally when the file was actively being put together, and renders were already made.
Scene now goes black when put into material preview or render view mode (eevee).
If the large cube covering the entire scene with fog material is deleted, it leaves behind this:

So far, I have tried:

Imported all collections into a new file (black).
Imported object per object until I got black (volume was seemingly the culprit).
Imported only the volume shader into a new file (looked fine).
Opened the original file again (everything looked fine).
Next day starting the PC, the file is once again black when openend.

Exact steps for others to reproduce the error
Seems to only happen in this very large file, and though it doesn't contain anything sensitive, it was made at work, so I can't just publicly post it. If a developer wants to look at it, please contact me in PM here or on devtalk/BA and I will send you the file.

**System Information** Operating system: Windows 10 Graphics card: 1080 ti **Blender Version** Broken: 2.82.7 Worked: 2.82.7 **Short description of error** * Scene was working normally when the file was actively being put together, and renders were already made. * Scene now goes black when put into material preview or render view mode (eevee). ![renderv.gif](https://archive.blender.org/developer/F8502391/renderv.gif) * If the large cube covering the entire scene with fog material is deleted, it leaves behind this: ![eeef8135d18608d3845dd714095eb6d44dd99b96.png](https://archive.blender.org/developer/F8502395/eeef8135d18608d3845dd714095eb6d44dd99b96.png) So far, I have tried: * Imported all collections into a new file (black). * Imported object per object until I got black (volume was seemingly the culprit). * Imported only the volume shader into a new file (looked fine). * Opened the original file again (everything looked fine). * Next day starting the PC, the file is once again black when openend. **Exact steps for others to reproduce the error** Seems to only happen in this very large file, and though it doesn't contain anything sensitive, it was made at work, so I can't just publicly post it. If a developer wants to look at it, please contact me in PM here or on devtalk/BA and I will send you the file.

Robert S commented

2020-04-30 09:02:02 +02:00

Added subscriber: @RobertS

Alaska commented

2020-04-30 09:42:12 +02:00

Added subscriber: @Alaska

Alaska commented

2020-04-30 09:42:12 +02:00

Are you able to test the file in Blender 2.83 and 2.90 to see if you can reproduce it? https://builder.blender.org/download/

You could also try updating your graphics drivers to see if that'll help. https://www.nvidia.com/Download/index.aspx

Just throwing some ideas out there.

Are you able to test the file in Blender 2.83 and 2.90 to see if you can reproduce it? https://builder.blender.org/download/ You could also try updating your graphics drivers to see if that'll help. https://www.nvidia.com/Download/index.aspx Just throwing some ideas out there.

Germano Cavalcante commented

2020-04-30 15:24:44 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-04-30 15:24:44 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Germano Cavalcante closed this issue

2020-04-30 15:24:44 +02:00

Germano Cavalcante self-assigned this 2020-04-30 15:24:44 +02:00

Germano Cavalcante commented

2020-04-30 15:24:44 +02:00

Thanks for the report. But due to the number of reported bugs, it is not worth it to spend a lot of time on reports that we cannot reproduce.
Large files are not suitable for investigating a bug, we require the bug reporter to narrow down the problem.
Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.
If there are many steps to reproduce the problem, please attach a simple .blend file saved right before the bug occurs, so only a few steps are needed to trigger the bug.

Thanks for the report. But due to the number of reported bugs, it is not worth it to spend a lot of time on reports that we cannot reproduce. Large files are not suitable for investigating a bug, we require the bug reporter to narrow down the problem. Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly. If there are many steps to reproduce the problem, please attach a simple .blend file saved right before the bug occurs, so only a few steps are needed to trigger the bug.

Robert S commented

2020-04-30 16:28:50 +02:00

So I guess this reply is futile now but I suspect the issue is the shader compilation and the sheer size of the file... the shader subsystem seems to give up before it's even started (progress bar never shows up)... which in that case would mean it's not possible to produce a simplified setting because the bug only appears in very heavy files.

Robert S commented

2020-04-30 16:42:08 +02:00

Ok, so with a bit of fiddling in 2.9, I can get the file working again... seems to not be the shader compilation, but something with the sheer size of the area and the fog volume/bloom:

This is still seems like a no-go in 2.82... tweaking the cameras and clipping planes do not seem to work there.

Seems an extremely large far clipping plane distance was saved with the file for some reason (fairly sure Blender-GIS set it... but also, fairly sure that shouldn't produce this result).

Ok, so with a bit of fiddling in 2.9, I can get the file working again... seems to not be the shader compilation, but something with the sheer size of the area and the fog volume/bloom: ![hmm.gif](https://archive.blender.org/developer/F8503291/hmm.gif) This is still seems like a no-go in 2.82... tweaking the cameras and clipping planes do not seem to work there. Seems an extremely large far clipping plane distance was saved with the file for some reason (fairly sure Blender-GIS set it... but also, fairly sure that shouldn't produce this result).

Germano Cavalcante commented

2020-04-30 16:43:04 +02:00

This can be the same issue reported on #74302

Robert S commented

2020-04-30 19:01:42 +02:00

Yes, seems very similar, if not the same!

My file opens in black & white every time as well, so if you are going to investigate the other issue, let me know if you want the file via some private channel (and which one in that case).

Yes, seems very similar, if not the same! My file opens in black & white every time as well, so if you are going to investigate the other issue, let me know if you want the file via some private channel (and which one in that case).

Germano Cavalcante commented

2020-04-30 19:32:23 +02:00

Closed as duplicate of #74302

Germano Cavalcante closed this issue

2020-04-30 19:32:23 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Black material + render view with heavy scene + fog #76253