I’ve been trying to render a Nuke scene on the farm that uses and Alembic file from Modo. But the jobs fail on the farm. In my ReadGeo node, if I unselect “read on each frame” the job will render just fine. But this defeats the purpose of Alembic in Nuke since I am using animated geo. Is this a known issue?
Hello James,
Not sure I have ever seen that one before. Can you share some job reports or slave logs? Thanks.
yeah sure. I’ve got a deadline on Wednesday, but I’ll get some logs up ASAP.
OK, so I have a test scene, my Alembic file, the modo file, and the task report zipped up in this file. Sending this to Deadline should cause the job to fail. As I mentioned in my first post, if you uncheck “read on each frame” the job will render fine.
Nuke_Alembic_Test.rar (1.03 MB)
Hello James,
So in doing some testing, I came across this mouse over info box on the ‘read each frame’ option for your ReadGeo. It would seem to indicate this is not a Deadline thing, but a Nuke thing. It clearly says that this should be on for animated objects. I would check with The Foundry to find out why this is.
That is there so that if you are reading in animated geo, Nuke will read each frame. It’s on by default and if you uncheck it the geo will be frozen on the frame that you are currently on. In my case I do have animated geo and do need that to remain checked to produce my render. My question for you guys, does Deadline not support this feature? It’s a pretty important feature if you are doing any sort of 3D projection in Nuke.
Hello James,
I ran into some errors about Write1 not having any channels that prevented me from testing any further, but I ran into the same wall on both sides. Due to pathing being an issue, think it would be good to get a successful and unsuccessful render log so we can see if the commands change. If they don’t, I’ll have you try to run the same scene saved with both possible options, one with it off, and one with it on, and we can see if it is a nuke command line issue, or a Deadline issue. Thanks.