On 8/16/2015 3:47 AM, clipka wrote:
> Am 15.08.2015 um 19:54 schrieb Mike Horvath:
>> I would be willing to sacrifice render speed for stability. In my case
>> the parsing is what uses all the resources, and rendering only takes a
>> few minutes even at 8192x8192px. As an option of course.
>
> In that case use only one single render thread ("+wt1").
>

I turned on the +wt1 switch and the render crashed outright. I uploaded 
the dump to wherever they get sent to.

>
> Also, if you're using radiosity, that is also something that eats up
> memory that you might get away without, if you use UberPOV and its
> "no_cache" radiosity option; if you use this, UberPOV will not store
> /any/ radiosity-related data, which obviously increases render time but
> saves a lot of memory (plus it also trades various types of artifacts
> for random noise, wich can be reduced easily by simply throwing more
> render time at it in "+am3" mode).
>

Radiosity is turned off.


Mike

Post a reply to this message