It's not an OpenGL problem, because it shows up in my final render (and I never use OpenGL rendering).
Memory could be a possibility. But I have multiprocessing turned off and the max amount of RAM devoted to AE. It's around 60 32bpc layers with six Adjustment Layers. At 2K, that's going to gobble up a lot of memory (plus effects).
Each 32-bit 2K layer is 35MB x 60 = 2.1GB. Plus whatever internal precomp AE has to make for Adjustment Layers. Plus whatever memory is needed for plug-ins at 32bpc. Hmmmm.... that doesn't look good, memory-wise.
Any ideas how to solve a low memory problem? Anyone got a copy of Nuke they want to loan me?
Actually, there's one thing I could thingk of: You have a non-32bpc effect somewhere inbetween. Native 32bpc effects use something called SmartFX, which is a tiled rendering algorithm for better memory efficiency. Effects not optimized to that standard might break rthe rendering order, as they are impossible to render in tiles, which in turn may lead to the odd memory problem where certain tiles of successive effects have no data to operate on.
i have the exact same issue with my comp now. i tried every trick i know but it just wont go away.
interestingly it is the same area of the image as with your example.
i could however narrow it down to one layer. which when disabled led to a normal render. but without that layer it was impossible for me to use that render. so i tried to "bake" things down. didnt help either because i coudlnt manage to render that one comp without it glitching away. i even tried to render that layer out again from max. with a different file format (tif, open exr, tga, png, bmp) nothing resolved the issue.
i also disabled every effect... didnt help.
i have a 8 core i7 with 16 gig ram. i tried to disable multicore and rendered on one core it still did happen. and my comp is only 720p. my ram doesnt even fill up completely (12 gig assigned to afx)
the interesting thing is. the error happens always on the same frames for one session/layer mix. if i disable or enable another layer it switches place (hops to another frame).
anyone got an answer to this?
I wonder if you could have a NaN pixel in there. If you had a big blur or something, that could create that block, and it would go away in 16-bit mode. Read about NaN's (and a solution) here: