The strange case of error 211005: timeout waiting for finished rectangles


In this case, Softimage 2010SP1 stopped rendering one day (but strangely, 7.5 and 2011 still worked). If you drew a render region, nothing would happen for a long time, and then you would get this error:

' ERROR : DISP 0.4  error  211005: timeout waiting for finished rectangles

If you tried to render a frame to file, you’d get the same error, and a truncated image file that couldn’t be read. The mental ray diagnostics looked like this:

' INFO : JOB  0.8  progr:    99.4%    rendered on Example.8
' INFO : JOB  0.9  progr:    99.7%    rendered on Example.9
' INFO : JOB  0.14 progr:   100.0%    rendered on Example.14
' ERROR : DISP 0.4  error  211005: timeout waiting for finished rectangles
' INFO : RC   0.4  info : rendering statistics
' INFO : RC   0.4  info :   type                           number   per eye ray
' INFO : RC   0.4  info :   eye rays                        32900          1.00
' INFO : PHEN 0.4  progr: calling output shaders
' INFO : PHEN 0.4  progr: Writing image file 'C:\Softimage\Softimage_2010_SP1\Data\XSI_SAMPLES\Render_Pictures\Default_Pass_Main.1.pic' (Channel 'Main').
' ERROR : DISP 0.4  error  211005: timeout waiting for finished rectangles
' INFO : RC   0.4  progr: rendering finished
' INFO : RC   0.4  info : wallclock  0:03:59.65 for rendering
' INFO : RC   0.4  info : allocated 17 MB, max resident 18 MB
' INFO : GAPM 0.4  info : triangle count (including retessellation) :         112
' ERROR : 21000-REND-RenderPasses - Unspecified failure
RenderPasses "Passes.Default_Pass", 1, 1, 1, siRenderVerbosityDefault
Command failed, returned -2147467259

Softimage would stop responding shortly afterwards.

Eventually we tracked this down to a conflict with the OGRE Exporter.
We removed the exporter, and Softimage 2010 SP1 was able to render again. We then reinstalled the OGRE addon, and Softimage 2010 SP1 still rendered.

I suspected some sort of application conflict all along, but it took awhile to find the root cause of the problem.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s