EEVEE: Depth Of Field produce glitches on high resolution renders #72489
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
EEVEE & Viewport
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
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#72489
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: AMD Radeon VII ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61
Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash:
f1aa4d18d4Worked: (optional)
Short description of error
Hi,
EEVEE gives glitched results when I render 2160P, however, If I turn depth of field off, glitches generally disappears. I have not experienced this on 1080P resolutions. A someone from Blenderartists I talked with also confirmed this issue.
I suppose this is not a vram capacity related issue because I even tested it on my old laptop with Geforce 650M and it rendered just fine.
Besides, I realised that after using vram with EEVEE, it doesn't go back to lower level, almost stays same and it looks that amount of vram is still in use while on idle according to AMD software. I am using Radeon Adrenaline 2020 to monitor GPU usage. I hope there is a easy fix for this.
Exact steps for others to reproduce the error
I am sending you the rendered image and the .blend file. You can find the glitch on the upper left corner. Please, have a look.
Thank you in advance.
Best wishes,
glitch.blend
Added subscriber: @egementncr
Added subscriber: @Lattapotta
That glitch doesn't happen with my Nvidia Geforce 1080 at least. Cannot confirm/disproof Vram leak.
(Sometimes rendering with the "Render Viewport Image" yields different results and fixes some glitches for me at least. :D Try it, if you are in a hurry.)
Added subscriber: @Jeroen-Bakker
It seems that viewport render doesn't have these glitches. (even with the same sample count). I will do more research on it.
Yes, viewport seems ok. I just turned depth of field off totally for now to continue rendering :)
Can you please also confirm that whether vram usage decrease after rendering on EEVEE with nvidia or not? I am not sure if this is a monitoring software issue.
One more problem I am having: With the same scene and almost same amount of vram, EEVEE causes lag much more than Cycles GPU on my screen. Is this how it is supposed to be ?
Added subscriber: @bigbad
I'm on windows 10 home. AMD r390x 8GB. 24GB ram. i7 5820k 4GHZ. Everything latest drivers.
Did a render animation. It seems when the blur of the dof increases the artifacts increases.
https://www.youtube.com/watch?v=ATdRcpskTzM
bug0001-7200.mkv
Added subscriber: @YAFU
Apparently for some reason this report is not visible to those visitors not logged in to the site.
Edit:
I am thinking, perhaps an intentional decision of the author because the shared scene.
This bug is still present on AMD GPUs in the new version of Blender 2.82. It's kinda render breaking as most animation today needs to be 4k and with DoF. Especially since AMD Cycles has gotten so slow it is not worth using it at all, one needs to go with Eevee because of the speed. Is there any hint why this is happening at all with AMD cards? Is it the OpenGL? Doing post process DoF works in compositing and then there are no bugs. It's just slower and harder to control.
glitches appear on EEVEEto EEVEE: Depth Of Field produce glitches on high resolution rendersAdded subscriber: @fclem
Changed status from 'Confirmed' to: 'Resolved'
This is fixed by the new DOF implementation.