AWS Thinkbox Discussion Forums

9.0.0.16 Local rendering not working with V-Ray RT

Hi,

It seems that local rendering is not working with V-Ray RT. Though it’s enabled, the frames are saved to the network drive directly.

It’s saving to mapped drive. Can it have something to do with that ?

Also other explanation is that most of the V-Ray options accessible through the MaxScript have different a bit structure in RT compared to Adv and Deadline is not changing saving paths correctly. While in Adv all properties are right under renderers.production , in RT they are moved to renderers.production.V_Ray_Settings.

Best,
Tomasz

Thanks for the feedback. Have logged for further investigation. Could you provide a full 3dsmax log report so we can see what is happening here? Thanks.

Sure,

[code]=======================================================
Log

2017-03-06 15:09:54: 0: Executing plugin command of type ‘Sync Files for Job’
2017-03-06 15:09:54: 0: All job files are already synchronized
2017-03-06 15:09:55: 0: Plugin 3dsmax was already synchronized.
2017-03-06 15:09:55: 0: Done executing plugin command of type ‘Sync Files for Job’
2017-03-06 15:09:55: 0: Start Job timeout is disabled.
2017-03-06 15:09:55: 0: Task timeout is 2880 seconds (Auto Task Timeout)
2017-03-06 15:09:55: 0: Plugin rendering frame(s): 402
2017-03-06 15:09:55: 0: Executing plugin command of type ‘Render Task’
2017-03-06 15:09:55: 0: INFO: Render Tasks called
2017-03-06 15:09:55: 0: INFO: STARTED
2017-03-06 15:09:56: 0: INFO: MaxLightning: Render frame 402
2017-03-06 15:09:56: 0: INFO: MaxLightning: Overriding save file option to 0
2017-03-06 15:09:56: 0: INFO: MaxLightning: Rendering frame “C:\ProgramData\Thinkbox\deadline\temp\temp_filename100330402.bmp”
2017-03-06 15:09:56: 0: INFO: MaxLightning: Rendering 0 render elements
2017-03-06 15:09:56: 0: INFO: MaxLightning: Checking output paths
2017-03-06 15:09:56: 0: INFO: MaxLightning: Checking default actions
2017-03-06 15:09:56: 0: INFO: MaxLightning: TYPE_MISSING_EXTERNAL_FILES = IGNORE
2017-03-06 15:09:56: 0: INFO: MaxLightning: TYPE_MISSING_UVWS = IGNORE
2017-03-06 15:09:56: 0: INFO: MaxLightning: TYPE_MISSING_DLL_FILES = FAIL
2017-03-06 15:09:56: 0: INFO: MaxLightning: TYPE_MISSING_XREF_FILES = IGNORE
2017-03-06 15:09:56: 0: INFO: MaxLightning: Calling renderer
2017-03-06 15:09:56: 0: INFO: V-Ray starting rendering…
2017-03-06 15:09:58: 0: INFO: Building dynamic mesh trees: done [00:00:00.1]
2017-03-06 15:09:58: 0: INFO: Building BVH tree: done [00:00:00.0]
2017-03-06 15:10:24: 0: INFO: Building light cache…: done [00:00:21.7]
2017-03-06 15:10:25: 0: INFO: Merging light cache passes…: done [00:00:01.0]
2017-03-06 15:10:25: 0: INFO: Prefiltering light cache…: done [00:00:00.1]
2017-03-06 15:11:45: 0: INFO: Writing output
2017-03-06 15:11:46: 0: INFO: Writing output [00:00:01.4] [00:00:00.0 est]
2017-03-06 15:11:47: 0: INFO: Writing output [00:00:01.7] [00:00:08.6 est]
2017-03-06 15:11:47: 0: INFO: Writing output: done [00:00:01.7]
2017-03-06 15:11:47: 0: INFO: MaxLightning: CallCurRendererRenderFrame returned code 1
2017-03-06 15:11:47: 0: INFO: MaxLightning: Render done
2017-03-06 15:11:47: 0: INFO: MaxLightning: Checking render elements
2017-03-06 15:11:47: 0: Done executing plugin command of type ‘Render Task’
[/code]

This is what I get. Local rendering option is switched on - dabarti.com/screens/s833a801 … 9a4956.png .

Best,
Tomasz

Sorry, my bad. Could I see the log report from the first frame that a particular Slave picks up for this job, as it will contain considerably more info for me to go on here. Also, to confirm, did you submit via SMTD or the Deadline Monitor?

I’m submitting through SMTD.

I’ve attached the log.
Job_2017-03-06_16-22-53_58bd7ecaa2951044ccff730e.txt (70.6 KB)

FYI. OK, this is now fixed and should hopefully be available in the next build of D9.0. Local Rendering was not supported in V-Ray RT and was semi-broken in V-Ray “normal” rendering (ie: not region or tile rendering) when VFB enabled and RAW/split was being used. Thanks for the feedback.

Privacy | Site terms | Cookie preferences