We are experiencing an unusual issue in Maya, when rendering on the farm (Deadline), local rendering behaves as expected.
We have a simple Maya scene which contains some native geo and also a vrscene asset loaded through the VRay Scene manager. All renders fine when testing locally but when submitted to the farm the frame completes in a minute or two without error but contains only black pixels. If I remove the vrscene node from the render layer and re-submit the job finishes as expected minus the necessary asset in the render.
Are there any known issues when using vrscene files as assets inside another file?
Were using V-Ray Next for Maya, hotfix 1 version 4.04.02.00010. Maya 2016
Update - It seems its not the vrsene that is causing the issue.
Upon sending to the farm via Deadline, the shotCam’s transform, rotation and scale seem to be ignored and it renders from a default position (0,0,0). This has begun happening since updating to Next from 3.60 hmm
I doubt its the camera, there is most likely another issue. I’ve rendered both vray scenes inside maya scene and shot cams over deadline and newest vray builds without issues.
The camera definitely renders from a default position as its apparent in the alpha. The position of the camera looks to be the same as a default front cam, however the camera that is reported to be picked up in the log is the shot cam.
Sure, here is a stripped down scene with some proxy geo and the same shotCam over 6 frames.
This scene produces the same issue for me in that the shotCam is reverted to a default position when rendered through the farm (Deadline 7). Renders fine locally.
Just to update further, I have since tried exporting as vrscene and submitting as a VRay Standalone job which renders fine. The issue seems to be associated with Maya Batch on the farm or when rendered locally via Maya Batch.
So I just tested with maya 2016 sp6, vray_40303_28410 and deadline 10 and all renders as the camera is seeing it in maya viewport. So a few questions - are you picking the actual camera when you are submitting to deadline in deadline submitter? Also I noticed you are submitting to one machine, does it happen to all machines on the farm?
Lastly, try export camera as alembic and bring back, make sure you select it from list of cameras in deadline.
To answer your questions, I am selecting the camera in the deadline submitter and also selecting it in the common rollout as the Renderable Camera - I have tried various combinations here with the same results.
Same results across the entire farm with the same versions of Maya and V-Ray as the machine submitting the job.
However, deadline aside, I get the same results when just doing a local Maya Batch Render so I am not sure it has anything to do with deadline anymore.
I will try the alembic camera, that is a good idea.
I mean this is really basic to render animated camera its what maya / mayabatch and vray meant to do. Can you show me what you get? How did you render animated cams before?
Just to set the picture a little bit, I have 15 years experience working in the Automotive and TVC industries, have lead teams at The Mill, Framestore, Nexus Productions and RealtimeUK - Just in case you think that I might be a bit wet behind the ears
I have rendered animated cameras every way imaginable and possible, this is a new issue here since updating to Next in our setup.
