Graphical persistance in EEVEE #64186

New Issue

chris stagg · 2019-05-06T00:50:45+02:00

chris stagg commented

2019-05-06 00:50:45 +02:00

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: Radeon RX 560X Series ATI Technologies Inc. 4.5.13547 Core Profile Context 25.20.15031.1000

Blender Version
Broken: version: 2.80 (sub 60), branch: blender2.7, commit date: 2019-05-03 21:09, hash: ee0d8426ab

Short description of error
EEVEE has graphical persistence with attached file. hp-willow-animation.blend

Exact steps for others to reproduce the error
Open attached file, go out of camera view and change to rendered mode, rotate view and graphics persist. Other modes don't have this problem, nor does other files.

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: Radeon RX 560X Series ATI Technologies Inc. 4.5.13547 Core Profile Context 25.20.15031.1000 **Blender Version** Broken: version: 2.80 (sub 60), branch: blender2.7, commit date: 2019-05-03 21:09, hash: `ee0d8426ab` **Short description of error** EEVEE has graphical persistence with attached file. [hp-willow-animation.blend](https://archive.blender.org/developer/F7008424/hp-willow-animation.blend) **Exact steps for others to reproduce the error** Open attached file, go out of camera view and change to rendered mode, rotate view and graphics persist. Other modes don't have this problem, nor does other files.

chris stagg commented

2019-05-06 00:50:45 +02:00

Added subscriber: @tzj

chris stagg commented

2019-05-06 01:12:59 +02:00

The fishy cat example has the same problem.

Sebastian Parborg commented

2019-05-06 18:40:05 +02:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-05-06 18:40:05 +02:00

I can't reproduce on my end. Is this still an issue with the latest build?

chris stagg commented

2019-05-07 22:14:49 +02:00

Yes it still persists, but the newest build does allow me to open the koro example, where as before it crashed blender on opening.

chris stagg commented

2019-05-07 22:19:36 +02:00

This is what I get.

![error2.jpg](https://archive.blender.org/developer/F7013452/error2.jpg) This is what I get.

chris stagg commented

2019-05-07 22:34:48 +02:00

The AMD graphics drivers are up to date also.

Sebastian Parborg commented

2019-05-08 10:37:36 +02:00

Added subscriber: @Jeroen-Bakker

Sebastian Parborg commented

2019-05-08 10:37:36 +02:00

@Jeroen-Bakker can you reproduce this?

Jeroen Bakker commented

2019-05-08 10:54:49 +02:00

Yes it is reproduceable.

Issue is reproduceable in simpler scenes when having a world materials with Pricipled Volume.
Volumetric rendering does not need to be turned on to get this issue.

Did a BiSect tracked it back to

fefc9c95e4818768ba08c665111d2e405ae72672 is the first bad commit
commit fefc9c95e4818768ba08c665111d2e405ae72672
Author: Clément Foucault <foucault.clem@gmail.com>
Date:   Fri Apr 5 20:45:32 2019 +0200

    DRW: Opti: Replace bound tex/ubo tracking array by bitfields

Scene seems to render fine when the Pricipled Volume is disconnected. Other Volume shaders seem to work ok.

So will look into the pricipled volume + world combination

Will check as there was a fix related to volumetrics later on.

Yes it is reproduceable. Issue is reproduceable in simpler scenes when having a world materials with Pricipled Volume. Volumetric rendering does not need to be turned on to get this issue. Did a BiSect tracked it back to ``` fefc9c95e4818768ba08c665111d2e405ae72672 is the first bad commit commit fefc9c95e4818768ba08c665111d2e405ae72672 Author: Clément Foucault <foucault.clem@gmail.com> Date: Fri Apr 5 20:45:32 2019 +0200 DRW: Opti: Replace bound tex/ubo tracking array by bitfields ``` Scene seems to render fine when the Pricipled Volume is disconnected. Other Volume shaders seem to work ok. So will look into the pricipled volume + world combination Will check as there was a fix related to volumetrics later on.

Jeroen Bakker self-assigned this 2019-05-08 10:59:46 +02:00

Jeroen Bakker commented

2019-05-08 11:00:18 +02:00

Changed status from 'Open' to: 'Resolved'

Jeroen Bakker closed this issue

2019-05-08 11:00:18 +02:00

Jeroen Bakker commented

2019-05-08 11:02:00 +02:00

Changed status from 'Resolved' to: 'Open'

Jeroen Bakker reopened this issue

2019-05-08 11:02:00 +02:00

Jeroen Bakker removed their assignment 2019-05-08 12:10:51 +02:00

Clément Foucault was assigned by Jeroen Bakker

2019-05-08 12:10:51 +02:00

Jeroen Bakker commented

2019-05-08 12:10:51 +02:00

This goes really deep into the world volumetrics, so I assign it to you.

fefc9c95e4 introduced the issue. Seems like it was to be fixed by 8d3af588a2 but still seems to be not working for AMD Pro drivers the open source driver seemed to be working.

Do you know what might be the problem.

This goes really deep into the world volumetrics, so I assign it to you. fefc9c95e4818768ba08c665111d2e405ae72672 introduced the issue. Seems like it was to be fixed by 8d3af588a23734c59f22a6feebe2d10f1a281875 but still seems to be not working for AMD Pro drivers the open source driver seemed to be working. Do you know what might be the problem.

Brecht Van Lommel commented

2019-07-03 18:53:31 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-07-03 18:53:31 +02:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2019-07-03 18:53:31 +02:00

Brecht Van Lommel commented

2019-07-03 18:53:31 +02:00

As far as I know this was fixed in #64983 (EEVEE viewport smudging / crash with volumes).

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

Graphical persistance in EEVEE #64186