As you are probably aware of, when trying to submit maya scene from version 2018.2 for example and on-farm have 2018.4 or any difference in version at all even if it is .X update difference, rendering on slave will fail and error will report failed to load scene .
Is there a way to completely ignore versions of Maya and just show that to farm and let slaves render?
I had cases with scenes from version 2018.0 with even some referenced files from 2017 load fine in maya 2018.5 and render without issues. But on deadline even if it is a pure scene with only .1 upgrade difference it fails.
Any way to just override that and force rendering?
If I recall correctly, the problem is only the inverse: Maya will fail to load if the scene was authored in a newer version. We don’t have explicit failures for this, so if the scenes are generating errors there may be something else at play here.
Would you be able to render a test scene (to avoid showing your current project’s paths and names in the logs) then post a job report here when it fails?
Long wait for reply just too busy.
Ok here is again what I mean.
I submit from maya 2018.6
It fails loading on every version bellow that even tho on GUI it loads fine and render.
Is there a way to simply ignore maya version and push render?
Also another thing, is there way to force maya version to use if you have two installed, like 2019 and 2018, to force render to use version that you select?
It fails loading on every version bellow that even tho on GUI it loads fine and render.
This is probably concurring because you have Strict error checking on in the Job Setting/Properties, so the errors that would normally be really bad, like a maya version mismatch , may actually be ok for what your doing. Most likely, even though it loads in the maya gui, there are most likely a pile of errors thrown in the script editor, the strict error checking is most likely failing on these.
with this off/ False, your render should in theory work, but may have other unintended side effects.
As for the Maya version, you should be able to force it when you submit the job to the farm.
though, the version needs to match with one that exists in your plugin’s settings, so by default there will be a version for every maya version that was available at the time of the deadline release, thou it is possible for you to add newer versions, to the .params / .options file of the given plugin.
