"vis. cache" = "env cache" ?
(But yes, that is the idea)
"vis. cache" = "env cache" ?
There is a problem with erratic photon distribution from infinite light leading to ghost reflections in glossy surfaces, that could be helped with cyclic cache.
Persistent (indirect) cache should work, persistent (caustic) cache should work too but it quite pointless as the saved cache will be used only for the very first cycle ... don't talk about "Cycles" ... it confuse meepilectrolytics wrote: ↑Mon Jun 17, 2019 8:23 pm Cyclic cache prevents persistent cache, that has to be exposed properly in Blender.
This should already work (see above).epilectrolytics wrote: ↑Mon Jun 17, 2019 8:23 pm It could get complicated like this:
Rendering an animation with persistent indirect cache plus a cyclic caustic cache.
This is normal, the update is done at least after X samples, not exactly at X samples (threads continue to asynchronous render while the need of an update is recognized, they a will always render a bit more before they can stop for the update, this will be even more noticeable with GPUs).epilectrolytics wrote: ↑Tue Jun 18, 2019 8:32 am Also the updating happens one sample later as specified:
If I want cache updates at sample 8,16,24,32... I have to choose 7 as parameter.
Are you sure? In my tests it worked in Blender, although the console messages indeed do not appear.epilectrolytics wrote: ↑Tue Jun 18, 2019 8:32 am Only it does not really work yet:
Cache update does not seem to happen as also indicated by console view which shows no entries during render.
New test scene works, the reason was this:
My first tests in LuxCoreUI showed when I enter periodic sample step of 7, the caustic pattern in the render view will change after 8,16,24... samples (corresponding with console print).Dade wrote: ↑Tue Jun 18, 2019 8:49 amThis is normal, the update is done at least after X samples, not exactly at X samples (threads continue to asynchronous render while the need of an update is recognized, they a will always render a bit more before they can stop for the update, this will be even more noticeable with GPUs).epilectrolytics wrote: ↑Tue Jun 18, 2019 8:32 am Also the updating happens one sample later as specified:
If I want cache updates at sample 8,16,24,32... I have to choose 7 as parameter.
Maybe I'm stupid again, but I don't get it to work.