Hi all,
I believe that I figured out the exact problem.
We sometimes use pre calculated uhd for our animations. It seems like anytime there is a path in the UHD cache filename, the error is generated.
Just empty that field and it should work again.
I’ll report that to the support and hopefully there is a fix soon.
Please let me know if this works for you too.
Chris
Hello,
Thanks, I will try.
I think all the scenes I had problems with were animations with the precomputed cache.
I hope there will be a fix soon since it’s not an option to render these animations without the cache.
10.1.16.9 seems to work. No error messages until now.
Lately, I also have had problems with Vexus submitting jobs to Deadline. Not the right view/camera is rendered despite that in the job option, the camera is correct, but it might be a Vexus submitter problem.
Yes, it seems if the default path for the UDH cache is removed a submitted file from the Max submitter will render. Even for a still where no UHD cache is used.
Can anyone test switching the uhd cache to discard, then back to the correct setting before sending? (I’m not near my test repo)
I’ve had this problem before with an earlier version of Deadline and Corona
Hello @squeakybadger @johan_belmans @Benjamin_Foldi @christopheC @mois.moshev @kehrmaschine @anthonygelatka @alexyork @Frodo
customize.zip (42.2 KB)
customize.tar (210.5 KB)
I’m attaching a file here please backup and replace the customise.ms in [Repo]/plugins/3dsmax/customise.ms
You should be good to go.
FWIW: In the max script we were trying to execute a file path which is why it was breaking.
Thanks zainali
This does indeed fix the issue.
Looks like it works for me as well 
