Thanks Mike, I’ll check this out. We’re in the middle of production now so I can’t update Deadline but I’ll sub in that py file and see what happens.
Unfortunately the patch didn’t work.
It’s not the raw vray image file but an exr rendered from the vray raw image option, hope that makes sense.
I watched the render slave’s temp directory and there was a file “VRayLocalOutput_temph8NDR0” with no extension, about the size of a vray raw image file, being placed in this directory
C:/Users/render.CICADA/AppData/Local/Thinkbox/Deadline8/slave/sm1524a/jobsData/58137576e5fe46306c4b5934/But deadline seems to be looking for a this file(s04-02_.0000.exr) in this directory
C:/Users/render.CICADA/AppData/Local/Thinkbox/Deadline8/slave/sm1524a/jobsData/58137576e5fe46306c4b5934/VRayLocalOutput_temph8NDR0The correct out put should be s04-02_.0000.exr so it seems like Deadline is looking in the right spot, its the temp rendering file not being saved in the right directory or possibly to the right file.
Here is the job log.
Job_2016-10-28_13-36-57_58138cb9167ef7042455f35a.txt (77.8 KB)
ok, thanks for all the notes. I can see exactly where it is going wrong. However, I have never seen this before and I’m also confused as to how you could ever have got yourself into this situation. Let me explain. In your log report for the first frame, all the V-Ray renderer maxscript properties are applied, which are captured at job submission time by SMTD. This tells me that you submitted via our SMTD system. However, several important maxscript properties are completely missing, not just post-job-submission changed or edited, but actually missing. For example:
the first line above is present, but the 2nd line which V-Ray internally then knows where to save the RAW exr file to is completely missing. At submission time, if going through SMTD, if “Sanity Check” had fired, it would have picked up that the RAW was set to save, yet the file path is missing and it would flag this as a fatal issue. Now, I can understand that perhaps Sanity Check was skipped, but I can’t understand how some random V-Ray maxscript properties are just straight up missing. We have a checkbox to control the export of these maxscript props, but it is either on or off, and if it was off, NO maxscript props would have been exported. There is some proper voodoo going on here. In fact, just rendering locally, with save RAW enabled in V-Ray VFB but no valid file path entered, V-Ray itself will raise the error and display a pop-up dialog telling you so.
Later on in your log, you can see where we fire an internal script in our 3dsmax.py plugin to control the setting of the RAW file path + name. Note, now it is missing a fileName+Extension right at the end:
re:
So…, just to clarify things here, before I run away for the weekend, here is an attached image, showing what I am referring to as the V-Ray VFB based RAW image file setting and where normally you would enter a valid file path, filename and extension. In my example, it is empty.
All I can think of as a random guess here, is your submitting using a custom submitter (ie: not SMTD), a really old version of SMTD or a studio custom submitter, which is removing some renderer maxscript properties at either submission time or post submission out of the Deadline job object.
Sorry, but I’m going to need some help understanding how you even got into this situation! Hopefully, I’ve just missed something obvious!
yes, that’s correct.
There is something weird going on for sure because I can’t see the lines vray_output_saveRawFile=true in the job log I just posted, maybe something went wrong in the upload so I’m just reattaching the job log, job plugin info and job info.
In the job plugin info file I can see the lines you were referring to (lines 343,344), and they seem fine.
I’m not really sure about this. I don’t even know how this is set, i’m guessing this is inside the 3dsmax.py
2016-10-28 13:31:58: 0: INFO: Executing script: C:/Users/render.CICADA/AppData/Local/Thinkbox/Deadline8/slave/sm1524a/jobsData/58137576e5fe46306c4b5934/VRayLocalOutput_temph8NDR0\setRawBufferFilename.ms
2016-10-28 13:32:08: 0: INFO: RawBufferFilename set to: C:/Users/render.CICADA/AppData/Local/Thinkbox/Deadline8/slave/sm1524a/jobsData/58137576e5fe46306c4b5934/VRayLocalOutput_temph8NDR0
We are using a custom script to submit the jobs but there are no weird callbacks or render path manipulations. Here is the part of the script that submits the job
[code]
myrend.output_on=true
myrend.output_useram = true
myrend.output_saverawfile = true
myrend.output_splitgbuffer = false
myrend.output_saveFile = false
myrend.output_splitRGB = false
myrend.output_splitAlpha = false
myrend.output_splitfilename = “”
myrend.output_force32bit_3dsmax_vfb = true
myrend.fileName_addDot = true
myrend.output_rawfilename = rootnode.CA_frameOutput +“\” + currCam + “\” + rootnode.CA_passDirectory + “\” + currCam + “_” rootnode.CA_extension
rendSaveFile = true
myrend.adv_irradmap_mode = 2
myrend.lightcache_mode = 2
myrend.options_dontRenderImage = false
rendFieldRender = false
rendShowVFB = false
rendSaveFile = false
rendTimeType = 2
rendNThFrame = rootnode.CA_FRNthFrame
makedir (rootnode.CA_frameOutput + currCam +“\”+ rootnode.CA_passDirectory)
SMTDSettings.JobName = “02.Fr___” + rootnode.CA_jobPrefix + “___” + currCam
SMTDSettings.Comment = “Scripted FR Job”
SMTDSettings.Priority = rootnode.CA_Priority
SMTDSettings.ChunkSize = 1
SMTDSettings.LimitEnabled = false
SMTDSettings.MachineLimit = 0
SMTDSettings.SlavesBlackList = true
SMTDSettings.SlavesList = #()
SMTDSettings.SubmitAsSuspended = false
SMTDSettings.LimitGroups = #()
SMTDSettings.LimitGroupsToUse= #()
SMTDSettings.group = “frames”
SMTDSettings.SequentialJob = false
SMTDSettings.JobIsInterruptible = false
SMTDSettings.RestartRenderer = false
SMTDSettings.purifyFilenames = true
SMTDSettings.IgnoreMissingXREFs = false
SMTDSettings.SubmitAsDependent = true
SMTDSettings.DependOnPreviousJobMode = #last
SMTDSettings.DependencyJobItems = #{1}
local batchName = getProjectName()
SMTDFunctions.SubmitJobFromUI batchName:batchName forceCamera:currCam
SMTDSettings.group = “none”[/code]
Something I forgot to mention is that the same job renders fine if the Local Render is turned off.
ErrorEXRJob.zip (14.7 KB)
Edit: I started checking logs for all the job we submitted and the line with the “setRawBufferFilename.ms” doesn’t seem to appear on all the jobs even though all the jobs are set to Local Render by default. When it does appear, sometimes it appears at the beginning of the log and sometimes half way through, not sure if that matters either.
Hi,
Alrighty, that was a bit of a mission. So, looks like a regression on our part and the confusing part…? The code was actually correct, but V-Ray maxscript properties are not consistent in their camelCase naming consistency and the V-Ray “rawFileName” is actually: “rawfilename”, which stopped the RAW filename from being set, which then broke it later on during rendering. The same camelCase or “lowercase” as it should be; error was present in various other places, whcih explains why it wasn’t visible when the customize.ms properties are set in your log, etc. Anyhow, fixed now and here’s a quick patch if you want to self-heal yourself or wait for it to be released in a future release. Unzip the attached file and overwrite the same named files in your repository with these files in their applicable directories. Again…sorry about this.
Hi,
Got the same error, with last beta version. Can I use this patch too ?
Thx
No, as 8.1 code is quite different. This is why I sent you through your support ticket a 8.1 version of this fix last night. Did you not get it?
Thanks Mike,
that did the trick.
Bugs happen in any software, so far you guys have been the only ones in our pipeline who reliably fix them. 
So from what I’m understanding is version 8.1 will have this fixed but not necessarily using this patch? Do you know roughly when that version will be available, just want to time that update with our production schedule.
Great! I’m glad it’s fixed. I’ve already taken myself to one side and had a ‘chat’ with myself on this little escapade already today. 
The above attached patch zip file is specifically for anyone on 8.0 to fix themselves. I have asked for this fix to be merged into the next 8.0 service pack and also merged later on into the current 8.1 code branch as well (for the next 8.1 beta release as well), so you shouldn’t be ‘tied’ to when is 8.1 released as this is a bug and bugs need fixing sooner for our customers! 
Hi Mike,
Nope didn’t get it 
Can you send me the fix again ?
Thanks
@Matt - re-sent just now via the same OS ticket as before.
Ok thanks but still nothing :S