what with BF being so fast these days, the only reason i really depend on imap is for flythroughs, where “multiframe incremental” is a massive timesaver..
any chance we can get a “multiframe incremental” cached option for BF? or is it just impractical? i guess it would mean either modifying imap to do an unfiltered per-pixel solution (currently doesnt work, even with interpolation at 0 (or 1 i dont recall) and min and max at 0, it produces a horrible result much slower than BF) or separating the BF into a prepass, which might be rather a big job.
in fact, I’m doing a job right now where its simple geo in the exterior setting. I cached irmap/lc but there were splotches so I switch to bf/lc. Render time went down from 50 min per frame to 30!
We’ve just had a bit of a nightmare job which was a 5000 frame long sequence. It was too slow with BF/LC and as it was just a camera move, no animated objects we did IR + LC with a pre-baking pass first, the dynamiscism of the camera move meant we had to prepass in some cases every 2nd frame rather than every 10th… We ended up breaking the sequence into sections, rendering these separately so we use more machines to cache the prepass. We still had loads of flickering issues in the fine detailed areas. It was a horrible scene, very low gloss flat colour surfaces with fine bump maps, paper-thin modelling details.
For camera fly-throughs, we could really do with a more advanced caching system now, being able to bake the scene with BF could have really helped!
If you think you can send me some part of that scene for investigation, it will be very helpful. From the description, it looks like the GI was not the real problem, but it would be good to take a look anyways.