I just started experimenting deadline to manage our renders within katana using redshift renderer. I’m using Katana 2.5 and deadline 8 on windows, deadline free license at the moment but need to add more slaves for more rendering power in near future.
I’ve installed deadline repository and mongo ans have one slave in same machine. Also I’ve installed deadline submitter for katana. I can submit jobs to the slave within katana and I can see them in dl monitor with status showing its rendering, but no progress and no gpu activity and of course no rendered image at the end. it gives me no error, simply no render. even when it shows render has been completed.
Now I’m wondering which one can cause this, deadline, katana or redshift? I can render same scene within katana and its render to disk command with no problem.
Any idea and experience with katana would be really appreciated.
Hey Rou, welcome to our little slice of public support fun.
You’re definitely in one of the lesser walked paths, so at this point I’m not sure what the issue might be. Usually the job reports will steer us in a better direction, but you may want to submit a test scene (just a cube on a plane) so that you’re render log is somewhat anonymized.
Hmm. Well, the job log isn’t very helpful as far as logging. It does spend about 10 minutes doing something as there’s a gap in the logs, but it’s not clear what that something is. I’ll ask the dev team what they think of it.
Relevant log info:
2017-08-22 12:58:20: 0: STDOUT: [INFO python.Main]: KATANA_RENDER_TILE_SIZE defaulting to 256x256
2017-08-22 12:58:20: 0: STDOUT: [INFO python.Main]: KATANA_IMAGE_MEMORY defaulting to 11726 MB
2017-08-22 12:58:20: 0: STDOUT: [INFO python.Main]: KATANA_IMAGE_DISK_MEMORY defaulting to 6948 MB
2017-08-22 12:58:20: 0: STDOUT: [INFO python.Main]: KATANA_SPEC_CACHE_ENABLED defaulting to 1
2017-08-22 12:58:24: 0: STDOUT: Using localhost
2017-08-22 12:58:25: 0: STDOUT: [WORKER] started
2017-08-22 13:08:42: 0: STDOUT: [INFO plugins.Redshift]: Closing the RS instance. End of the plugin log system.
2017-08-22 13:08:42: 0: STDOUT: [WORKER] shutdown
2017-08-22 13:08:43: 0: INFO: Process exit code: 0
2017-08-22 13:08:43: 0: Done executing plugin command of type 'Render Task'
Hmm. I’ve been informed that we don’t support Redshift with Katana as of yet, so I’ll add that to the dev system. I’m not quite sure what can be done if anything yet while you wait, but I’ll find out.
No problem. Can you think of anything that might give us a leg up here? I’m kind of curious how Redshift is called within Katana under the hood. I guess as an end user that’s probably not something you’ve had to worry about up until now.
So, from reading both logs everything seems to be normal. I’m assuming it’s just not saving somehow… How does Redshift know where to store its output? Is is something we’d have to control? It looks like we’re just running things via command line switches so I’m not sure what’s available for us to pass in (installing Katana now).
I don’t think its just not saving, because gpu is idle all the time. BTW it worth mentioning that I’m using a .bat file to run katana to set env variables.
