EEVEE-Next #93220

This is a list of all the tasks planned for the future of EEVEE's codebase.
Due to a change in requirements, this rewrite is planned for after the metal backend has landed in master.

The initial release of EEVEE-Next is currently planned for the 4.0 release. Additional features will be added throughout the lifetime of the 4 series.

Main features currently implemented:

Virtual Shadowmapping: Increases shadow resolution and maximum sharpness while keeping relatively low memory footprint.
Subsurface Scattering: New algorithm that eliminate light leaking between objects and supports per pixel radius.
High Light count support: Lights are now efficiently culled and there is virtually no limits to the maximum number of lights in a scene.
Motion Blur: Now supports shutter curve.
Grease Pencil Object support: Grease pencil object are now treated as any other geometry and fully compatible with the shading pipeline.
Shading: Arbitrary number of BSDFs are now supported without major performance impact. Raytracing and SSS is no more restricted to one BSDF node.
Thickness output: This is a new output which control the thickness for translucency, refraction and volume shader.
Renderpass: All passes are rendered at once and do not need multiple geometry passes (except cryptomatte).

Motion Vector

Motion vectors support in the viewport.

Film

TAA reprojection.
Sample accumulation.
Reduced memory usage of weight buffers.

Camera

Port Depth Of Field.

Motion Blur

Shutter curve support for time steps.
Motion steps data.
- Mesh.
- Curves.

Shading

Bump Mapping support.
Shader to RGB support.
Vertex Displacement support
Single pass HiZ using compute shader.
#105868 Deferred Shading.

Light

Efficient Light culling
Arbitrary light count

Shadows

#104472 Virtual Shadow mapping
Shadow tracing

Render Passes

Render Passes
#99390 Cryptomatte

Global Illumination

#105643 Irradiance Baking
#105673 Screen Space Effects
#105649 Reflection Cubemaps

Volumetric

#105672 Volume Rendering

Milestone: Screen Space Effects minimum-viable-product for 4.0 release.

Extended target

D9792: [WIP] Eevee: Parallax Occlusion Mapping from Displacement Output
Panoramic camera support.
Depth Of Field for panoramic camera.
Grease Pencil Geometry support.

This is a list of all the tasks planned for the future of EEVEE's codebase. Due to a change in requirements, this rewrite is planned for after the metal backend has landed in master. The initial release of EEVEE-Next is currently planned for the 4.0 release. Additional features will be added throughout the lifetime of the 4 series. Main features currently implemented: - **Virtual Shadowmapping**: Increases shadow resolution and maximum sharpness while keeping relatively low memory footprint. - **Subsurface Scattering**: New algorithm that eliminate light leaking between objects and supports per pixel radius. - **High Light count support**: Lights are now efficiently culled and there is virtually no limits to the maximum number of lights in a scene. - **Motion Blur**: Now supports shutter curve. - **Grease Pencil Object support**: Grease pencil object are now treated as any other geometry and fully compatible with the shading pipeline. - **Shading**: Arbitrary number of BSDFs are now supported without major performance impact. Raytracing and SSS is no more restricted to one BSDF node. - **Thickness output**: This is a new output which control the thickness for translucency, refraction and volume shader. - **Renderpass**: All passes are rendered at once and do not need multiple geometry passes (except cryptomatte). ### Motion Vector - [x] Motion vectors support in the viewport. ### Film - [x] TAA reprojection. - [x] Sample accumulation. - [x] Reduced memory usage of weight buffers. ### Camera - [x] Port Depth Of Field. ### Motion Blur - [x] Shutter curve support for time steps. - [ ] Motion steps data. - [x] Mesh. - [ ] Curves. ### Shading - [x] Bump Mapping support. - [x] Shader to RGB support. - [x] Vertex Displacement support - [x] Single pass HiZ using compute shader. - [x] #105868 Deferred Shading. ### Light - [x] Efficient Light culling - [x] Arbitrary light count ### Shadows - [x] #104472 Virtual Shadow mapping - [ ] Shadow tracing ### Render Passes - [x] Render Passes - [x] #99390 Cryptomatte ### Global Illumination - [ ] #105643 Irradiance Baking - [ ] #105673 Screen Space Effects - [ ] #105649 Reflection Cubemaps ### Volumetric - [ ] #105672 Volume Rendering Milestone: Screen Space Effects minimum-viable-product for 4.0 release. ### Extended target - [ ] [D9792: [WIP] Eevee: Parallax Occlusion Mapping from Displacement Output](https://archive.blender.org/developer/D9792) - [ ] Panoramic camera support. - [ ] Depth Of Field for panoramic camera. - [ ] Grease Pencil Geometry support.

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

Added subscriber: @fclem

Added subscriber: @EAW

Added subscriber: @lsscpp

Added subscriber: @geocentric_wage

Added subscriber: @Rawalanche

Is this: https://developer.blender.org/T68478 really missing from the list or is it part of some other feature in the list?

I am asking because lack of almost any feature in this list is nowhere near as big of a pain point as the fact currently, when using any HDRI lighting, users have to keep two separate lighting setups for Eevee and Cycles, and also spend substantial amount of time creating Eevee HDRI light ligth based on rough calibration by the Cycles reference. Then, every time when switching between Eevee and Cycles, the user has to either swap the light rigs, or use the less physically based (with scene lights in place of HDRI hotspots) Eevee light right also with Cycles.

Furthermore, majority of users do not even posses the skill and knowledge to pull off an Eevee HDRI light rig that's at least remotely closer to correct HDRI illumination. Aside from getting the light intensities, colors and radii right, one also has to do numerous hacks with ray switching in world shader to ensure that directly visible environment is unclamped for tone mapping and bloom to work correctly, while at the same time making sure that diffuse contribution of the world shader is clamped so that the light is not doubled.

Solving this issue would significantly improve both Eevee workflow as well as image quality produced by users to average skill level, since diffuse illumination from HDRIs would not longer be extremely incorrect.

Unless the Ray Tracing section of this list includes diffuse illumination from the world shader with HDRI texture support, then even if every single feature on this list would be completed, most users would still produce images of significantly degraded quality unless they posses the quite advanced knowledge to work around it described above.

Is this: https://developer.blender.org/T68478 really missing from the list or is it part of some other feature in the list? I am asking because lack of almost any feature in this list is nowhere near as big of a pain point as the fact currently, when using any HDRI lighting, users have to keep two separate lighting setups for Eevee and Cycles, and also spend substantial amount of time creating Eevee HDRI light ligth based on rough calibration by the Cycles reference. Then, every time when switching between Eevee and Cycles, the user has to either swap the light rigs, or use the less physically based (with scene lights in place of HDRI hotspots) Eevee light right also with Cycles. Furthermore, majority of users do not even posses the skill and knowledge to pull off an Eevee HDRI light rig that's at least remotely closer to correct HDRI illumination. Aside from getting the light intensities, colors and radii right, one also has to do numerous hacks with ray switching in world shader to ensure that directly visible environment is unclamped for tone mapping and bloom to work correctly, while at the same time making sure that diffuse contribution of the world shader is clamped so that the light is not doubled. Solving this issue would significantly improve both Eevee workflow as well as image quality produced by users to average skill level, since diffuse illumination from HDRIs would not longer be extremely incorrect. Unless the Ray Tracing section of this list includes diffuse illumination from the world shader with HDRI texture support, then even if every single feature on this list would be completed, most users would still produce images of significantly degraded quality unless they posses the quite advanced knowledge to work around it described above.

@Rawalanche I will add it to the list of features that may be tackled after the rewrite. I would not consider it a blocker since it is a new feature and is not fundamentally a missing part of the pipeline.

The Raytracing changes does improve this use case but still introduce too much noise. So I think sun light extraction is still a needed feature.

@Rawalanche I will add it to the list of features that may be tackled after the rewrite. I would not consider it a blocker since it is a new feature and is not fundamentally a missing part of the pipeline. The Raytracing changes does improve this use case but still introduce too much noise. So I think sun light extraction is still a needed feature.

Added subscriber: @TheRedWaxPolice

Added subscriber: @PhlixFer

Added subscriber: @JohnCox-3

Added subscriber: @AlexeyAdamitsky

Added subscriber: @Jaydead

Added subscriber: @dabuxian

Added subscriber: @sbchild

Added subscriber: @s12a

Added subscriber: @SergeyHerr

Added subscriber: @mavek

Added subscriber: @Baga-4

Added subscriber: @dodo-2

Added subscriber: @ThomasToo

This comment was removed by @ThomasToo

*This comment was removed by @ThomasToo*

Added subscriber: @Jeroen-Bakker

Added subscriber: @AndyCuccaro

Added subscriber: @AD_Blend-69420

Added subscriber: @ThomasDinges

Added subscriber: @JacobMerrill-1

Added subscriber: @frogstomp-4

Added subscriber: @RedMser

Added subscriber: @Caden-Mitchell

This comment was removed by @JacobMerrill-1

*This comment was removed by @JacobMerrill-1*

Added subscriber: @Eary

This comment was removed by @JacobMerrill-1

*This comment was removed by @JacobMerrill-1*

