Flicker Volume Artifacts in EEVEE on RTX Cards by increasing samples #77202

New Issue

HEYPictures · 2020-05-30T16:32:28+02:00

HEYPictures commented

2020-05-30 16:32:28 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits + Linux
Graphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92
It seems to be only on RTX Cards

Blender Version
Broken: version: 2.83 - 3.1 (Seems to be worse since 3.0)

Short description of error
Wierd colorful artifacts every frame in volume in rendered footage from EEVEE (Not in viewport)
Bloom makes out of this artifacts a big glowing colorfull mess.
Without bloom you can see little white artifacts random generated around in Volume (like in old Films)
if you have less Objects in your Scene. less Artifacts are their (Video 2).
When you increase the sample rate more artifacts show up. You can use a sample rate like 1000 and you have Disco.

Exact steps for others to reproduce the error
It is in every big volume scene (this isnt the only scene where these artifacts are. All of my scenes ,that have volume in it, have these artifacts (with bloom on, you can realy see the lightflashes)

Bug Report from Nvidia:
https://developer.nvidia.com/nvidia_bug/3233904

Blend file:Scene Volume Moinster.blend

Video much Stones (100 samples) : Bug wierd flikkering40000-0150.mp4

Video less Stones (100 samples) : Bug wierd flikkering50000-0150.mp4

Video less Stones (1000 samples) : Bug wierd flikkering6 1000samples0000-0150.mp4

Other Examples: S1 new Exp0800-0950.mp4
I hope you can find the Problem
Thank you for your Time to make Blender better.
Thank you very much

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits + Linux Graphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92 It seems to be only on RTX Cards **Blender Version** Broken: version: 2.83 - 3.1 (Seems to be worse since 3.0) **Short description of error** Wierd colorful artifacts every frame in volume in rendered footage from EEVEE (Not in viewport) Bloom makes out of this artifacts a big glowing colorfull mess. Without bloom you can see little white artifacts random generated around in Volume (like in old Films) if you have less Objects in your Scene. less Artifacts are their (Video 2). When you increase the sample rate more artifacts show up. You can use a sample rate like 1000 and you have Disco. **Exact steps for others to reproduce the error** It is in every big volume scene (this isnt the only scene where these artifacts are. All of my scenes ,that have volume in it, have these artifacts (with bloom on, you can realy see the lightflashes) Bug Report from Nvidia: https://developer.nvidia.com/nvidia_bug/3233904 Blend file:[Scene Volume Moinster.blend](https://archive.blender.org/developer/F8565651/Scene_Volume_Moinster.blend) **Video much Stones (100 samples) :** [Bug wierd flikkering40000-0150.mp4](https://archive.blender.org/developer/F8565664/Bug_wierd_flikkering40000-0150.mp4) **Video less Stones (100 samples) :** [Bug wierd flikkering50000-0150.mp4](https://archive.blender.org/developer/F8576181/Bug_wierd_flikkering50000-0150.mp4) **Video less Stones (1000 samples) :** [Bug wierd flikkering6 1000samples0000-0150.mp4](https://archive.blender.org/developer/F8577059/Bug_wierd_flikkering6_1000samples0000-0150.mp4) **Other Examples:** [S1 new Exp0800-0950.mp4](https://archive.blender.org/developer/F9937144/S1_new_Exp0800-0950.mp4) I hope you can find the Problem Thank you for your Time to make Blender better. **Thank you very much**

HEYPictures commented

2020-05-30 16:32:28 +02:00

Added subscriber: @Florian-10

blender-admin commented

2020-05-30 16:32:28 +02:00

#84839 was marked as duplicate of this issue

blender-admin commented

2020-05-30 16:32:28 +02:00

#84843 was marked as duplicate of this issue

blender-admin commented

2020-05-30 16:32:28 +02:00

#84775 was marked as duplicate of this issue

blender-admin commented

2020-05-30 16:32:28 +02:00

#84173 was marked as duplicate of this issue

blender-admin commented

2020-05-30 16:32:28 +02:00

#81439 was marked as duplicate of this issue

blender-admin commented

2020-05-30 16:32:28 +02:00

#81033 was marked as duplicate of this issue

blender-admin commented

2020-05-30 16:32:28 +02:00

#80015 was marked as duplicate of this issue

Alaska commented

2020-05-31 00:32:12 +02:00

Added subscriber: @Alaska

Alaska commented

2020-05-31 00:32:12 +02:00

This comment was removed by @Alaska

*This comment was removed by @Alaska*

Alaska commented

2020-05-31 00:32:25 +02:00

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

YAFU commented

2020-05-31 18:13:25 +02:00

Added subscriber: @YAFU

YAFU commented

2020-05-31 18:13:25 +02:00

Hi. I don't have the best hardware here for testing. But you may need to use Clamp values (Under Bloom and Volumetrics > Volumetric Lighting). Could you do tests with values = 10 on both and see if the problem is attenuated?

Edit:
I have tested here with the first 10 frames with default blend file shared above, and I can't reproduce the problem at least in those first 10 frames. Linux, GTX 960 4GB (440.82 driver), Blender 2.83 e5ace51295. Since the problem doesn't seem to happen on my system with default blend file, now I'm not sure if this is just a configuration problem.

Hi. I don't have the best hardware here for testing. But you may need to use Clamp values (Under Bloom and Volumetrics > Volumetric Lighting). Could you do tests with values = 10 on both and see if the problem is attenuated? Edit: I have tested here with the first 10 frames with default blend file shared above, and I can't reproduce the problem at least in those first 10 frames. Linux, GTX 960 4GB (440.82 driver), Blender 2.83 e5ace51295b9. Since the problem doesn't seem to happen on my system with default blend file, now I'm not sure if this is just a configuration problem.

HEYPictures commented

2020-05-31 18:50:00 +02:00

@YAFU yes i test it
Thank you

@YAFU yes i test it Thank you

HEYPictures commented

2020-05-31 19:22:32 +02:00

with set the Clamp Values on 10 changes nothing (maybe the dots are not so big and not so acressive ore it is random i don't know) .
yet you can see the Domain as an xray:

Bug wierd flikkering clamp values test0000-0150.mp4

But thanks aniway @YAFU

with set the Clamp Values on 10 changes nothing (maybe the dots are not so big and not so acressive ore it is random i don't know) . yet you can see the Domain as an xray: [Bug wierd flikkering clamp values test0000-0150.mp4](https://archive.blender.org/developer/F8568036/Bug_wierd_flikkering_clamp_values_test0000-0150.mp4) But thanks aniway @YAFU

YAFU commented

2020-06-01 01:01:58 +02:00

@Alaska . You said in another entry that you use POP! _OS 20.04 (Ubuntu 20.04 based distribution).

Do you have drivers installed from repositories? Are you sure that the driver version is really 440.82? I am asking that because Ubuntu package maintainers renamed packages to 440.82 so that it has more priority against nvidia from PPA packages, but it is really 440.64 driver:
https://packages.ubuntu.com/focal/nvidia-driver-440

@Florian-10 , Could you try installing the latest nvidia drivers available for Windows in nvidia official site? Edit: Mmm, apparently you have the latest Studio drivers installed. But I don't know if Game drivers would be better for Eevee.

Just trying to figure out why I can't reproduce the problem.

@Alaska . You said in another entry that you use POP! _OS 20.04 (Ubuntu 20.04 based distribution). Do you have drivers installed from repositories? Are you sure that the driver version is really 440.82? I am asking that because Ubuntu package maintainers renamed packages to 440.82 so that it has more priority against nvidia from PPA packages, but it is really 440.64 driver: https://packages.ubuntu.com/focal/nvidia-driver-440 @Florian-10 , Could you try installing the latest nvidia drivers available for Windows in nvidia official site? Edit: Mmm, apparently you have the latest Studio drivers installed. But I don't know if Game drivers would be better for Eevee. Just trying to figure out why I can't reproduce the problem.

Alaska commented

2020-06-01 01:05:43 +02:00

In #77202#942030, @YAFU wrote:
@Alaska . You said in another entry that you use POP! _OS 20.04 (Ubuntu 20.04 based distribution).

Do you have drivers installed from repositories? Are you sure that the driver version is really 440.82? I am asking that because Ubuntu package maintainers renamed packages to 440.82 so that it has more priority against nvidia from PPA packages, but it is really 440.64 driver:
https://packages.ubuntu.com/focal/nvidia-driver-440

@Florian-10 , Could you try installing the latest nvidia drivers available for Windows in nvidia official site?

Just trying to figure out why I can't reproduce the problem.

Yeah, it's Ubuntu 20.04 based and yeah, I probably do have the issue of incorrect drivers. Will retest with Windows now.

> In #77202#942030, @YAFU wrote: > @Alaska . You said in another entry that you use POP! _OS 20.04 (Ubuntu 20.04 based distribution). > > Do you have drivers installed from repositories? Are you sure that the driver version is really 440.82? I am asking that because Ubuntu package maintainers renamed packages to 440.82 so that it has more priority against nvidia from PPA packages, but it is really 440.64 driver: > https://packages.ubuntu.com/focal/nvidia-driver-440 > > @Florian-10 , Could you try installing the latest nvidia drivers available for Windows in nvidia official site? > > Just trying to figure out why I can't reproduce the problem. Yeah, it's Ubuntu 20.04 based and yeah, I probably do have the issue of incorrect drivers. Will retest with Windows now.

Alaska commented

2020-06-01 01:56:16 +02:00

Edit: Posted the wrong build information.

No issues when rendering with:
Windows-10-10.0.18362-SP0
GTX 1050Ti 445.87
Blender 2.90.0 Alpha, branch: master, commit date: 2020-05-29 18:08, hash: 2ee94c954d

I asked a friend with a RTX 2070 Super to test and they experience the artifacts. May be a RTX card issue.

Edit: Posted the wrong build information. No issues when rendering with: Windows-10-10.0.18362-SP0 GTX 1050Ti 445.87 Blender 2.90.0 Alpha, branch: master, commit date: 2020-05-29 18:08, hash: `2ee94c954d` I asked a friend with a RTX 2070 Super to test and they experience the artifacts. May be a RTX card issue.

HEYPictures commented

2020-06-01 09:28:34 +02:00

@YAFU I actually already have the studio drivers from the NVIDIA website.

I don't know much about Driver. But i have they from the NVIDIA Website.
Are they ok?
{F8569337, size=full}

@YAFU I actually already have the studio drivers from the NVIDIA website. I don't know much about Driver. But i have they from the NVIDIA Website. Are they ok? {[F8569337](https://archive.blender.org/developer/F8569337/Geforce-Driver.png), size=full}

YAFU commented

2020-06-01 13:31:40 +02:00

Yes, you have the latest Studio drivers. Let's just wait until some developer has time to take a look at this problem and decide what is going on here.

HEYPictures commented

2020-06-01 16:45:10 +02:00

OK Thanks for your help @YAFU and @Alaska

HEYPictures changed title from ~~Flicker Volume Artifacts in EEVEE~~ to Flicker Volume Artifacts in EEVEE on RTX Cards

2020-06-04 11:37:03 +02:00

HEYPictures changed title from ~~Flicker Volume Artifacts in EEVEE on RTX Cards~~ to Flicker Volume Artifacts in EEVEE on RTX Cards by increasing samples

2020-06-04 18:27:22 +02:00

HEYPictures commented

2020-06-04 18:29:11 +02:00

I found some thinks out:
So if you take the numbers of Objects in the Scene higher, the Artefacts are more and more acressive
And if you take the Sample rate also higher The Artefacts are also more.

I found some thinks out: So if you take the numbers of Objects in the Scene higher, the Artefacts are more and more acressive And if you take the Sample rate also higher The Artefacts are also more.

Clément Foucault commented

2020-07-01 00:55:51 +02:00

Added subscriber: @fclem

Clément Foucault commented

2020-07-01 00:55:51 +02:00

Seems to be a Nvidia driver bug caused by the volume integration shader.

HEYPictures commented

2020-07-02 17:20:17 +02:00

what should i do?

Alaska commented

2020-07-03 09:50:01 +02:00

In #77202#971615, @Florian-10 wrote:
what should i do?

Seems like the only option is to wait. Things point to the issue coming from the Nvidia driver which means either you will have to wait until a work around is developed in Blender or a fix is made by Nvidia. I'm not a developer, so I can't tell you which one will occur first, or even if the Blender development tell will try and tackle the issue.

> In #77202#971615, @Florian-10 wrote: > what should i do? Seems like the only option is to wait. Things point to the issue coming from the Nvidia driver which means either you will have to wait until a work around is developed in Blender or a fix is made by Nvidia. I'm not a developer, so I can't tell you which one will occur first, or even if the Blender development tell will try and tackle the issue.

HEYPictures commented

2020-07-03 10:08:51 +02:00

ok thanks

Germano Cavalcante commented

2020-08-24 17:51:34 +02:00

Added subscribers: @scuinox, @MarcinTwarowski, @mano-wii

Evan Wilson commented

2020-09-21 21:24:35 +02:00

Added subscriber: @Massimo_Conci

Massimo commented

2020-09-24 02:34:57 +02:00

As a tempory work around for anyone experiancing this. Render your video out to frames, then find the frames with the artifacts and re-render just those frames. Then use eithor blenders internal NLE or 3rd party like Premier Pro or Davinchi Resolve to combine into a video.

If you are re-rendering individual frames and are experiancing the artifact still, try adjusting the clamping very slightly under render properties>bloom, this will move went the artifacts are occuring and should be able to get a clean rendered frame out for you.

As a tempory work around for anyone experiancing this. Render your video out to frames, then find the frames with the artifacts and re-render just those frames. Then use eithor blenders internal NLE or 3rd party like Premier Pro or Davinchi Resolve to combine into a video. If you are re-rendering individual frames and are experiancing the artifact still, try adjusting the clamping very slightly under render properties>bloom, this will move went the artifacts are occuring and should be able to get a clean rendered frame out for you. ```

Evan Wilson commented

2020-10-04 20:37:45 +02:00

Added subscriber: @Arken

Germano Cavalcante commented

2020-12-31 17:48:30 +01:00

Added subscriber: @Macilvoy

YAFU commented

2021-01-16 14:17:04 +01:00

Just out of curiosity, has anyone reported this to nvidia?

Apparently it is a Windows problem only.

Just out of curiosity, has anyone reported this to nvidia? Apparently it is a Windows problem only.

Robert Guetzkow commented

2021-01-18 13:40:45 +01:00

Added subscriber: @lucutes

Robert Guetzkow commented

2021-01-19 11:40:31 +01:00

Added subscriber: @rockittt

Robert Guetzkow commented

2021-01-19 11:47:43 +01:00

Added subscriber: @Mediah

YAFU commented

2021-01-19 13:08:03 +01:00

For any Windows user who wants to report this old problem to nvidia, you will see the two options below in the link:

https://nvidia.custhelp.com/app/answers/detail/a_id/4512/kw/report

You share this blender report with nvidia developers.

For any Windows user who wants to report this old problem to nvidia, you will see the two options below in the link: https://nvidia.custhelp.com/app/answers/detail/a_id/4512/kw/report You share this blender report with nvidia developers.

HEYPictures commented

2021-01-19 14:24:18 +01:00

I made a bug report by Nvidia I hope i does it right
https://developer.nvidia.com/nvidia_bug/3233904

I made a bug report by Nvidia I hope i does it right https://developer.nvidia.com/nvidia_bug/3233904

Christophe Leyder commented

2021-04-17 09:42:34 +02:00

Added subscriber: @shotalot

Christophe Leyder commented

2021-04-17 09:42:34 +02:00

In #77202#1094766, @YAFU wrote:
Just out of curiosity, has anyone reported this to nvidia?

Apparently it is a Windows problem only.

I am getting this on linux too.

> In #77202#1094766, @YAFU wrote: > Just out of curiosity, has anyone reported this to nvidia? > > Apparently it is a Windows problem only. I am getting this on linux too.

YAFU commented

2021-04-17 12:15:07 +02:00

@shotalot , Does that mean that you can reproduce the problem with the .blend file on the first post of the report? What is your graphics card?

@Florian-10 , Any news about the report to nvidia? It seems like a private report, I don't have access.

@shotalot , Does that mean that you can reproduce the problem with the .blend file on the first post of the report? What is your graphics card? @Florian-10 , Any news about the report to nvidia? It seems like a private report, I don't have access.

HEYPictures commented

2021-04-17 17:48:15 +02:00

@YAFU I have absolutely not an Idea if i done the Report right. And the only reaction from Nvidia was yesterday. They have asked if it is still a Problem.

jw commented

2021-04-18 12:12:02 +02:00

Added subscriber: @jens-2

jw commented

2021-04-18 12:12:02 +02:00

Hi, I've tried to reproduce this today with

Windows 10 w/ latest NVIDIA studio drivers (462.31-desktop-win10-64bit-international-nsd-dch-whql.exe)
Blender 2.92.0
RTX 3090

I see no artifacts in any of the 150 frames (bloom enabled, 256 volumetrics).
I also tried the oldest readily downloadable versions of Blender (2.83.12) and nvidia drivers (game-ready flavour this time, 456.55-desktop-win10-64bit-international-whql.exe), and I don't get any artifacts with that combination either.
If this still happens for you, can you please specify which versions you're using nowadays and confirm that updating doesn't fix it?

Hi, I've tried to reproduce this today with * Windows 10 w/ latest NVIDIA studio drivers (462.31-desktop-win10-64bit-international-nsd-dch-whql.exe) * Blender 2.92.0 * RTX 3090 I see no artifacts in any of the 150 frames (bloom enabled, 256 volumetrics). I also tried the oldest readily downloadable versions of Blender (2.83.12) and nvidia drivers (game-ready flavour this time, 456.55-desktop-win10-64bit-international-whql.exe), and I don't get any artifacts with that combination either. If this still happens for you, can you please specify which versions you're using nowadays and confirm that updating doesn't fix it?

Massimo commented

2021-04-19 02:39:25 +02:00

In #77202#1148170, @jens-2 wrote:
Hi, I've tried to reproduce this today with

Windows 10 w/ latest NVIDIA studio drivers (462.31-desktop-win10-64bit-international-nsd-dch-whql.exe)

Blender 2.92.0

RTX 3090

I see no artifacts in any of the 150 frames (bloom enabled, 256 volumetrics).
I also tried the oldest readily downloadable versions of Blender (2.83.12) and nvidia drivers (game-ready flavour this time, 456.55-desktop-win10-64bit-international-whql.exe), and I don't get any artifacts with that combination either.
If this still happens for you, can you please specify which versions you're using nowadays and confirm that updating doesn't fix it?

I will re-run my old render tonight with latest drivers and report back.

> In #77202#1148170, @jens-2 wrote: > Hi, I've tried to reproduce this today with > * Windows 10 w/ latest NVIDIA studio drivers (462.31-desktop-win10-64bit-international-nsd-dch-whql.exe) > * Blender 2.92.0 > * RTX 3090 > > I see no artifacts in any of the 150 frames (bloom enabled, 256 volumetrics). > I also tried the oldest readily downloadable versions of Blender (2.83.12) and nvidia drivers (game-ready flavour this time, 456.55-desktop-win10-64bit-international-whql.exe), and I don't get any artifacts with that combination either. > If this still happens for you, can you please specify which versions you're using nowadays and confirm that updating doesn't fix it? I will re-run my old render tonight with latest drivers and report back.

HEYPictures commented

2021-04-19 09:27:03 +02:00

@jens-2 Its definitely still there. If rendered the scene ones more and its even worse.

jw commented

2021-04-19 17:54:07 +02:00

In #77202#1148463, @Florian-10 wrote:
@jens-2 Its definitely still there. If rendered the scene ones more and its even worse.

Which versions of the nv driver and blender are you using? Surely not still the ones from the original report? I see this - one thing that irritates me is I cannot increase either the volumetrics samples or the shadows samples counts beyond these values (far from 1000), were those clamped in later Blender versions or am I looking at the wrong thing? Also, those artifacts are almost certainly NaNs, and clamping might prevent them from showing here. I see that clamping in the bloom and the vol lighting settings is turned off, but maybe there are more instances of clamping in the GUI? I'm using the .blend file from this report, though.

> In #77202#1148463, @Florian-10 wrote: > @jens-2 Its definitely still there. If rendered the scene ones more and its even worse. Which versions of the nv driver and blender are you using? Surely not still the ones from the original report? I see this ![image.png](https://archive.blender.org/developer/F9992291/image.png) - one thing that irritates me is I cannot increase either the volumetrics samples or the shadows samples counts beyond these values (far from 1000), were those clamped in later Blender versions or am I looking at the wrong thing? Also, those artifacts are almost certainly NaNs, and clamping might prevent them from showing here. I see that clamping in the bloom and the vol lighting settings is turned off, but maybe there are more instances of clamping in the GUI? I'm using the .blend file from this report, though.

HEYPictures commented

2021-04-19 20:19:02 +02:00

@jens-2 I mean the Rendersamples over 1000 than you have a better Chance to see Artifacts (not in every frame) try with a Sequenze with 15 frames. Than you should see.

YAFU commented

2021-04-20 14:00:05 +02:00

@Florian-10 , Did you try the version of the nvidia driver @jens-2 are using or an even newer version?
You write here the versions of the driver that you are testing and with which you still reproduce the problem.

@Florian-10 , Did you try the version of the nvidia driver @jens-2 are using or an even newer version? You write here the versions of the driver that you are testing and with which you still reproduce the problem.

HEYPictures commented

2021-04-20 18:37:10 +02:00

Im not shure what Number my drivers are exactly but i have installed from 2 Days the newest so it should be the newest driver

Lars commented

2021-07-25 02:33:35 +02:00

Added subscriber: @mvipe

Lars commented

2021-07-25 02:33:35 +02:00

hey i have the same issue with eevee on nvidia studio drivers. started today after i installed the latest studio drivers from nvidia. very annoying. its definately a nvidia driver issue, since it literally wasnt there 10 minutes ago.

Lars commented

2021-07-25 12:15:13 +02:00

hello, for me installing the latestgame ready drivers (471.41 - WHQL), instead of the studio drivers solved the issue for now.
older studio drivers also produced the same problem for me here.

also on windows 10, rtx 2080 super, blender 2.93.1 eevee, amd ryzen 3950x

hello, for me installing the latestgame ready drivers (471.41 - WHQL), instead of the studio drivers solved the issue for now. older studio drivers also produced the same problem for me here. also on windows 10, rtx 2080 super, blender 2.93.1 eevee, amd ryzen 3950x

Fischer commented

2021-08-28 02:54:18 +02:00

Added subscriber: @Shiki-1

Fischer commented

2021-08-28 02:54:18 +02:00

Same problem happened on Studio driver 471.11, RTX2080super, Blender2.93LTS, Ryzen5950x.

Moooo commented

2021-09-11 20:31:51 +02:00

Added subscriber: @Cowbless

Moooo commented

2021-09-11 20:31:51 +02:00

It seems that I've run into the same problem. Tried the drivers @mvipe mentioned, as well as latest 471.96 (both game ready and studio). It didn't make a difference for my RTX 2060 (Win10 x64).
Here's my stack exchange question - I tried a lot of stuff. https://blender.stackexchange.com/questions/237837/flashes-of-light-escaping-through-solid-objects-in-rendered-animation
I really hope this will be fixed. I've ran into this during my first month in blender, I'm making a really cool project, and I'd hate to spend additional time picking out faulty frames from a 6 min music visualizer video by hand.

Just to be clear - it's not volumetric lighting (checking the box), it's not ambient occlusion, it's not even screenspace reflections.
I have found the culprit!
A vanilla project with nothing but a couple of lights, a screen and a camera still does this, if you put thetile size of volumetrics to 2px - just checked it.

Setting the volumetrics>tile size back to 8px eliminates this issue. I guess that's a fair tradeoff, but I'd love to see it fixed.

It seems that I've run into the same problem. Tried the drivers @mvipe mentioned, as well as latest 471.96 (both game ready and studio). It didn't make a difference for my RTX 2060 (Win10 x64). Here's my stack exchange question - I tried a lot of stuff. https://blender.stackexchange.com/questions/237837/flashes-of-light-escaping-through-solid-objects-in-rendered-animation I really hope this will be fixed. I've ran into this during my first month in blender, I'm making a really cool project, and I'd hate to spend additional time picking out faulty frames from a 6 min music visualizer video by hand. Just to be clear - it's not volumetric lighting (checking the box), it's not ambient occlusion, it's not even screenspace reflections. I have found the culprit! A vanilla project with nothing but a couple of lights, a screen and a camera still does this, if you put the**tile size** of volumetrics to 2px - just checked it. Setting the volumetrics>tile size back to 8px eliminates this issue. I guess that's a fair tradeoff, but I'd love to see it fixed.

Lars commented

2021-09-16 09:50:00 +02:00

Actually, the issue did persist even with the latest drivers game ready or studio from Nvidia. I couldnt resolve it in the end :( i jsut got lucky with some short renders that didnt have the flickers..

The weird thing is that i didnt have this issue until very recently when i manually i updated some Nvidida drivers (didnt update for quite a while before), so i assume there must be an old version that doesnt produce the issue, but i couldnt find it again so far.
anyone coudl find a Nvidida drivers version that savely gets rid of the issue? cause this might be the only fix..
So annoying now i cant really render any of my projects anymore, as they all use volumetrics always.

Blender please let us know how to fix this, Blender once again became unusable, but i want to keep loving it :(

Actually, the issue did persist even with the latest drivers game ready or studio from Nvidia. I couldnt resolve it in the end :( i jsut got lucky with some short renders that didnt have the flickers.. The weird thing is that i didnt have this issue until very recently when i manually i updated some Nvidida drivers (didnt update for quite a while before), so i assume there must be an old version that doesnt produce the issue, but i couldnt find it again so far. anyone coudl find a Nvidida drivers version that savely gets rid of the issue? cause this might be the only fix.. So annoying now i cant really render any of my projects anymore, as they all use volumetrics always. Blender please let us know how to fix this, Blender once again became unusable, but i want to keep loving it :(

Moooo commented

2021-09-16 10:24:38 +02:00

@mvipe did you try to set the tile size bigger? Did it help?

Lars commented

2021-09-16 12:37:08 +02:00

yes and no, it did help kinda to set pixelsize of volumes in eevee to 8px, but honestly it produces to low res renders even with samples of volumes set to 64 so it is not really an option,
also it doesent eliminate the issue completely it still happens just less

i guess i will haveto take a day and go through all old nvidia drivers to see which one worked..

yes and no, it did help kinda to set pixelsize of volumes in eevee to 8px, but honestly it produces to low res renders even with samples of volumes set to 64 so it is not really an option, also it doesent eliminate the issue completely it still happens just less i guess i will haveto take a day and go through all old nvidia drivers to see which one worked..

Alaska commented

2021-09-16 12:39:16 +02:00

In #77202#1220692, @mvipe wrote:
Blender please let us know how to fix this.

This is appears to be a issue with the Nvidia GPU drivers on some Nvidia GPUs. The best fix would be for Nvidia to release a driver with a fix.
Other than that, the graphics code for volumes could be changed in EEVEE to avoid going down a code patch that causes issues for this combination of GPUs and drivers. And that very well could happen soon. But I believe it is more likely that this fix of "using a different code path for volumes" will come from EEVEE's switch to the Vulkan graphics API, something that is planned for the future. Some information on this can be found here: https://code.blender.org/2021/06/eevees-future/

> In #77202#1220692, @mvipe wrote: > Blender please let us know how to fix this. This is appears to be a issue with the Nvidia GPU drivers on some Nvidia GPUs. The best fix would be for Nvidia to release a driver with a fix. Other than that, the graphics code for volumes could be changed in EEVEE to avoid going down a code patch that causes issues for this combination of GPUs and drivers. And that very well could happen soon. But I believe it is more likely that this fix of "using a different code path for volumes" will come from EEVEE's switch to the Vulkan graphics API, something that is planned for the future. Some information on this can be found here: https://code.blender.org/2021/06/eevees-future/

captain2D commented

2021-10-27 18:10:29 +02:00

Added subscriber: @captain2D

captain2D commented

2021-10-27 18:10:29 +02:00

Hi,

I have some observations regarding this issue related to Blender v2.92 and Blender v2.93.5.

On a same RTX GPU and with same Nvidia driver when I render portion of the scene with Blender 2.92 and Blende 2.93.5 (Windows 10) I get different renderings
Blender 2.92

Blende 2.93.5

The changes which look related are in the blender shader code https://github.com/blender/blender/blob/master/intern/opencolorio/gpu_shader_display_transform.glsl

  /* Convert to display space. */
  col = OCIO_to_display(col);

  /* Blend with overlay in UI colorspace.
   *
   * UI colorspace here refers to the display linear color space,
   * i.e: The linear color space w.r.t. display chromaticity and radiometry.
   * We separate the colormanagement process into two steps to be able to
   * merge UI using alpha blending in the correct color space. */
  if (overlay) {
    col.rgb = pow(col.rgb, vec3(exponent * 2.2));
    col = clamp(col, 0.0, 1.0);
    col *= 1.0 - col_overlay.a;
    col += col_overlay; /* Assumed unassociated alpha. */
    col.rgb = pow(col.rgb, vec3(1.0 / 2.2));
  }
  else {
    col.rgb = pow(col.rgb, vec3(exponent));
  }

  if (dither > 0.0) {
    col = apply_dither(col, noise_uv);
  }

  return col;

@Florian-10 Could you please check the issue with Blender 2.93.5 and update if this difference in rendering is happening at your end too.

Thanks !

Hi, I have some observations regarding this issue related to Blender v2.92 and Blender v2.93.5. On a same RTX GPU and with same Nvidia driver when I render portion of the scene with Blender 2.92 and Blende 2.93.5 (Windows 10) I get different renderings Blender 2.92 ![blender_2.92.png](https://archive.blender.org/developer/F11547489/blender_2.92.png) Blende 2.93.5 ![blender_2.93.5.png](https://archive.blender.org/developer/F11547488/blender_2.93.5.png) The changes which look related are in the blender shader code https://github.com/blender/blender/blob/master/intern/opencolorio/gpu_shader_display_transform.glsl ``` /* Convert to display space. */ col = OCIO_to_display(col); /* Blend with overlay in UI colorspace. * * UI colorspace here refers to the display linear color space, * i.e: The linear color space w.r.t. display chromaticity and radiometry. * We separate the colormanagement process into two steps to be able to * merge UI using alpha blending in the correct color space. */ if (overlay) { col.rgb = pow(col.rgb, vec3(exponent * 2.2)); col = clamp(col, 0.0, 1.0); col *= 1.0 - col_overlay.a; col += col_overlay; /* Assumed unassociated alpha. */ col.rgb = pow(col.rgb, vec3(1.0 / 2.2)); } else { col.rgb = pow(col.rgb, vec3(exponent)); } if (dither > 0.0) { col = apply_dither(col, noise_uv); } return col; ``` @Florian-10 Could you please check the issue with Blender 2.93.5 and update if this difference in rendering is happening at your end too. Thanks !

Mark Sutton commented

2021-11-17 11:29:10 +01:00

Added subscriber: @MarkSutton

LanaMclaughlin commented

2021-12-14 08:08:58 +01:00

Added subscriber: @LanaMclaughlin

LanaMclaughlin commented

2021-12-14 08:08:58 +01:00

Hi all,

I have a problem with my new RTX 2080: I have a constant artifact/blinking on a big part of my screen, like this:

The fact is that it occurs ONLY with the DisplayPorts (I tested the 3, same result) but not on HDMI one. I tested the DP cable with my previous PC (GTX 970) with the same monitor (1440p, 60Hz) and it worked fine.

Further, these artifacts/blinking seems only to happen with the DP when the vertical resolution is >1080p... in 1920x1080 it works.

Did you already faced this problem? I fear that my GPU is defective...

Thank you for your Roblox Music codes !

Hi all, I have a problem with my new RTX 2080: I have a constant artifact/blinking on a big part of my screen, like this: The fact is that it occurs ONLY with the DisplayPorts (I tested the 3, same result) but not on HDMI one. I tested the DP cable with my previous PC (GTX 970) with the same monitor (1440p, 60Hz) and it worked fine. Further, these artifacts/blinking seems only to happen with the DP when the vertical resolution is >1080p... in 1920x1080 it works. Did you already faced this problem? I fear that my GPU is defective... Thank you for your [Roblox Music codes ](https://robloxmusiccodes.net/)!

HEYPictures commented

2021-12-27 13:07:19 +01:00

Don't worry @LanaMclaughlin this is a bug and it is not related to your graphics card. Sadly is that the devs from blender or invidia are not addressing this for years which makes Eevee unusable with volumes. The only thing we can all hope for is the rewrite of Eevee in blender 3.2+ which has a chance to be better.

Samuel Nkrumah commented

2022-01-02 23:31:11 +01:00

Added subscriber: @sammynater

Samuel Nkrumah commented

2022-01-02 23:31:11 +01:00

sun absorpsion _10010-0130.mp4 yep got the same thing here however ever since I switched to 3.0 the problem has gotten worse and when I render other volumes the problem doesn't occor.

[ sun absorpsion _10010-0130.mp4](https://archive.blender.org/developer/F12785745/_sun_absorpsion__10010-0130.mp4) yep got the same thing here however ever since I switched to 3.0 the problem has gotten worse and when I render other volumes the problem doesn't occor.

lucus commented

2022-01-27 15:41:35 +01:00

few years in and they still haven't fixed this crap...

RedMser commented

2022-03-31 20:53:18 +02:00

Added subscriber: @RedMser

Matthew Gafford commented

2022-05-10 19:12:14 +02:00

Added subscriber: @AFoxInSpace

sentharn commented

2023-01-18 07:39:49 +01:00

Added subscriber: @sentharn

sentharn commented

2023-01-18 07:39:49 +01:00

I can confirm this is still reproducible using the sample file in the above bug report, on the following system, with a recent Game Ready driver. (Yes, it's a bit out of date, but more recent than the one in the report.) This is not a new bug report. Just a confirmation that the issue still exists with the same sample file.

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: 55485cb379

I had to set the samples to 1000 and the output resolution to 4k and I ended up with 2 artifact frames out of roughly 30, each with a single bright speck. This was done on a dual monitor setup with the primary (display port) monitor running at 4k 60Hz and the secondary (HDMI) monitor running at 1080p.

I haven't been able to get the card to artifact by only setting the samples to 1000.

I am testing some more scenarios overnight:

Intel Arc A770 with latest beta drivers (4034) at both 1080p (no luck) and 4k (running) output resolution, at 1080p desktop resolution, on a separate machine
RTX 3080 with desktop resolution at 1080p and output resolution set to 4k

Edit: 4k desktop resolution is not necessary, only output resolution is important. 4k + 1000 samples will pretty reliably cause at least one artifact within the first 20-40 frames.

Edit 2: Re-rendering the same frame usually results in a clean frame. Re-rendering the sequence also results in that particular frame being clean.

I can confirm this is still reproducible using the sample file in the above bug report, on the following system, with a recent Game Ready driver. (Yes, it's a bit out of date, but more recent than the one in the report.) **This is not a new bug report.** Just a confirmation that the issue still exists with the same sample file. **System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25 **Blender Version** Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: `55485cb379` I had to set the samples to 1000 and the output resolution to 4k and I ended up with 2 artifact frames out of roughly 30, each with a single bright speck. This was done on a dual monitor setup with the primary (display port) monitor running at 4k 60Hz and the secondary (HDMI) monitor running at 1080p. I haven't been able to get the card to artifact by only setting the samples to 1000. I am testing some more scenarios overnight: 1. Intel Arc A770 with latest beta drivers (4034) at both 1080p (no luck) and 4k (running) output resolution, at 1080p desktop resolution, on a separate machine 2. RTX 3080 with desktop resolution at 1080p and output resolution set to 4k Edit: 4k desktop resolution is not necessary, only output resolution is important. 4k + 1000 samples will pretty reliably cause at least one artifact within the first 20-40 frames. Edit 2: Re-rendering the same frame usually results in a clean frame. Re-rendering the sequence also results in that particular frame being clean.

Philipp Oeser removed the

Interest

EEVEE & Viewport

label 2023-02-09 15:14:55 +01:00

Sign in to join this conversation.