Any rendering has the potential for something to go wrong. In our vast experience, it's usually a material, but often we have seen a "quirky model" downloaded from the 3D Warehouse as the culprit when a render fails. If you suspect it's a quirky model, simply exploding the model has often done the trick- often a problem model simply has too many nested groups and components. Exploding a Group that contains a group of groups and components, without exploding the individual components will often solve the problem.
If your rendering is still failing, and it's not due to some "quirky" 3D Warehouse model, then it's likely that your computer is running out of RAM.
If you are running out of RAM, it's likely due to one of two things - one or more textures in the model are of too high resolution, or there are too many lights.
There are two tools we developed for helping to pin-point problem spots in your scene. The Log File, and the Diagnostic Report tool.
For the Diagnostic Report dialog, go to Plugins>Twilight V2>Diagnostic Report.
Then choose either "All" or "Materials" for the type of Diagnostic Report you would like to receive.
For the Log File, start the log file before you render, then see what is written in the log file as you experience the problem while rendering.
to open the Log File, choose to do so in the Twilight V2 Options Dialog. For the Options Dialog, go to Plugins>Twilight V2>Options.
The Twilight Render Team shares tips, ideas, helpful hints, and more on using Twilight Render
1 post • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest