That looks really cool!
There cant be noise correlation between pixels for the denoiser to work. There is no denoiser or blur on eevee legacy renders, thats why it works.
You can probably make it work with next by disabling every denoiser in eevee settings.
Iāve played with different settings in Render Properties, like Denoising and Filter Size, but no change or improvement.
Are there other denoiser settings in eevee Iām missing?
3 Likes
Oddly enough, the Compositor Denoise Node does work with a sample of 1.
Are you not using the Raytracing Denoising?
Just the Denoiser node in compositing.
Itās discussed as an issue/bug currently. We also discovered the 1 sample denoising, which can be explained technically (not by me)
That is cool as long as it freezes in case Blender freezes. So seeing it moving tells you that the process is actually running
2 Likes
Below a comparison between Legacy and Next using my personal work.
These are just a collection of observations. Iām still trying to figure things out in Next.
- Iām aware about the SSS leaking being a limitation. So Iām trying to look for other solutions
- The Denoise node not detecting Eevee Next noise has been reported as a bug
11 Likes
Hello all, Iāve been testing EEVEE in 4.2 beta and have come across a problemā¦ I cannot seem to get glass objects to show anything behind them when the raytracing method is set to āLight Probe.ā
Does anyone happen to know if this is a known limitation or a bug that I should report? Iāve searched everywhere for information but canāt seem to find any indication one way or another.
Thanks in advance for any help.
EDIT: I should probably note that I have it working with āScreen - Traceā method and have tried changing all sorts of settings and using thickness and of course, adding light probes. Nothing seems to help.
@fclem take a look at this problem please, looks like it is also caused by ea5e1fef2a
#123413 - EEVEE-Next: Complex files with many lights crash when entering rendered view - blender - Blender Projects
Shadow Catcher should work if you set the material to blended mode (itās not possible to drive the opacity of a dithered material with ShaderToRBG).
Since some workflows rely on the SSS leaking between objects, maybe we could add a global toggle to disable SSS object id detection, even if it doesnāt match the Cycles behavior.
1 Like
Not a bug. You either use Blended transparency, or use Dithered+Screen Tracing.
1 Like
We are well aware of all the open issues (especially those tagged as high priority).
Thereās no need to poke at devs like that.
3 Likes
But blended mode doesnāt work with render passes ā¦ so how would you isolate it in post?
(Purely a question, as Iāve not yet tried the node setup posted just now, so perhaps thereās an easy way.)
2 Likes
You can always use a view layer.
I guess at some point we will add support for the Shadow Catcher property, just like Cycles does.
1 Like
Oh, I see what you mean. Isolate on its own view layer, then that layer itself can be your post source. Yeah, I think that should work and doesnāt seem like much extra overhead.
Might involve a material override, also not that big of a dealā¦ Sorry just thinking out loudā¦
Unfortunately, the ShadertoRGB node does not work properly with raytracing. Once you plug the diffuse shader into the ShadertoRGB node, all Raytracing (AO or GI) disappears.
Which makes it pretty useless as a shadow catcher. Having it at least retain AO would solve a lot.
BTW, I actually donāt need transparency or Blended mode. I use the World color in the floor shader instead. This keeps the floor opaque and it clips anything penetrating, similar to Cyclesā shadow catcher (image above has Suzanne penetrating the floor).
But the problem remains, as this method also needs the ShadertoRGB node to function properly. I fear Iāll have to wait for a proper shadow catcher in the future.
2 Likes
Good day to everyone! I have a question. Does Subsurface only work with light sources, or can it also receive scattered light from an HDRI card, similar to how it works in Cycles?
2 Likes
Should work. Suzanne below is lit only with one of the HDRIs that come with blender. No light.
No idea about the best settings, but I had to set the Thickness value lower than 1 in the Material Output.
2 Likes
As much as I love EEVEE Next, it struggle a lot with high light count compared to EEVEE Legacy and the viewport performance is just abysmal (A scene with ton of point light in EEVEE Legacy managed to pull 10-15 fps but with Next itās only 0.5-1 fps and somehow)ā¦ Also doing stuff like adding a material, turning on/off raytracing(or any other settings) in EEVEE Next cause Blender to froze for a solid 5-8 second or just straight up crashing.
Wish i can show the comparison between Next and Legacy,but iām not allowed to upload file because Iām a new user
3 Likes
Regarding Bloom
Compared to Legacy Bloom in the Render Properties, the new Bloom in the Glare node has very little options.
The new Bloom:
- needs the compositor to be open and enabled.
- requires a lot more node set-up for specific needs. This makes it extra complicated, and some of us lack that high-level technical skill.
- only has 4 sizes. Scaling it with a blur node doesnāt work, as it would also scale an objectās light source. Would I have to clamp it? And no clue how to scale it lower than 6.
- gives gradients a harsh cut-off thatās hard to fix (see image below)
To me, the old and the new Bloom seem like 2 different tools/functionalities. Is there a reason why they cannot co-exist?
I have a pipeline that is based on simplicity and efficiency, so the ability to quickly set Bloom and Color Management in the Render Properties is great.
If the reason is ābecause almost everything in the compositor can be visible in the viewportā:
- does this mean that some color management properties (Exposure, Gamma, RGB Curves) will disappear from Scene Properties as well? Since thatās also in the Compositor.
- what if I want to work with Bloom, but not with other nodes Iāve set up in the Compositor? Do I have to mute everything except Bloom?
I truly hope Bloom can come back in the Render Properties, as itās such a powerful functionality for the real-time āexperienceā.
7 Likes