Bucket rectangles saved with snapshots

[maxtarpini]

Would be cool to not have buckets corners on the same framebuffer where we have rendered pixels so we can have clean snapshots 😉 I know I can disable them but sometime I need to have a clue where Arnold is doing work.

[peter_horvath · Accepted solution]

I'll make a ticket, but looking at the code it might not be so trivial to implement. So I can not promise this will be addressed soon.

[maxtarpini]

When you gonna fix this take care also that when you draw another render region .. buckets on the first region remain there.

[peter_horvath]

---

@maxtarpini wrote:

When you gonna fix this take care also that when you draw another render region .. buckets on the first region remain there.

---

 Noted, thanks. I have a plan how to fix this, but no ETA at the moment.

[maxtarpini]

Hopefully I'm not bothering you Peter 😉 Just noted another couple of things.

While the rendering is started, enabling or disabling buckets ain't updating. 

When the OIDN denoiser is in the imagers list but then disabled, buckets have some erratic behaviour.. kinda appearing when the frame starts rendering and then randomly disappering. 

🖖

[peter_horvath]

Sure, no worries, just keep the feedback coming. Hopefully I'll have some time soon to work on this.

[peter_horvath]

Hi Max, bucket corners are fixed in the latest release, C4DtoA 4.6.4.

Regarding the denoiser imager, it is executed periodically on the full frame buffer, that's why buckets are filling the entire image then disappear repeatedly. Changing that would require some serious effort, so I can't promise anything for the short-term.

[maxtarpini]

Oh wow this is great Peter, well done .. really like all the improvements on the IPR ! 

There's just a little problem: on old scenes the 'Display buckets corners' is greyed out and whatever it was set .. it's not displaying the buckets. 

The thing about the denoisers with the imagers is so bad on all the plugins that I cannot get a clue how ppl can work with that at all. Thing is that even disabling it while leaving the imager, it still impacts the fb rendering.

[peter_horvath]

Do you have progressive render enabled maybe? Bucket corners are disabled in progressive mode and on the GPU now.

[maxtarpini]

Yes I have progressive enabled.. why buckets are disabled in progressive mode ?.. it still works on a buckets basis as opposed to GPU.

[peter_horvath]

Well, GPU and progressive CPU basically works the same. The data transfer to the display driver is still bucket based, but iterates over the full image multiple times. The CPU is much slower though, that's why you can catch the bucket corners on the screen, as opposed to the GPU, where they are just flashing. That said, it might make sense to re-enable them on the CPU.

[maxtarpini]

Yeah re-enable them 😉 also to stay inline with the other plugins.

[maxtarpini]

This works a treat now.. thanks again Peter ! 🖖