rrJob - Render Log Files
Render Log files
|
|
Structure of the render log file
|
A |
++++++++++++++++++++++++ Log Start +++++++++++++++ DAYWALKER033 rrClient console L 8.0.beta2b rrVer8.0.alpha17 08.22 03:18.09 ... ... ... |
This part shows some information about the client the render range the executable used to render the scene file that was redered |
|
B |
++++++++++++ Environment Variables Job: +++++++++++++++++ ... ... ... ++++++++++++ Environment Variables Client: +++++++++++++++ ... ... ... ++++++++++++ Environment Variables Done +++++++++++++++++++ |
Some Environment variables with all kind of information about the job and the client. |
|
C |
call "\RRender6\render_apps\_setenv\win\Softimage.bat" ... ... ... |
Now the commands of the render config files are executed. Usually the first command is to call the global and render app specific setenv file. This setenv file sets the path to plugins, license servers, can define options, ... |
|
D |
++++++++++++++++++++++ START +++++++++++++++++++++++ C:\Program Files\Autodesk\Maya\bin\Maya scene start end params ... 15:33.14 rrMaya - SET: defaultRenderGlobals.imageFilePrefix = MyImageOutput 15:33.14 rrMaya - SET: defaultRenderGlobals.animation = True 15:33.14 rrMaya - SET: defaultRenderGlobals.modifyExtension = 0 ... ... ... 15:33.15 rrMaya : Scene load time: 0:00:07.125000 h:m:s.ms 15:33.15 rrMaya : Scene init done, starting to render... |
The render application is started with all required commandline parameters. Some render scripts will print what they change in the scene file before it starts to render. |
|
E |
15:33.23 rrMaya : Starting to render frame #1 ... 15:33.23 rrKSO - ---: C:/RR_localdata/renderout/A/3D/Maya/images/MUM_ANIM_MASTER1.1.exr ... SCEN 0.2 22 MB info : wallclock 0:00:00.00 for scene preprocessing RC 0.2 23 MB info : option: scanline off RC 0.2 23 MB info : option: trace on ... RC 0.2 36 MB info : wallclock 0:00:02.49 for rendering ... 15:33.27 rrMaya : Frame #1 done. Frame Time: 0:00:04.569000 h:m:s.ms 15:33.27 rrMaya : rrKSO Frame(s) done #1 ... 15:37.29 rrMaya : Render done |
Some RR render scripts report which frame they start to render. Then the renderer outputs some information. And at last the RR script reports the time a frame took to process. |
|
F |
++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++ Render Executable done ++++++++++++++++ ++++++++++++++ Royal Render checks the return code of the executable +++++ ++++++++++++++++++++++ 05.26 14:13.53 +++++++++++++++++++++++ ++++ Executable returned -1073741819 (0x ffffffffc0000005) as exit code for frame 65. ++++ Render crashed +++++++++++++++++++++++++++++++++++++++++++++++++ |
After the render application finished, the tool rrCheckexitcode checks for the returned error code of the application. If an application crashed, then it returns an error code. An application should never crash, it should always print an error message and exit. But as all applications have bugs, a crash can happen. Most of the time it is not possible to convert these error codes into actual error messages. You can try to take a look at Windows/Linux system error codes, but they probably won't help you. Note: It happens that the application rendered the frames successfully, but crashed afterward. For example while unloading a plugin or releasing memory. |
|
G |
Current time:08.17 15:37.37 Total processing time: 00:01.34 (this KSO segment) Max memory usage: 0.85GB (this KSO segment) Max memory usage: 0.85GB (all KSO segments) Max CPU usage: 2.3cores 29% (of 8 cores) (last KSO segment) Max CPU usage: 2.5cores 32% (of 8 cores) |
After all processes closes, the rrClient adds the current time and some other informations to the log file. |
|
H |
************************* LOCAL RENDER INFORMATION ************************* Total render files found: 7 (all KSO segments) Total render files found: 4 (this KSO segment) Files successful copied: 7 Files broken/not copied: 0 Total render files found (main pass only): 4 List of files: (C=copied R=successfully read X=Exr cropped F=image verify failed V=rrViewer cache created) 6 C R V: \Maya\images\MUM_ANIM_MASTER1.6.exr 7 C R V: \Maya\images\MUM_ANIM_MASTER1.7.exr 8 C R V: \Maya\images\MUM_ANIM_MASTER1.8.exr 9 C R V: \Maya\images\MUM_ANIM_MASTER1.9.exr |
If you have enabled local render out, then you can see which frames have been rendered during this frame segment. As well as if the frames have been valid (R=successfully read). And if the frame was copied (C) to the fileserver. If it was not copied, then it was usually a placeholder file which was created before the render started. |
|
I |
*********** CLIENT REPORTS DURING THIS RENDER ************** |
If the client has collected some information during render, then it will append the information at the end of the log file. It collects for example error messages that it has found in the log output. |
|
E - I |
" |
If you have enabled KSO (Keep Scene Open), the client might get a new segment to render. And it will output log sections E to I again for each segment. |
Find issues
- At first, you should check section H (* LOCAL RENDER INFORMATION *) for the files that have been rendered and copied.
- And section I (* CLIENT REPORTS DURING THIS RENDER *). If there are some error messages, you should always scroll up and re-check them in the surrounding content.
Perhaps there was more information about the error in the preceding/next lines. - The next would be the last lines of the render application (Before section F +++ Render Executable done ++).
Sometimes the applications report an error and close the application. During close they report some other default stuff, so you have to check at least the last 10 lines. - One important aspect can be the different times that are reported like
- Total Processing time. From Section A 08.22 03:18.09 to section G Current time:08.22 03:29.28, Total processing time: 00:01.34
- Scene processing time, section D Scene load time: 0:00:07.125000 h:m:s.ms
- Per Frame times, section E.
In this example you can see that the renderer took 2,5 seconds, but the total time was 4,5 seconds. So Maya took 2 seconds to export the frame. - Total Frame time including preprocessing of the render app (e.g. Maya) and the times of the renderer (e.g. Mray) Frame #1 done. Frame Time: 0:00:04.569000 h:m:s.ms
- Renderer times. wallclock 0:00:02.49 for rendering
- Application unload time. Compare the last time reported from the render script (In this example: 15:37.29 rrMaya) and the time reported after the render segment (Current time:08.17 15:37.37).
In this example the application took 8 seconds to close.