I see that in beta13 “ReRenderOutput” was renamed to “RenderElementOutputFilename”.
How does that affect existing jobs? There are quite a few jobs active in the queue with ReRenderOutput in the plugin info settings. Also, we have countless “ready to go” right eye renders for stereo jobs that can be submitted via a batch file, where the job/plugin info file was pregenerated weeks/months ago, all using ReRenderOutput in the info file…
I have no idea where the ReRenderOutput came from, because it used to be “RenderElementOutputFilename” for many many years. At some point, both names appeared in the SMTD code, but the “RenderElementOutputFilename” was removed from the 3dsmax.py, thus breaking most of the tile/region rendering.
I think you could modify 3dsmax.py to check which one exists and use the one you can find to set the respective value in Lightning. The change is really only on the script side and does not affect the internals, so I hope such a modification will allow your existing jobs to pass through the queue.
Look around line 1416 for
[code] reFilenameIndex = 0
reFilename = self.Plugin.GetPluginInfoEntryWithDefault( “RenderElementOutputFilename” + str(reFilenameIndex), “” )
while reFilename != “”:
reFilename = RepositoryUtils.CheckPathMapping( reFilename ).replace( “/”, “\” )
self.MaxSocket.Send( "OutputImageReFilename,%d,%s" % (reFilenameIndex,reFilename.replace( "\\", "/" )) )[/code]
and add some handling to use “ReRenderOutput” if it exists and “RenderElementOutputFilename” doesn’t.
Sorry for the mess, but it had to be unified under one consistent name for both tiles and regions and the “RenderElementOutputFilename” has been the original name ever since we added Tile Rendering in 2006 (although the earliest SVN record Blame shows is build 30627 from 2008 
).
Give me a ring if you want to shout at someone 
Hehehe, Ill send Beni over to take revenge on your living room 
Oh noes!
