AnsweredAssumed Answered

animation render output missing

Question asked by Ernie Eaton on Jan 25, 2020
Latest reply on Jan 26, 2020 by Ernie Eaton

Any help with this would be appreciated. 

 

I'm attempting to render an animation in 360 mp4 4096x2048 fast, no denoiser, 50 passes. I can see it producing the individual frame TIF image files. When the process completes the folder with images is gone and there is no movie file either.  The animation is about 40 seconds long, 30FPS.  I was able to successfully render a 110 frame section of the same animation.  I am running Visualize Professional 2019 SP 2  27.2.0.51 with a student license on an i7 w/16GB ram, GeForce GTX 1080 Ti w/11GB. 

 

The model has about 8100 components but it doesn't seem to be an issue with part count because all the frame images seem to render.

 

If I choose "send to queue" the queue window shows the  render progress and then shows the job complete/"green". While the job is in process I can find the output folder and images files in sub folders under C:\ProgramData\SOLIDWORKS\SOLIDWORKS Visualize 2019\Queue..   These files disappear as well when the job completes, they are not moved to the default output folder username\Solidworks Visualize Content\Images.  There is 60+GB free on the C drive at the point the image render portion of the job is nearly done.  I think I've tried unchecking the make video option with similar results. Similar results when not sending it to the queue. 

 

a "preview" render of the same animation was successful. the mp4 file is 145MB. the TIF file folder is 9.7GB with 1198 TIF files---- UPDATE- this was a perspective not 360 render. Also successful was a fast, perspective, slightly shorter (1037 frames) 1920x1080 2.9GB of TIF, 22MB mp4 . 

 

I watched carefully the end of another render. This one rendered accurate 50 passes, also 360, 4096x2048, directed to a folder on the F drive. After all the frames had been rendered to tif files using the name I had specified it started making copies of each tif file in the same folder. These were named tempMovieProject_xxxx.tif. When that step completed a tempMovieProject.mp4 file was created, also within the folder I had specified.  The system ground for a few minutes then the File Explorer window I had open viewing the folder changed to viewing F:\ and my output folder was gone. 

 

These are the last few entries in the OfflineRenderer.log file from a job run without using "send to queue".  For this render I had selected to output to a folder "temp visualize render folder" I had already created  on my F: drive (265GB free).  After completion the folder was gone. During the render I could see TIF files being placed there. 

 

348834 INFO  Rendering Thread Manage.CommonRenderingExecutor: Rendering Progress: 99.96996%
29366119 INFO  Rendering Thread Manage.CommonRenderingExecutor: Rendering Progress: 100.0017%
29931695 INFO  Rendering Thread       Manage.RenderingExecutor: DoRenderWork() returned

                              filename: F:\temp visualize render folder
29933092 INFO  Rendering Thread       Manage.RenderingExecutor: SaveOutput() returned filename:

                       F:\temp visualize render folder\Body Assembly 20200106_RECOVERED_1b.mp4

 

 

OfflineRenderer - iray.log

[29321.0] IRT:RENDER   1.0   IRT    rend info : Scene graph manager init took 0.000178 seconds
[29321.0] IRT:RENDER   1.0   IRT    rend info : Material update took 0.000000 seconds
[29321.0] IRT:RENDER   1.0   IRT    rend info : Decal update took 0.000012 seconds
[29321.0] IRT:RENDER   1.0   IRT    rend info : Projector update took 0.000001 seconds
[29321.0] IRT:RENDER   1.0   IRT    rend info : Lights update took 0.000002 seconds
[29321.0] IRT:RENDER   1.0   IRT    rend info : Geometry update took 0.000003 seconds
[29321.0] IRT:RENDER   1.0   IRT    rend info : Top group update took 0.000000 seconds
[29321.0] IRT:RENDER   1.0   IRT    rend info : Light profiles update took 0.000001 seconds
[29321.0] IRT:RENDER   1.0   IRT    rend info : Scene update took 0.002934 seconds
[29321.0] IRT:RENDER   1.0   IRT    rend info : Environment update took 0.000044 seconds
[29322.0] IRT:RENDER   1.0   IRT    rend info : rendered frame 0001 in 0.997376s, 1.0fps (internal: 0.947593s, 1.1fps, overhead 5.0%)
[29322.0] IRT:RENDER   1.0   IRT    rend info : Scene graph manager init took 0.000019 seconds
[29323.9] IRT:RENDER   1.0   IRT    rend info : rendered frame 0003 in 1.849345s, 0.5fps (internal: 1.803812s, 0.6fps, overhead 2.5%)
[29323.9] IRT:RENDER   1.0   IRT    rend info : Scene graph manager init took 0.000020 seconds
[29327.5] IRT:RENDER   1.0   IRT    rend info : rendered frame 0007 in 3.635723s, 0.3fps (internal: 3.590851s, 0.3fps, overhead 1.2%)
[29327.5] IRT:RENDER   1.0   IRT    rend info : Scene graph manager init took 0.000021 seconds
[29334.7] IRT:RENDER   1.0   IRT    rend info : rendered frame 0015 in 7.165633s, 0.1fps (internal: 7.121774s, 0.1fps, overhead 0.6%)
[29334.7] IRT:RENDER   1.0   IRT    rend info : Scene graph manager init took 0.000022 seconds
[29349.1] IRT:RENDER   1.0   IRT    rend info : rendered frame 0031 in 14.467463s, 0.1fps (internal: 14.419911s, 0.1fps, overhead 0.3%)
[29349.1] IRT:RENDER   1.0   IRT    rend info : Scene graph manager init took 0.000020 seconds
[29366.4] IRT:RENDER   1.0   IRT    rend info : rendered frame 0050 in 17.283289s, 0.1fps (internal: 17.233459s, 0.1fps, overhead 0.3%)
[29932.0] API:DATABASE   1.0   API    db   warn : Transaction is released without being committed or aborted. Automatically aborting.
[29932.0] IRT:RENDER   1.0   IRT    rend info : Shutting down irt render context.

 

Outcomes