On a side but possibly related note if you put the same exact material (brick texture into bump node's height) on suzzane and then compare Eevee's normal render pass with Cycles normal pass you can tell that Eevee seems to have a lot more green than cycles. No idea if this is expected or not, just thought i would share.

I don't think it's anything specific to the brick texture in fact i don't even think it's anything specific to the bump node. I have been able to reproduce this using just good old math nodes and texture coordinate node.

just turn off the motion blur and the render successfull, when i turned on the motion blur it gets crashed anytime.

I think I've fixed this by modifying a depth correction factor in effect_subsurface_frag.glsl and removing interpolation.

I can confirm that a strong Moire pattern appears, but this might just be a limitation of the Brick Texture's implementation in EEVEE. @Clément Foucault (fclem) or @Jeroen Bakker (jbakker) will have to let us know.

I can confirm the problem in the attached file.
This reminds me of the bug described in T82240: Issues with the viewport when activating the option "Display in front"..

I can't see anything holding this diff any longer.

• EEVEE Cryptomatte: Add support for motion blur.

• Cleanup: Removed unneeded include

• Fixed unstable Color/value detection. Now the type of the AOV is added as part of the aov_hash.

In D7010#240960, @Clément Foucault (fclem) wrote:

Also the render viewer seems to have issue with the single component buffer (treated as color + alpha until you change the display mode to color, which is the only display mode available after zbuf).

This is a known issue already present in Blender for ages. We should fix this, but wouldn't do this as part of this patch. T83314: Image Editor: Viewing a value buffer could use incorrect channel selector

Oh boy it's hard to respond if you completely edit your posts while I'm replying to them.

I'll bet 99.99% of users don't care how that noise is generated, but they don't want obvious artifacts to show up so easily. So YES, this is a bug in Blender. If Perlin noise, or whatever mathematical formula the developers decide to use, doesn't work for creating noise on a simple flat wall then it needs to be replaced or fixed. Is it a critical bug that needs work today? Obviously not, but it's still a bug. That node is used by a lot of users and it's the only noise node besides White Noise, which is used for other things entirely. There's just so much resistance to acknowledging that there's an issue here.

@Russell (russ1642) Nobody is denying that there is banding. You don't have to defend yourself, this was all just discussion about technicalities. I'm sorry if we gave you the impression that this was somehow personal.

In this thread I've been told that I just don't understand the Object or Generated texture coordinate spaces. I've been told that I'm wrong for expecting the Noise node to not have obvious non-randomness to it. I've been told that I'm confusing the Noise node with the White Noise node. All this because there's obvious banding in what's supposed to be a simple random noise texture on a flat wall. I'm honestly only trying to help. I shouldn't have to defend my bug submissions this much to keep them from being rejected.

@Russell (russ1642) I'm sorry if we were talking past each other. I was in no way saying that the banding is your fault, it is inherent in the way the procedural noise is generated according to @Omar Emara (OmarSquircleArt). I just thought you there might be a misunderstanding what the noise node does, because it isn't random noise and the 2.79 noise used to be random noise.

Thank you for A, acknowledging the issue, and B, not telling me it's my fault. I will gladly work around the issue now that I know how.

@Russell (russ1642) We understand your frustration. Ideally, this banding pattern shouldn't occur. However, that's how it works, sometimes procedural textures behave unexpectedly in certain cases. We are typically able to workaround those issues one way or another. I am not sure if we will be able to workaround this particular issue, but we will certainly look into it.
Meanwhile, you may mitigate the issue as I described above. Alternatively, a much simpler approach would be to rotate the texture coordinates by a random amount as demonstrated below.

The banding should not be there. It's a bug. I don't want white noise, which is noise at all frequencies. I want noise with controllable frequency and effect, which is what the noise node is used for. I don't want anything that has zero noise, such as the hard banding effect, to be generated by the node. I didn't think I'd need to get so technical about not wanting weird banding effects. Ask yourself if this is what the designers had in mind when they created the noise node.

@Russell (russ1642) Yes, for the reason @Omar Emara (OmarSquircleArt) explained. The Noise texture node is Perlin noise, not true random noise. If you want true random noise use the White Noise node.

Are you suggesting that the visible banding pattern is correct? The noise node is supposed to do that? You're saying that I just don't understand the function of the node. I don't see any reference to banding patterns and such in the documentation. Noise is supposed to be random. And don't just correct me if I'm wrong, correct everyone because we're obviously mistaken about the Noise Texture node.

@Russell (russ1642) Could it be that you're confusing the Noise and White Noise nodes?

The entire purpose of the noise node is to be random and free of patterns, and it's used in so many node trees to do just that. It's clearly a bug/known issue.

@Germano Cavalcante (mano-wii) This happens due to very slight rotation along one of the axis. A simple way to replicate that is to add a plane and rotate it along the x axis with 0.5 degrees. Attached a minimal blend file for that. That's also why the checker texture appear as in your screenshot.

I tested with motion blur and it works.

Thanks. Can I also ask about the generated mapping? It should create a coordinate space that goes from 0 to 1 over the bounds of the object. That shouldn't create patterns in the noise texture. Also, if I use the object type mapping it should create a 3d coordinate space based on the object's origin and transformations. Again, no reason the noise texture should show patterns. If those assumptions are wrong please let me know because often with these nodes, and the thin documentation, people aren't confident on how things are supposed to work. I'm only pretty sure and you're obviously not because you thought that this had something to do with UV mapping.

I have a crash when using motion blur with steps > 1 :

/home/clement/Blender/build_linux/bin/blender(BLI_system_backtrace+0x35) [0x4d64f9f]
/home/clement/Blender/build_linux/bin/blender(_BLI_assert_print_backtrace+0x16) [0x4c961b0]
/home/clement/Blender/build_linux/bin/blender(EEVEE_cryptomatte_output_init+0x145) [0x29d292f]
/home/clement/Blender/build_linux/bin/blender(EEVEE_renderpasses_output_init+0x2e2) [0x29601a4]
/home/clement/Blender/build_linux/bin/blender() [0x2949c17]
/home/clement/Blender/build_linux/bin/blender(DRW_render_to_image+0x333) [0x292f756]
/home/clement/Blender/build_linux/bin/blender() [0x4ad84c8]
/home/clement/Blender/build_linux/bin/blender(RE_engine_render+0x4e2) [0x4ad8a43]
/home/clement/Blender/build_linux/bin/blender() [0x4ae094b]
/home/clement/Blender/build_linux/bin/blender() [0x4ae0c84]
/home/clement/Blender/build_linux/bin/blender() [0x4ae11e2]
/home/clement/Blender/build_linux/bin/blender() [0x4ae1eeb]
/home/clement/Blender/build_linux/bin/blender(RE_RenderFrame+0x15f) [0x4ae301a]
/home/clement/Blender/build_linux/bin/blender() [0x3fa89dc]
/home/clement/Blender/build_linux/bin/blender() [0x26d09ad]
/home/clement/Blender/build_linux/bin/blender() [0x4d700dc]
/usr/lib/libpthread.so.0(+0x93e9) [0x7f3a15c1e3e9]
/usr/lib/libc.so.6(clone+0x43) [0x7f3a11947293]
BLI_assert failed: source/blender/draw/engines/eevee/eevee_cryptomatte.c:153, EEVEE_cryptomatte_output_init(), at 'g_data->cryptomatte_accum_buffer == ((void *)0)'

Okay, I can't confirm it as a bug, but I can forward it to the Render & Cycles and EEVEE & Viewport team for the developers to check it out.
It's good to keep in mind that their task list is quite long and it may take a while for them to take a look.