batchRenderMgr.outputFilename causing render failure with net render/backburner..

Become a member of the CGSociety

Connect, Share, and Learn with our Large Growing CG Art Community. It's Free!

THREAD CLOSED
 
Thread Tools Search this Thread Display Modes
Old 10 October 2012   #1
batchRenderMgr.outputFilename causing render failure with net render/backburner..

Hello,

I've has a search for this issue and couldn't find an answer. The over view of the task is that I'm scripting the creation of a series of batch render views, and setting animaiton frame, output filenames, aspect ratios etc.

When I am scripting the output file name for a batchrender 'view' using the batchRenderMgr interface, where I am using net render/backburner to submit the batch renders, backburner will return an error when the file is picked by a render machine.

The issue stems from the file extension. If you set the file extension to anything other than '.rpf' the net render will fail.

I tested this by setting the output file name like so:


outFileName  = nameVar + ".rpf"
batchRenderMgr.outputFilename  = outFileName 


which worked fine, so I then tried:


outFileName  = nameVar + ".jpg"
batchRenderMgr.outputFilename  = outFileName 


and the net render failed with the error (Backburner server log):

3dsmax adapter error : 3dsmax.exe process no response.


I then proceeded to test other extensions and got the same error. .. BUT if I manually go into the batch render dialog, and manually set the path and the name with the extension (any extension) it works fine - no error.

My next port of call was to try and use the super class for image extensions to set the file options as this is the only step that is different when you change the output file name manually, but this didn't work eg:

fileFormat = "jpg" -- this is actually set as a global local var elsewhere in the script, but for for the purposes of this example I'm putting it here

outputFileName = nameVar +  "." + fileFormat
if fileFormat == "jpg" then
(
   JPEG.ijpegio.setQuality 100
)
batchRenderMgr.outputFilename = outputFileName 


but still get the same error...

Has anyone else had a problem with this?
__________________
"Sonny..... did we just land or were we shot down?"

Last edited by CrazyDamo : 10 October 2012 at 05:54 AM.
 
Old 10 October 2012   #2
Also ...

help..
From what I can see there is no temporary work around for this either - I was thinking perhaps I could manually iterate through the list of views in the batch render manager, and submit the jobs individually with the correct output file name. I can successfully script the job submission to Back burner ....But the main reason we are thinking of using the Batch Render Manager was to utilize the scene states.
From what I can see you cannot assign the Scene State names to a render job through the maxscript netrender() interface ... which makes me wonder how Max does this when submitting via the Batch Render Manager?

Any suggestions would be much appreciated.

Cheers,
D.
__________________
"Sonny..... did we just land or were we shot down?"
 
Old 10 October 2012   #3
Aks a question then answer it....

hehehe so I think I found the answer to this and it didn't make me love Autodesk.

It seems that you have to create a bitmap in the directory you are saving to and then pass the file name of the instance of the bitmap to the #.outputfilename.....

Not only is this a bug in my mind, but it also applies to several other maxscript filename attributes/properties... I would hazard a guess all of them.

yes ladies and gentlemen.. the most retarded approach to scripting I have every seen.

SO, here is an example of what I'm talking about that applies to scripting vray's render element output filename (and the reason I found this solution) :


vr = renderers.current
vr.output_on = true
vr.output_splitgbuffer = true
--here is where the joy starts, setting the name of the path and filename
fileName = outputFilename + "." + extension
--now we create a temporary bitmap in that location
screwedBitmapCreation = Bitmap 10 10 fileName:fileName
--save it and close it
save screwedBitmapCreation
close screwedBitmapCreation
--now using the bitmap instance we parse the filename of the bitmap to the render attribute .......LAME!!
vr.output_splitfilename = screwedBitmapCreation.filename


Really disappointed by this.. but hey.. I'm just an art monkey, what do I know.

Cheers,
D.
__________________
"Sonny..... did we just land or were we shot down?"

Last edited by CrazyDamo : 10 October 2012 at 02:43 AM. Reason: bad gramma
 
Old 10 October 2012   #4
...NOT fixed...

ok... so it seems I was a tad eager in thinking this issue was resolved.

The above solution doesn't actually work.

The issue of having to press the "Browse" button in order to parse a legitimate file name to a render attribute is still very much alive.

I made the mistake of testing my script 'AFTER' I had used the 'browse' button.

After allot more testing its seems it doesn't matter what file you select, or what name you give it in the 'save dialog' window, as long as you commit a file name manually, you can then via script , change that name to anything and everything will render as it should.

If you don't do this manual process ... nothing works. I am at a complete loss - can anyone help?

Via script - I need two things:
1)I need to, per view, set a file name to the output of the batch render manager.
2) I need to, in a separate script, set a new output path for the split render channel via the Vray Frame buffer, per render submission (iterated via script).

Currently I can't do this via script unless I manually press buttons.. which is sooo crazy -

Is any one else having problems with file name selection in Max 2013 .. I haven't come across this yet with older versions (2008, 2010 etc)?
__________________
"Sonny..... did we just land or were we shot down?"
 
Old 10 October 2012   #5
Thread automatically closed

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
__________________
CGTalk Policy/Legalities
Note that as CGTalk Members, you agree to the terms and conditions of using this website.
 
Thread Closed share thread



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
CGSociety
Society of Digital Artists
www.cgsociety.org

Powered by vBulletin
Copyright 2000 - 2006,
Jelsoft Enterprises Ltd.
Minimize Ads
Forum Jump
Miscellaneous

All times are GMT. The time now is 08:12 PM.


Powered by vBulletin
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.