07-27-2005, 05:11 AM
Is this only when rendering multiple frames or for single frames as well?
This looks like the same type of error we used to get when rendering multiple frames
with the Final Render renderer back before the issue was addressed.
One fix then was to disable the "Multi-threading" selector in the your Max preferences.
There was some sort of conflict with how DS and FR handled their multi-threading.
Could be the same type of thing with Brazil, though I haven't heard of it before.
If you're still having a problem with it, try writing support at turbosquid,
they may have some more information for you.
Posting here is good too.
This looks like the same type of error we used to get when rendering multiple frames
with the Final Render renderer back before the issue was addressed.
One fix then was to disable the "Multi-threading" selector in the your Max preferences.
There was some sort of conflict with how DS and FR handled their multi-threading.
Could be the same type of thing with Brazil, though I haven't heard of it before.
If you're still having a problem with it, try writing support at turbosquid,
they may have some more information for you.
Posting here is good too.