Weird glitch on surface on frames at random
Question Materials and Textures

Question

I'm having trouble with a surface I came up with for the ground in a personal project that has turned into the greatest rabbit hole of my life.

This is the material node tree, which I hope when I post can be seen at full size because I'm not familiar with this forum:

8-24 at 11.31.24.png

The camera is pointing almost straight horizontally angled a bit upwards, or Z=0.019844 m and X rotation 97º. Other than that, Z rotation is keyframed from 0º to -360º, from frame 12197 to 14500. This is a 2160p project at 60 fps.

Other than the floor, there are 8 planes in a circular pattern, with the camera being at the origin and rotating on its own Z axis so it shows each plane until it shows the first one. These planes are like giant screens which show videos, but these videos are not live motion, they are screen recordings.

So those are pretty much the only things in the project, other than two paths that are used for alignment and set to not render. Not a very complex project.

But every few frames the multifractal pattern changes for one frame or two, making it useless because it's very distracting. Just in case you can't see the tree above in detail, here's the node for the noise texture:

8-24 at 12.23.19.png

And here are the render settings:

8-24 at 11.32.01.png

8-24 at 11.32.18.png

8-24 at 11.32.34.png

8-24 at 11.32.48.png

8-24 at 11.33.10.png

This is rendered to an EXR sequence, float full, no compression. Most of the frames are fine, they show as they are supposed to be, but it's one or two every few seconds that go out of whack. Here's what it's supposed to look like:

8-24 at 12.05.43.png

The bad frames look similar, but the pattern is different.

Any suggestions?

Answer 1 · 2024-08-25T00:12:07Z

Omar Domenech replied August 25, 2024 12:12am

Yes, it's a very common glitch EEVEE has. What I usually do is to go the frame that came out with the error and just re-render it. And I mean a normal still frame render, not animation render. Most of the time it just comes out fine and I manually save the frame. Sometime it requires I re-render it again before it comes out right. But that usually does the trick. And don't worry, everyone that renders in EEVEE comes up face to face with this annoyance.

Answer 2 · 2024-08-25T00:46:29Z

L

replied August 25, 2024 12:46am

Thanks for your reply. Actually I forgot to mention that I had already tried to re-render some of these bad frames, and they came out just as bad, and not in some random way, but identical to the initial bad frame.

But after trying lots of different changes in the render and material settings and seeing the same problem, I decided to switch to Cycles. It will be slower, but I'll have to put a few extra machines to render. On the upside, the texture looks better, and the glitch I mentioned doesn't happen. I'll just render in 1080p and upscale in Resolve.

👌