Hi guys,
I recently made the descision to take the plunge iv always wanted to from motion gfx in to vfx and im currently working on my debut vfx reel. Unfortunately iv run in to a problem with rendering out of maya and I was wondering if anyone here could help me out.
Im fairly sure I have set up the render globals correctly for animation (using mentalray) and when i set off a batch render, the prompt in the bottom right says firstly that mentalray is rendering then a few seconds later it says that rendering is completed, and there is no output, no rendered frames.
Iv tried rendering out to different file formats with no luck. Single frames render perfectly. Iv tried importing my scene into a fresh file and rendering with no luck. Iv tried creating a new scene with very simple animation, again, no luck. Iv tried rendering my scene with maya software which does work. So i think its a mentalray problem. When I looked at the renderLog I saw a few error msgs but dont realy know what they mean or more importantly, how to put them right!
Here is the renderLog:
Starting "C:\Program Files\Autodesk\Maya2009\bin\mayabatch.exe"
mental ray for Maya 10.0
mental ray: version 3.7.1.27, Jan 26 2009, revision 30548
File read in 0 seconds.
Result: C:/Documents and Settings/RenderNode/Desktop/Main folder/Showreel intro/showreelIntro/scenes/showreelIntro04__156.mb
mental ray: got 8 satellite CPUs.
Prog: (Mayatomr.Scene) : optimize animation detection: done 8 animated nodes
MI 0.0 error 121002: failed to open /usr/include/mi/mayahair.mi for reading, The system cannot find the path specified.Info: (mental ray) : number of render thread(s): 4
MEM 0.0 info : heap size limit set to 2301 MB
// mental ray for Maya: using rayhosts file C:/Documents and Settings/RenderNode/My Documents/maya//maya.rayhosts
Info: (mental ray) : adding rayhosts
Info: (mental ray) : adding host: 192.168.1.72:7109
MSG 0.0 debug: mi_msg_add_host adding host 192.168.1.72:7109, socket -1
MSG 0.0 info : adding new host 1 (192.168.1.72:7109)
MSG 0.0 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 0.0 debug: WIN_NT: setting thread to default socket operation
MSG 0.0 error 011329: mi-ray/tcp: not a service (check %SystemRoot%\system32\drivers\etc\services)
MSG 0.0 warn 012219: using fallback inet service 7003
MSG 0.0 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 0.0 debug: WIN_NT: setting thread to default socket operation
MSG 0.0 debug: remote capabilities |RAY37|SUB1
MSG 0.0 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 0.0 debug: WIN_NT: setting thread to default socket operation
LINK 0.0 debug: broadcasting filename architectural.dll of module #1
LINK 0.0 debug: broadcasting filename base.dll of module #2
LINK 0.0 debug: broadcasting filename contour.dll of module #3
LINK 0.0 debug: broadcasting filename paint.dll of module #4
LINK 0.0 debug: broadcasting filename physics.dll of module #5
LINK 0.0 debug: broadcasting filename production.dll of module #6Info: (mental ray) : adding host: 192.168.1.73:7109
LINK 0.0 debug: broadcasting filename subsurface.dll of module #7
LINK 0.0 debug: broadcasting filename surfaceSampler.dll of module #8
LINK 0.0 debug: broadcasting filename architectural.so of module #9
LINK 0.0 debug: broadcasting filename paint.so of module #10
LINK 0.0 debug: broadcasting filename subsurface.so of module #11
LINK 0.0 debug: broadcasting filename mayabase.dll of module #12
LINK 0.0 debug: broadcasting filename AdskShaderSDK.dll of module #13
LINK 0.0 debug: broadcasting filename mayahair.dll of module #14
JOB 0.0 info : started threads 0,1,2,3 on 192.168.1.72:7109 now known as host 1
MSG 0.0 debug: mi_msg_add_host adding host 192.168.1.73:7109, socket -1
MSG 0.0 info : adding new host 2 (192.168.1.73:7109)
MSG 0.0 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 0.0 debug: WIN_NT: setting thread to default socket operation
MSG 0.0 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 0.0 debug: WIN_NT: setting thread to default socket operation
MSG 1.3 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 1.3 debug: thread 3 running
MSG 1.3 debug: thread padding address 020A1F50 size 57344
MSG 1.3 debug: starting thread
JOB 1.3 debug: starting new thread
MSG 0.0 debug: remote capabilities |RAY37|SUB1
MSG 0.0 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 0.0 debug: WIN_NT: setting thread to default socket operation
LINK 0.0 debug: broadcasting filename architectural.dll of module #1
LINK 0.0 debug: broadcasting filename base.dll of module #2
LINK 0.0 debug: broadcasting filename contour.dll of module #3
LINK 0.0 debug: broadcasting filename paint.dll of module #4
LINK 0.0 debug: broadcasting filename physics.dll of module #5
LINK 0.0 debug: broadcasting filename production.dll of module #6Info: (mental ray) : adding host: 192.168.1.50:7109
LINK 0.0 debug: broadcasting filename subsurface.dll of module #7
LINK 0.0 debug: broadcasting filename surfaceSampler.dll of module #8
LINK 0.0 debug: broadcasting filename architectural.so of module #9
LINK 0.0 debug: broadcasting filename paint.so of module #10
LINK 0.0 debug: broadcasting filename subsurface.so of module #11
LINK 0.0 debug: broadcasting filename mayabase.dll of module #12
LINK 0.0 debug: broadcasting filename AdskShaderSDK.dll of module #13
LINK 0.0 debug: broadcasting filename mayahair.dll of module #14
JOB 0.0 info : started threads 0,1,2,3 on 192.168.1.73:7109 now known as host 2
MSG 0.0 debug: mi_msg_add_host adding host 192.168.1.50:7109, socket -1
MSG 0.0 info : adding new host 3 (192.168.1.50:7109)
MSG 0.0 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 0.0 debug: WIN_NT: setting thread to default socket operation
MSG 0.0 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 0.0 debug: WIN_NT: setting thread to default socket operation
MSG 2.3 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 2.3 debug: thread 3 running
MSG 2.3 debug: thread padding address 020A1F50 size 57344
MSG 2.3 debug: starting thread
JOB 2.3 debug: starting new thread
MSG 0.0 debug: remote capabilities |RAY37|SUB1
MSG 0.0 debug: WIN_NT: setting thread to non-overlapped socket operation
MSG 0.0 debug: WIN_NT: setting thread to default socket operation
LINK 0.0 debug: broadcasting filename architectural.dll of module #1
LINK 0.0 debug: broadcasting filename base.dll of module #2
LINK 0.0 debug: broadcasting filename contour.dll of module #3
LINK 0.0 debug: broadcasting filename paint.dll of module #4
LINK 0.0 debug: broadcasting filename physics.dll of module #5Info: (mental ray) : network rendering slaves: 192.168.1.72:7109 192.168.1.73:7109 192.168.1.50:7109
LINK 0.0 debug: broadcasting filename production.dll of module #6
Error: (Mayatomr) : mental ray init failed, can’t start render
LINK 0.0 debug: broadcasting filename subsurface.dll of module #7Warning: (Mayatomr) : mental ray has reported severe errors, see the log
LINK 0.0 debug: broadcasting filename surfaceSampler.dll of module #8
LINK 0.0 debug: broadcasting filename architectural.so of module #9Error: Scene C:/Documents and Settings/RenderNode/Desktop/Main folder/Showreel intro/showreelIntro/scenes/showreelIntro04__156.mb failed to render.
LINK 0.0 debug: broadcasting filename paint.so of module #10
LINK 0.0 debug: broadcasting filename subsurface.so of module #11
LINK 0.0 debug: broadcasting filename mayabase.dll of module #12
LINK 0.0 debug: broadcasting filename AdskShaderSDK.dll of module #13
LINK 0.0 debug: broadcasting filename mayahair.dll of module #14
JOB 0.0 info : started threads 0,1,2,3 on 192.168.1.50:7109 now known as host 3
// Maya exited with status 210
I have a small render farm but the problem still exists even rendering without rendering over a network. The whole setup was working perfectly when i last used it, that was a few months back but nothing should have changed. Im puzzled, just like this little blue man :confused:
Any help, suggestions or pointers would be realy great cos iv just about run out of ideas.
Thanks
Adam