EEVEE: Incorrect rendering when render size smaller than reflection probe size #117444

Open
opened 2024-01-23 12:56:10 +01:00 by Jeroen Bakker · 1 comment
Member

System Information
Operating system: Linux-6.5.0-14-generic-x86_64-with-glibc2.35 64 Bits, X11 UI
Graphics card: AMD Radeon PRO W7500 (gfx1102, LLVM 16.0.6, DRM 3.54, 6.5.0-14-generic) AMD 4.6 (Core Profile) Mesa 23.2.0-devel

Blender Version
Broken: version: 4.1.0 Alpha, branch: main (modified), commit date: 2024-01-23 10:12, hash: cd756143cf7a
Worked: (newest version of Blender that worked as expected)

Short description of error
When rendering an image in EEVEE-Next, where the resolution of the image is smaller than the reflection probe size, the image will contain render artifacts.

Exact steps for others to reproduce the error

  • Set render engine to EEVEE-Next
  • Add sphere reflection probe
  • set render resolution to 256*256
  • set probe resolution to 512*512
  • render image.

The cause is that the HizBuffer is initialized based on the render extent, but a different size could be used when render probes are updated. It was assumed that the render extent was always bigger then the spherical probes.

I see similar artifacts on Metal and Vulkan. The actual artifacts can differ per scene.

I have created an issue as there are multiple ways how to handle this situation and we should first discuss the correct solution.

See the attached files for an example file, the correct and incorrect rendering and a renderdoc screenshot showing the incorrect hiz buffer.

**System Information** Operating system: Linux-6.5.0-14-generic-x86_64-with-glibc2.35 64 Bits, X11 UI Graphics card: AMD Radeon PRO W7500 (gfx1102, LLVM 16.0.6, DRM 3.54, 6.5.0-14-generic) AMD 4.6 (Core Profile) Mesa 23.2.0-devel **Blender Version** Broken: version: 4.1.0 Alpha, branch: main (modified), commit date: 2024-01-23 10:12, hash: `cd756143cf7a` Worked: (newest version of Blender that worked as expected) **Short description of error** When rendering an image in EEVEE-Next, where the resolution of the image is smaller than the reflection probe size, the image will contain render artifacts. **Exact steps for others to reproduce the error** * Set render engine to EEVEE-Next * Add sphere reflection probe * set render resolution to 256*256 * set probe resolution to 512*512 * render image. The cause is that the HizBuffer is initialized based on the render extent, but a different size could be used when render probes are updated. It was assumed that the render extent was always bigger then the spherical probes. I see similar artifacts on Metal and Vulkan. The actual artifacts can differ per scene. I have created an issue as there are multiple ways how to handle this situation and we should first discuss the correct solution. See the attached files for an example file, the correct and incorrect rendering and a renderdoc screenshot showing the incorrect hiz buffer.
Jeroen Bakker added this to the 4.1 milestone 2024-01-23 12:56:10 +01:00
Jeroen Bakker added the
Type
Bug
Module
EEVEE & Viewport
Status
Confirmed
Priority
Normal
labels 2024-01-23 12:56:11 +01:00
Jeroen Bakker added this to the EEVEE & Viewport project 2024-01-23 12:56:13 +01:00
Miguel Pozo added the
Interest
EEVEE
label 2024-01-23 16:10:02 +01:00
Jeroen Bakker self-assigned this 2024-01-25 09:13:17 +01:00
Jeroen Bakker modified the milestone from 4.1 to 4.2 LTS 2024-01-25 09:13:28 +01:00
Author
Member

#117502 fixes the allocation error, but the render artifacts are still there.

In the eval lights shader the light_shadowing is incorrect for pixels in a certain range.
@fclem I looked at the lighting and shadowing code but got stuck to what is actually happening and where the issue originates from

This issue can also be simulated in the viewport by resizing the viewport to a small size.

#117502 fixes the allocation error, but the render artifacts are still there. In the eval lights shader the light_shadowing is incorrect for pixels in a certain range. @fclem I looked at the lighting and shadowing code but got stuck to what is actually happening and where the issue originates from This issue can also be simulated in the viewport by resizing the viewport to a small size.
Jeroen Bakker removed their assignment 2024-01-25 12:29:02 +01:00
Sign in to join this conversation.
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 Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#117444
No description provided.