Right textures in Live Viewer, but not in final render

Tue Dec 20, 2016 7:34 pm

I'm rendering a calendar with a bunch of pages each side of each page showing a different month. Each page has a mix shader set to "side" so I can put different months on each side of the page. In the live viewer, everything looks fine. If I render "current frame", everything looks fine. However, if I render the entire sequence, the textures are not on the correct pages and the alignment is off. Scene was initially built in 3.04.3. I updated to most current version in hopes it would fix this, but it's still there.

Apologies if this has been answered before. I only was able to find issues with lighting not matching and gamma issues on shaders.

Thanks in advance for any help.

Tue Dec 20, 2016 9:24 pm

How can we know that without seeing your scene? My estimation is you changed to "send all data" method for rendering or so. Do you have somethings to share?

Tue Dec 20, 2016 11:10 pm

It's not set to "Send all data". As far as I can tell it's set on "Resend only updated objects" (unless there is another place that can be changed that I'd have accidentally adjusted). I can't share the scene as is, but I'll try to widdle it down and see if I can post it.

Tue Dec 20, 2016 11:12 pm

Sure! Very small example scene is enough. I don't want your whole content. Thx

Wed Dec 21, 2016 12:21 am

Not sure if you need the texture files or whether you can see the issue without them. If you need them, let me know. Thanks!

Wed Dec 21, 2016 1:19 am

I figure you'll probably need them. I'm dumb.

I'm only sending a small portion of them though.

Wed Dec 21, 2016 1:22 am

Interesting! I'm seeing LV and PV have similar on outputs. Which frame range is wrong for you? Only problem i can see is that page_1 is unvisible on output.

Wed Dec 21, 2016 1:38 am

Hmm... 170-542. I made it to about 235 before I came back and noticed the errors. And yes, that disappearing page has also been an issue. Can't figure that one out either.

Wed Dec 28, 2016 9:50 pm

I'm still looking this scene. It's weird one. strange behaviour on C4D's itself also. Seems like a cache generation problem when it's opened. See video.