Moderation note This is not the proper place for user feedback or feature requests. Please check this for appropriate places: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

**Moderation note** This is not the proper place for user feedback or feature requests. Please check this for appropriate places: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

Added subscriber: @Low_Polygon42

Added subscriber: @GeorgiaPacific

Added subscriber: @Blendork

Added subscriber: @browneggz

Added subscriber: @2905710881

This comment was removed by @2905710881

*This comment was removed by @2905710881*

Added subscriber: @viadvena

Added subscriber: @Georgefly

Added subscriber: @EvertonSchneider

Added subscriber: @Prodeous

Added subscriber: @Yuro

Added subscriber: @winnertakesteve-1

Added subscriber: @pixeltrain3d

Added subscriber: @Defka

Added subscriber: @Zeirus

This comment was removed by @dodo-2

*This comment was removed by @dodo-2*

This comment was removed by @dodo-2

*This comment was removed by @dodo-2*

Added subscriber: @TheCrowdedOne

Added subscriber: @ephraimpauli

Added subscriber: @blenderrocket

Added subscriber: @2046411367

Added subscriber: @homeworker

Added subscriber: @Confabulatori

This comment was removed by @2905710881

*This comment was removed by @2905710881*

Again, please don't use this task for feature requests or user questions! There are other channels for this: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

This comment was removed by @dodo-2

*This comment was removed by @dodo-2*

Added subscriber: @bent

Added subscriber: @Festivity

Added subscriber: @VDC

Added subscriber: @Motiomancer

Added subscriber: @SteffenD

This comment was removed by @TheCrowdedOne

*This comment was removed by @TheCrowdedOne*

This comment was removed by @dodo-2

*This comment was removed by @dodo-2*

Added subscriber: @Guilherme-Emerich-Setubal

Added subscriber: @LouisLithium

Added subscriber: @matthewg.3d

Added subscriber: @set9

Added subscriber: @Dangry

Added subscriber: @iloveyehan

This comment was removed by @JacobMerrill-1

*This comment was removed by @JacobMerrill-1*

Added subscriber: @fanny

Added subscriber: @ShenCiao-2

Added subscriber: @leomid

Added subscriber: @Imaginer

Added subscriber: @maylog

Added subscriber: @Eliot-Mack

This comment was removed by @JacobMerrill-1

*This comment was removed by @JacobMerrill-1*

Added subscriber: @Steve-Hanff

Added subscriber: @Garek

Added subscriber: @RomanKuz-4

Added subscriber: @DuarteRamos

Added subscriber: @ShyDugong

Added subscriber: @Emi_Martinez

Added subscriber: @StojoArt

Added subscriber: @lictex_1

Added subscriber: @nlate

Added subscriber: @Mounir

Added subscriber: @ClinToch

This comment was removed by @ClinToch

*This comment was removed by @ClinToch*

This comment was removed by @dodo-2

*This comment was removed by @dodo-2*

Added subscriber: @dvi

This comment was removed by @dvi

*This comment was removed by @dvi*

This comment was removed by @Defka

*This comment was removed by @Defka*

This comment was removed by @dvi

*This comment was removed by @dvi*

Please keep this task on topic! This task is for developers and should focus on code design and review. Please refrain from further user questions, including asking for a build, asking for a merge ETA, examples, comparison with other software and so on... It is also too early for bug reports. Thank you for your understanding.

Added subscriber: @brurpo

Added subscriber: @cmzw

Added subscriber: @Aiden-McKown

This comment was removed by @dvi

*This comment was removed by @dvi*

This comment was removed by @Low_Polygon42

*This comment was removed by @Low_Polygon42*

This comment was removed by @dvi

*This comment was removed by @dvi*

Added subscriber: @AditiaA.Pratama

This comment was removed by @AD_Blend-69420

*This comment was removed by @AD_Blend-69420*

This comment was removed by @dvi

*This comment was removed by @dvi*

Added subscriber: @brecht

Added subscriber: @zNight

This comment was removed by @dodo-2

*This comment was removed by @dodo-2*

This comment was removed by @ThomasDinges

*This comment was removed by @ThomasDinges*

This comment was removed by @dvi

*This comment was removed by @dvi*

Like any other online platform, there are rules here as well. I explained this several times before. One again:
Please keep this task on topic! This task is for developers and should focus on code design and review. Please refrain from further user questions, including asking for a build, asking for a merge ETA, examples, comparison with other software and so on... It is also too early for bug reports. Thank you for your understanding.

Or in more simple words: If you are not a developer, working on the EEVEE rewrite, this is NOT the right place for comments.

