Is it possible to save a renders progress to return later?

[Scott762]

With some renders taking longer than I sleep, it would be nice to be able to pause a render, save it, then return to it later to resume. That way, for example I could render overnight then work on another project during the day then resume that render the next night.

[Zay]

I think that was one of the features for the upcoming Octane 3.

[glimpse]

not yet =) maybe in v3 (due to be released later this/next year =)

[Scott762]

Bummer. That would be nice to be introduced into version 3. I think I won't need that feature by then but who knows. I just got a 1000 watt power supply to prepare the system for a Titan X, with a 970 but with rendering times I may very well to get two!

[face_off]

If a render is taking that long - it sounds like you might need to check your settings. To minimise noise, 1) set Imager->hot_pixel to 0, increase Kernel->Caustic Blur, reduce Kernel->GI Clamp (to 1 if needed), use an IBL if possible, if interior then knock out some walls behind the camera to get more light in, use IES ditributions for emitters, etc, etc. Also, the number of polygons in the scene has a big impact on render time, so reducing the subd level can make a big difference.

Paul

[Scott762]

If a render is taking that long - it sounds like you might need to check your settings. To minimise noise, 1) set Imager->hot_pixel to 0, increase Kernel->Caustic Blur, reduce Kernel->GI Clamp (to 1 if needed), use an IBL if possible, if interior then knock out some walls behind the camera to get more light in, use IES ditributions for emitters, etc, etc. Also, the number of polygons in the scene has a big impact on render time, so reducing the subd level can make a big difference.

Paul

Thanks for the info Paul.

System: i7 2600K 3.8 GHz, Win 7 x64, 16 GB RAM, 2x EVGA GTX 970 superclocked.

I already typically use Caustic Blur at 1 to reduce fireflys. So I monkeyed with a scene I just finished rendering. Tried setting Imager->hot_pixel to 0 and Kernel->GI Clamp to 1, it made little difference (Using PMC, before I saw MSamples/Sec at 1.7-1.81, typically toward the 1.8). After it seems to stay at the 1.8-1.81. That's an open scene, lighted mostly by daylight with an emitter prop for fill power @ 1.5. Fairly large scene with 2 V4s with RedSpec SSS which have the most polys, but there's a large body of water and most materials are glossy, but with low specular (.02-.05).

I also will usually render pretty high resolution (2560x1440) to future-proof myself a bit, so I think it's mostly self inflicted.
1280x720 ~2:15, 1920x1080 ~6 hours, and 2560x1440 ~10 hours.



Off the top of my head, the scenes I'm rendering with PMC I'm typically getting 2 MSamples/Sec or so.

With the demo for the benchmark thread, I was getting using default settings:
SLI Disabled
PMC 6.8-6.9 MSamples/Sec
Path tracing 9.8-10 MSamples/Sec

[face_off]

You don't have to render until Max Samples have been reached. You render until all the noise is gone and everything is sharp. So the MSamples/Sec is not of concern. Sometimes the MSamples/Sec will be lower with a particular setting, but the render is cleaning up faster. I would expect a scene light via Daylight to render very quickly. One other thing to try is to increase the Kernel-> Coherent Mode (0 = setting up the scene, 1 = for the final render).

Paul