Add Stop to DLCS or any other pre-rendering phase

[marcatore]

As subject, please devs, is it possible to have the opportunity to stop a caching phase calculation?

If, for example, something goes wrong with the settings you have just two choices:

1- kill Blender if you are sure you have saved file before start rendering (this force you to remember this everytime)

2- wait it ends calculation

Thank you

[Dade]

Yes, it is known problem, something we need to look into (however, the solution isn't going to be trivial to write).

[lacilaci]

or, make calculating of caches so fast that it's not a problem there you go, problem solved

[Dade]

or, make calculating of caches so fast that it's not a problem there you go, problem solved

"There are no free lunches"

[marcatore]

Yes, it is known problem, something we need to look into (however, the solution isn't going to be trivial to write).

Ok... I hope you'll find a way to do it.

or, make calculating of caches so fast that it's not a problem there you go, problem solved

[lacilaci]

or, make calculating of caches so fast that it's not a problem there you go, problem solved

"There are no free lunches"

so maybe just a little faster, like 75% faster??

[FarbigeWelt]

Yes, it is known problem, something we need to look into (however, the solution isn't going to be trivial to write).

Why can you not just divide into partial loops like you do it for console messages (pgic indirect cache photons counting)? Rendering can be stopped with ‚ESC‘ key. Is there not a similar solution possible? It would be very useful sometimes.

Just another side idea: If cache evaluation is dividable why not start rendering with the first bunch of entries and refining step by step. This would reduce waiting for first result, i.e. fast but inaccurate then improving stepwisely accuracy with the advantage to stop at any time.

[provisory]

Just another side idea: If cache evaluation is dividable why not start rendering with the first bunch of entries and refining step by step. This would reduce waiting for first result, i.e. fast but inaccurate then improving stepwisely accuracy with the advantage to stop at any time.

Something like that would be great!