EEVEE-NEXT: Some Reflections missed. #119826
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#119826
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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: WIN 11
Graphics card: RTX 2060 6GO
Blender Version
Broken: Blender 4.2 Alpha
Worked: None, alpha features
Short description of error
Some reflections in eevee-next are completly missed, basicaly only the light are "Reflected"
Reference image using WEBGL Sketchfab for the reflections and is completely correct here !
Even in cycles the reflection are here even is a ray-tracing ! :
Image from eevee-next (You see in the water the mill are completely missed and missing the reflections in the water.)
Maybe a re-factoring or an another method for fixing this bad boy but here isn't good for the reflection / Refraction part.
Scene used in GLTB : https://sketchfab.com/3d-models/windmill-near-water-11523012f4424ff9acc9b9a3a7d46603
Blend file in attachement for not downloading directly from sketchfab and also ready configured for eevee-next !
Video in attachement : (Added for comment of member but present the problem btw)
@Zuorion Definitively not the same result like you for the same settings....and even compared to cycles or even sketchfab render WEBGL The reflections look not food and too blurry and not " really present"
See my videos
I think we can agree that these are not "completely missed".
Dont think you can expect Cycles quality reflections with Screen tracing, for one, there is just stuff that Eevee "does not see" -- it is screen based after all -- and there is still a bit to gain in the Raytracing / Screen tracing panels settings.
To enhance, have you considered using a Plane Reflection / Light Probe ?
I'm already use screen trace... not needed an light probe is purely useless and change nothing....
This is without
This is with
So I would argue that
is just wrong... dont you see a difference on your side?
Go looking my video in past comment you see it !
https://projects.blender.org/attachments/c3468658-34d9-41d2-a7fd-507372b2332c
Mine is really totally different !
And in my side i don't put any lightprobe because i have the screen space tracing idk why i do use light probe with screen trace ... screen trace is invented to replace "Lightprobe" why i should be use light probe WITH screen trace is purely incoherent !
So in this terms remove simply screen tracing and use light probe volume he simply make better works than screen tric if is that i'm sorry but this implementation not looking good if is the case :/
And let me teell you you're not in render mode ? You render look like preview mode is strange !
Afaict, screen tracing and plane probes can go hand in hand :
https://docs.blender.org/manual/en/4.2/render/eevee/render_settings/screen_space_reflections.html
(manual is about EEVEE, but apparently the same still holds for EEVEE next)
Yes afaict but normally if your using screen space tracing you don't need to user light probe i'm sorry but tell in what render engin you do this ?
Because in my mind nothing motor game engine or render engine ! technically is
But i never seen you do use both in same time... If you do use both in the same time simply use lightprobe again you win more time you use less compute and you get same result for less power.... SO i don't understand the logical here !
screen tracing does have limitations though (the "visibility problem") and apparently can be made faster with probes
lightprobe only also has limitations (not sure if we need to go into details)
Sketchfab has a lot of visibility "problems" as well btw., not exactly sure how they do it, but afaict, they fill in gaps with some sort of approximated stuff, so that is far from perfect either.
I think if you can get the best of both worlds, then why not use it?
To get this report a bit away from "this generally looks bad/good", I would like to see some concrete examples (with a sharable .blend file) where we clearly have a screen trace reflection missing (that is not because of the ray not being able to "see" the stuff because it is not on screen)
I vote to close this issue as it doesn't seem to fall in the categories of bugs. @dodo-2 expects that something should work, because it works in other engines. Or wants better render quality, but without any reduction of features. Those are feature requests and should be discussed in the appropriate channels.