View Full Version : Maya exited with status 210
rhythmone 03-29-2007, 06:55 AM I am on OSX 10.4 trying to render via command line and -preRender
Can someone help me out?
Render -im occlusion -rl cur_Rlyr -preRender "/Users/.../maya/scripts/...rendPrepPass_occlusion.mel" -cam persp -s 1 -e 1 -b 1 -x 640 -y 480 -pad 4 -rd $rendPath $filePath
.... and get
Error: }
Error: Syntax error
Error: Scene /Users/..../scn/fish1_refs.ma failed to render.
// Maya exited with status 210
| |
rhythmone
03-29-2007, 03:27 PM
And just to clarify... I believe that I have tried many troubleshooting combinations...
The proc runs fine when executed from within Maya
I have tried "source path/to/file; proc"
I have tried "source path/to/file" and have the execution call after the proc like:
global proc rendPass () {
bla;
bla;
}
rendPass;
.... I have tried in both TCSH and BASH... and at this point I have emptied the proc just to try and call it without error.
global proc rendPass () {
}
rhythmone
03-30-2007, 01:38 AM
ALLRIGHT!!! For any of you other poor souls who have come across this...
So I am using BBedit to write mel... and it saves line breaks in UNIX.... well the command line doesn't like this... (which sucks cause Maya was reason why I had to set my BBedit preferences to UNIX)... So I opened up TextEdit and saved out a parser:
global proc simpleStupidParser (string $mel) {
eval $mel;
}
... and now everything works...
... you don't have to source it.
.... you don't have to quote it.
.... you don't have to escape \char\acter it..... NOTHING.... now hopefully I can get on with my life.
llikethat
06-26-2007, 10:11 AM
Hi!
I'm one among those poor souls.. i'm getting the same error. Could you please explain me in detail how you are executing your script. And why this problem is occuring.
Thanks,
rhythmone
06-26-2007, 08:06 PM
Hi
I was able to resolve this by using TextEdit to create a generic parser script... I believe that textEdit writes its linebreaks in a manner that is more command line friendly (although I am sure if you knew the line break format you could set up any editor to use it, I just didn't want to change my bbedit format cause it will break some of my mel line breaks)
Anyway, I just created this
global proc rendPrepPass_parser (string $mel) {
// THIS FILE IS FOR CMD LINE ACCESS ONLY
// LINE BREAKS FROM BBedit ARE NOT WORKING IN SHELL
evalEcho $mel;
}
Then from the shell script:
#***********************************************************************
pass="occlusion"
passScript="rendPrepPass_${pass}"
rPass="string\$curChar=\"${char}\";${rendPass}(\"${passScript}\")"
Render -im $pass -preRender $rPass -proj $projPath -of $format -fnc 2 -cam $cam -x $dimenX -y $dimenY -pad 4 -rd $rendPath $filePath
It appears that you cannot put ANY spaces in the preRender value, I tried escape characters, double quotes, etc.. and could never get it to work, so now if I have to pass in a list, I use commas to separate th values.
I know, lame, but now everything is working great so until I understand all the different line break insanity...
One Other thing - I just bought a new MacBookPro and noticed that the default shell is BASH again, not sure why Apple keeps switching back and fourth.... all I could ever really get to work was BASH though
llikethat
06-27-2007, 06:15 AM
Hi!
I'm really sorry.. i couldn't understand the shell script and the proceedure too... I'm still trying to understand how to use the mel parser also.
In my case, i want use a script to change the absolute paths inside a maya scene to relative paths. Then call the script using the -preRender flag and render the scene. This is the command i used...
C:\>render -r sw -s 1 -e 1 -preRender "D:\....\....\mel\furExpressionRelative.mel" D:\....\.....\scenes\whatafile.mb
The script i use is as follows...
string $expressions[]=`lsType expression`;
string $del[]={"<done>",""};
$expressions=stringArrayRemove($del, $expressions);
string $FurDescriptions[]=`lsType FurDescription`;
$FurDescriptions=stringArrayRemove($del, $FurDescriptions);
for($exp in $expressions)
{
string $checks[]=`listConnections $exp`;
for ($ch in $checks)
{
for ($Fur in $FurDescriptions)
{
if ($ch==$Fur)
{
select $exp;
string $a=`expression -q -s $exp`;
string $buffer[];
$numTokens =`tokenize $a "\"" $buffer`;
$regularExpr =$buffer[($numTokens-2)];
string $p=`substitute ".*:.*/.*fur" $regularExpr "fur/fur"`;
string $v=$buffer[0]+"\""+$buffer[1]+"\""+$buffer[2]+"\""+$buffer[3]+"\""+$buffer[4]+"\""+$p+"\""+$buffer[6];
expression -e -s $v $exp;
select -cl;
}
}
}
}
Please tell me how do i use the -preRender flag here.
Thanks,
rhythmone
06-27-2007, 04:50 PM
Not sure if I can help you with this one... I was a proponent of relative paths but have sicne switched to using environmental variables instead. I did this for numerous reasons:
-Referencing a scene which itself contains a relative path, will try and resolve the relative path against the location of the parent scene, not the referenced scene... this was breaking everything for me.
-Env vars (paths) can also be set in the shell script prior to render
-Setting the paths prior to opening the scene is more efficient then having Maya try to resolved or reference a path that you are going to end up replacing anyway
rygoody
06-29-2007, 10:28 AM
So I got maya exited with status 210 as well. But I got it differently. Maya mental ray found the file just fine, rendered the entire thing just fine got to 100% just fine. But then the first error it gets is:
PHEN 0.2 error 051003: frame buffer 0 invalid cannot create file C:/etc/pic.exr [The operation completed succesfully]
Which then prints out another dozen lines which seem like it's completed normal. But comes to:
Error: Scene scene.mb failed to render.
// Maya exited with status 210
Anyone know whats going on here?
llikethat
06-29-2007, 10:34 AM
Try using a different file format. It looks like you are using .exr, try using iff or someother format and see if you are getting an error.
Regards,
rygoody
06-30-2007, 02:48 AM
Thanks for the advice. I tried used .hdr and it did save out the render. Although it still exited with status 210.
CGTalk Moderation
06-30-2007, 02:48 AM
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.
vBulletin v3.0.5, Copyright ©2000-2009, Jelsoft Enterprises Ltd.