Hi Ryan
I think this is not the first time that is reported, but I’m having some problems with the camera/viewport lock option on the Max render setup.
When this option is checked, It seems that deadline renders another viewport, and it is always the one that I don’t want!
Do you have a solution for this?
Best regards,
Mario
Hi Mario,
Yes, DON’T use the viewport lock!! 
That’s the short answer, and while I’m sure Bobo could go on for paragraphs about why you shouldn’t rely on it, I’ll provide my reasoning here as well.
The biggest issue is that the locked viewport feature wasn’t exposed to the 3dsmax SDK and maxscript until recently, and there are still bugs in it that we cannot workaround (these bugs were confirmed by Autodesk when we submitted the bug report). The latest version of Deadline works with it the best we can, but it is still not 100% guaranteed that it will work. So to save yourself headaches, we recommend to not rely on the viewport lock, and instead make sure the viewport you want to render is selected prior to submitting the job.
Cheers,
Sorry to thread-jack, I found a bug (max 9, deadline 4.0) when you have 2 cameras with the same name, say one has been Xreffed in for instance, then Deadline can easily render from the wrong one as I assume it is storing the camera identification as a name string and thus has no way of knowing which one it should actually use. It doesn’t come up as a warning in the Sanity Checker either.
We added a sanity check for duplicate camera names a while ago (pre-4.0), so that’s strange that it’s not catching your duplicate names. When there are duplicate cameras, you should see this error in the sanity check:
If you don’t see this, can you upload a small sample scene that reproduces the problem?
Thanks!
Get that message if I XRef Object in the camera, but not if I Xref Scene the Camera in.
Can you post a sample package that reproduces the problem?
Thanks!