Please help to keep this platform clean for developers and use places like blenderartists for user discussions. Thanks.

Like any other online platform, there are rules here as well. I explained this several times before. One again: `Please keep this task on topic! This task is for developers and should focus on code design and review. Please refrain from further user questions, including asking for a build, asking for a merge ETA, examples, comparison with other software and so on... It is also too early for bug reports. Thank you for your understanding.` Or in more simple words: If you are not a developer, working on the EEVEE rewrite, this is NOT the right place for comments. Please help to keep this platform clean for developers and use places like blenderartists for user discussions. Thanks.

This comment was removed by @dodo-2

*This comment was removed by @dodo-2*

Added subscriber: @Stat_Headcrabed

Added subscriber: @AM-1

Added subscriber: @johannes.wilde

Added subscriber: @Fynn-Ribbeck

Added subscriber: @Olliver

This comment was removed by @Olliver

*This comment was removed by @Olliver*

Added subscriber: @EvaVomhoff

This comment was removed by @TheCrowdedOne

*This comment was removed by @TheCrowdedOne*

This comment was removed by @Caden-Mitchell

*This comment was removed by @Caden-Mitchell*

Added subscriber: @hzuika

An update is long overdue.

This task has accumulated many delay due to multiple things.

The major reason is that during the middle of the rewrite, I was facing major technical difficulty caused by limitations from our GL 3.3 requirement. So at some point I took the decision to make use of more modern techniques and drop support from older hardware. We are aiming to require GL 4.3 capable hardware in the near future. However this means that we cannot rely on the GL implementation on Apple computers. So I had to sidetrack to another project to make sure that shaders will be compatible with Vulkan and Metal (D13360).

Comming back to the rewrite I had to redo many things a second time to use the more modern way to do things. This was needed for performance reasons.

But with all the added delay and without much real testing possible (because of feature incompleteness and plethora of TODOs) it was starting to feel like a never ending project. So we decided to start pushing the developpement into master in an attempt to guide the developpement using feedback from the Blender Studio. The new implementation is hidden under a new experimental option (59f53f5802). My goal with this is to merge the eevee-rewrite branch into master bit by bit making sure each feature is polished. The GPU module changes needed are already in master.

I'll resume my weekly reports on my [wiki section ]] for the week to week updates. For important milestones and feedback, I created [ https:*devtalk.blender.org/t/eevee-next/23570 | this topic on devtalk .

I would like to thank everyone who showed interest in this task.

An update is long overdue. This task has accumulated many delay due to multiple things. The major reason is that during the middle of the rewrite, I was facing major technical difficulty caused by limitations from our GL 3.3 requirement. So at some point I took the decision to make use of more modern techniques and drop support from older hardware. We are aiming to require GL 4.3 capable hardware in the near future. However this means that we cannot rely on the GL implementation on Apple computers. So I had to sidetrack to another project to make sure that shaders will be compatible with Vulkan and Metal ([D13360](https://archive.blender.org/developer/D13360)). Comming back to the rewrite I had to redo many things a second time to use the more modern way to do things. This was needed for performance reasons. But with all the added delay and without much real testing possible (because of feature incompleteness and plethora of TODOs) it was starting to feel like a never ending project. So we decided to start pushing the developpement into `master` in an attempt to guide the developpement using feedback from the Blender Studio. The new implementation is hidden under a new experimental option (59f53f5802). My goal with this is to merge the `eevee-rewrite` branch into master bit by bit making sure each feature is polished. The GPU module changes needed are already in master. I'll resume my weekly reports on my [wiki section ]] for the week to week updates. For important milestones and feedback, I created [[ https:*devtalk.blender.org/t/eevee-next/23570 | this topic on devtalk ](https:*wiki.blender.org/wiki/User:Hypersomniac#Weekly_Reports). I would like to thank everyone who showed interest in this task.

Added subscriber: @Alaska

In #93220#1327240, @fclem wrote:
The major reason is that during the middle of the rewrite, I was facing major technical difficulty caused by limitations from our GL 3.3 requirement. So at some point I took the decision to make use of more modern techniques and drop support from older hardware. We are aiming to require GL 4.3 capable hardware in the near future. However this means that we cannot rely on the GL implementation on Apple computers. So I had to sidetrack to another project to make sure that shaders will be compatible with Vulkan and Metal (D13360).

Possibly a dumb question, but if Apple support means having to sidetrack to support Vulkan and Metal, why not just use Vulkan as the base for all platforms instead of GL 4.3? Or did I misunderstand something?

> In #93220#1327240, @fclem wrote: > The major reason is that during the middle of the rewrite, I was facing major technical difficulty caused by limitations from our GL 3.3 requirement. So at some point I took the decision to make use of more modern techniques and drop support from older hardware. We are aiming to require GL 4.3 capable hardware in the near future. However this means that we cannot rely on the GL implementation on Apple computers. So I had to sidetrack to another project to make sure that shaders will be compatible with Vulkan and Metal ([D13360](https://archive.blender.org/developer/D13360)). Possibly a dumb question, but if Apple support means having to sidetrack to support Vulkan and Metal, why not just use Vulkan as the base for all platforms instead of GL 4.3? Or did I misunderstand something?

@Rawalanche having shader syntax compatible with vulkan is an important step into this direction. Having a production ready fully working vulkan backend takes (a lot) more time. Bumping the version to OpenGL 4.3 would make it easier to transition to vulkan.

In #93220#1327526, @Jeroen-Bakker wrote:
@Rawalanche having shader syntax compatible with vulkan is an important step into this direction. Having a production ready fully working vulkan backend takes (a lot) more time. Bumping the version to OpenGL 4.3 would make it easier to transition to vulkan.

I see. I did not know upgrading GL version is/could be just intermediate step on the road to Vulkan backend. That's why I asked :)

> In #93220#1327526, @Jeroen-Bakker wrote: > @Rawalanche having shader syntax compatible with vulkan is an important step into this direction. Having a production ready fully working vulkan backend takes (a lot) more time. Bumping the version to OpenGL 4.3 would make it easier to transition to vulkan. I see. I did not know upgrading GL version is/could be just intermediate step on the road to Vulkan backend. That's why I asked :)

Added subscriber: @insideitall

Thank you so much Clement, this was all I wanted! I wish you the best of luck with the project, I know nothing about program development but an eevee rewrite sounds like a lot of work. Also sorry Thomas for all the trouble, just wanted to thank Clement :D

Added subscriber: @Sparazza

Added subscriber: @LasseFoster-2

This comment was removed by @dodo-2

*This comment was removed by @dodo-2*

Removed subscriber: @AM-1

This comment was removed by @JacobMerrill-1

*This comment was removed by @JacobMerrill-1*

This comment was removed by @dodo-2

*This comment was removed by @dodo-2*

Added subscriber: @Zelo101

Added subscriber: @GaryRitchie

Added subscriber: @SamGreen

Added subscriber: @Macilvoy

Added subscriber: @TroyAC

This comment was removed by @TroyAC

*This comment was removed by @TroyAC*

Added subscriber: @Sean-Boyle

Added subscriber: @MrAlwis

Removed subscriber: @StojoArt

Added subscriber: @vegetablescum

This comment was removed by @vegetablescum

*This comment was removed by @vegetablescum*

Added subscriber: @zanqdo

Added subscriber: @Hannah-Umit

Added subscriber: @mod_moder

Added subscriber: @finalflasher

Added subscriber: @RobertWesseling

Removed subscriber: @Sean-Boyle

Added subscriber: @hipda

This comment was removed by @hipda

*This comment was removed by @hipda*

Added subscriber: @osayami

Removed subscriber: @bent

Added subscriber: @Striletsky

This comment was removed by @dodo-2

*This comment was removed by @dodo-2*

Added subscriber: @NEEO

Added subscriber: @Soichi-Sugano

Added subscriber: @hamza-el-barmaki

This comment was removed by @hamza-el-barmaki

*This comment was removed by @hamza-el-barmaki*

Added subscriber: @satishgoda1

Added subscriber: @baybaypras

Added subscriber: @Spundun-Bhatt

Added subscriber: @Benni-Merz

Added subscriber: @DARRINALDER

Added subscriber: @Horizon42

Added subscriber: @zhanghua

Removed subscriber: @Low_Polygon42

Added subscriber: @Joe_W

Added subscriber: @Yacine-Teach

Added subscriber: @Nik-9

Added subscriber: @Basarchitects

Added subscriber: @digital0785

Added subscriber: @intracube

Added subscriber: @Cigitia

Added subscriber: @Asger

Added subscriber: @jpburns

Added subscriber: @Austin-Berenyi

Added subscriber: @SpectreFirst

Added subscriber: @Nico-Traber

Added subscriber: @Strike_Digital

Added subscriber: @cueqzapper

Added subscriber: @Nabarun

Added subscriber: @Jarrett-Johnson

Added subscriber: @JanErik

Added subscriber: @heini

Added subscriber: @julien.hondaa

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Labels Milestones

EEVEE-Next #93220

Motion Vector

Film

Camera

Motion Blur

Shading

Light

Shadows

Render Passes

Global Illumination

Volumetric

Extended target