Eevee 6.0 Render Nodes: Keep Legacy + Next + Nanite Alive Forever
The Problem: Eevee Next raytracing killed legacy speed on low-spec machines. No middle ground.
The Fix: Rebuild Eevee's RENDER ENGINE as nodes – both Legacy Eevee AND Eevee Next live together in one hybrid system.
Both Engines Coexist in Nodes
| Legacy Path | Eevee Next Path | Hybrid Magic |
|---|---|---|
RasterShadows
🟢 120fps
|
RT_Reflections
🟡 30fps
|
Mix 70/30 per scene |
LegacyGI
🟢 Screen-space
|
FullRT
🔴 Path-traced
|
FPS-scaled blending |
NaniteGeometry
🟢 RT-ready
|
RT_Volumetrics
🟡 Medium
|
Viewport stays smooth |
Example Node Tree:
[Your Facial Rig] → [NaniteGeo] → [Legacy Shadows ●●●] ─┐
├─> [Mix 80/20] → [60fps Viewport]
[Next RT Glass ●●○] ──────────────────────┘
Legacy + Next = Unkillable
- Legacy path = exact 4.1 Eevee recreation (screen-space everything)
- Next path = full raytracing (volumetrics, refractions, probes)
- Mix nodes = 80% legacy speed + 20% Next realism = perfect viewport
- No more deprecation – both engines evolve together
NOT Just Materials
| Shader Nodes | THIS Render Engine |
|---|---|
| Per-object BSDFs | Global GI/Shadows/RT |
| Post-process FX | Pre-pixel pipeline |
Why This Wins
- Legacy stays alive – recreate it exactly via nodes
- Next gets better – add Lumen/Nanite without breaking old workflows
- Hardware adaptive – weak GPU? Auto-legacy. RTX 5090? Full RT.
- Rigging heaven – your calisthenics characters at 60fps viewport + realistic glass
Dev Challenge:
@fclem @Jeroen_Bakker
MVP:
LegacyPath → Mix → NextPath
node + FPS limiter.
Both engines live forever.
Poll: Node-based Eevee keeping Legacy + Next alive?
- Yes – perfect hybrid
- Demo first
- Legacy only forever
#Blender #EeveeEngine #LegacyLives #RenderNodes
4 Comments
if you can achieve the functions you mentioned completely on your own and maintain 2 render engines perfectly forever, it's a 1000% win so that other developers can save time to improve other stuff. you will be the MVP ;)
From 4.0 when introduced raytracing into eevee, everyone was complaining about eevee next killing eevee legacy!!! And Now u are comming up with these argument???
Yeah, fair callout – those complaints were 100% valid back then.
But here's the difference: I'm not saying "keep two full engines forever" (that's dev hell). The node idea turns Legacy behavior into a user-configurable node tree using existing render blocks – one codebase, zero double maintenance.
MVP test: Just expose RasterGI + ScreenShadows as starter nodes. Artists recreate Legacy speed instantly. Devs freed up for bigger features.
No sacred cows harmed. Both camps happy? 😎
"just add nodes"