vrqy for maya... yet again

Hi I found a problem with the vray frame buffer in vray for maya. When the use vray frame buffer attribute is on in the scene, when rendering with the maya batch plugin I get this strange error:

[code]0: WARNING: Detected popup dialog “Render history settings”.
0: WARNING: ---- dump of dialog ----
0: WARNING: Button: …
0: WARNING: Static: VFB history temp path:
0: WARNING: Edit:
0: WARNING: Static: Maximum size on disk (MB):
0: WARNING: Edit:
0: WARNING: Button: OK
0: WARNING: ---- end dump of dialog ----
Scheduler Thread - Render Thread 0 threw an error:
Scheduler Thread - Exception during render: An error occurred in RenderTasks(): Dialog popup detected: Title “Render history settings”, Message “Maximum size on disk (MB):” (Deadline.Plugins.ScriptPlugin+FailRenderException) (Deadline.Plugins.RenderPluginException)

at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String& outMessage)

Exception Details

RenderPluginException – Exception during render: An error occurred in RenderTasks(): Dialog popup detected: Title “Render history settings”, Message “Maximum size on disk (MB):” (Deadline.Plugins.ScriptPlugin+FailRenderException) (Deadline.Plugins.RenderPluginException)

at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String& outMessage)

RenderPluginException.Cause: JobError (2)

Exception.Data: ( )

Exception.TargetSite: Void RenderTask(Int32, Int32)

Exception.Source: deadline

Exception.StackTrace:

at Deadline.Plugins.Plugin.RenderTask(Int32 startFrame, Int32 endFrame)

at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask()

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[/code]

So I forced the attribute to off in the plugin, I modified the GetStartFrameCommand() function to add the vfbOn attribute to off:

def GetStartFrameCommand( self ): [...] elif self.Renderer == "vray": return 'setAttr "vraySettings.startFrame" ' + self.StartFrame + '; setAttr "vraySettings.animation" true;setAttr "vraySettings.vfbOn" 0;' [...] return ''

As always, thanks for the info! We’ll include this in the next release as well.

In 3dsmax, we ran into the same problem, and we’ve been forcing the vray vfb off for a while now. Didn’t even think to check this in Maya. :slight_smile:

Cheers,

  • Ryan