Page MenuHome

EEVEE image sequence not updating in animation render
Closed, ResolvedPublic


System Information
Operating system: ubuntu 18.04 lts 64 bit
Graphics card: nvidia geforce gt 840 (in this video i turned it off and used CPU graphics because of power saving)

Blender Version
Broken: blender-2.80-72ede30d0f97-linux-glibc224-x86_64

Problem to render every frames in animation in eevee

There is a problem that eevee doesnt render every frames and make mistakes. here is a VERY SHORT video to explain problem. Thankkss

Event Timeline

Can you upload the .blend file and the video, so that we can reproduce the issue?

Jacques Lucke (JacquesLucke) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Apr 25 2019, 2:40 PM

@Jacques Lucke (JacquesLucke) Ow excuse me that's here. :)

Jacques Lucke (JacquesLucke) raised the priority of this task from Needs Information from User to Confirmed, Medium.Apr 25 2019, 3:51 PM

A shorter video that shows the issue:

Left are the rendered frames, right is in Blender.

This is a depsgraph / iuser problem.

image_user_id_eval_animation works OK for the viewport but when rendering, it seems that iuser->framenr stays the same.

As the iuser pointer keep changing between rendered frame I suspect that there is COW happening somewhere and it's not setting IMA_GPU_REFRESH as it should to ensure the correct image sequence frame.

That said this solution is still a bit hacky. @Brecht Van Lommel (brecht) since you were the one who introduce the patch to support the image sequence I'll leave it to you.

Brecht Van Lommel (brecht) raised the priority of this task from Confirmed, Medium to Confirmed, High.May 23 2019, 1:57 AM

I'm having trouble reproducing this with both latest master and rB72ede30d0f97. Is this still an issue?

I guess it might be some threading issue, between viewport and render redraws sharing the same image buffer. Not sure. We definitely know the sharing of the image buffer is weak, and could try to ensure there is a separate buffer for render and viewport, even if a more general image cache would be too much work now.

I'm still able to reproduce the issue.