LeakProof — Where Light Gets Into Your Interior, and Proof It Stopped
The Whole Delivery folder check no longer replaces a file in the folder you pick. Before, the report was always written as leak_proof_report.html (and the baseline as leak_proof_report_baseline.json), and a file with that name already there, such as an earlier report you kept, was overwritten. Now a free name is taken (leak_proof_report_2.html and so on), the message at the bottom of Blender names the file it wrote, and a run that fails while writing removes only the file it created. The report is written as UTF-8, as the page declares. The report and the baseline keep one number (leak_proof_report_2.html with leak_proof_report_2_baseline.json). A folder that cannot be written to is now refused in words instead of a Python error (and no empty report is left behind when only the baseline cannot be created), a folder that already has the report's name is skipped like a taken file, and the closing message is shown: before, a run with no problems or with unchecked files ended in a Python error instead of the message. Checking a folder no longer stalls on a file whose check prints a lot: on Windows such a file sat until the 30-minute limit and was reported as not finished. A file Blender cannot open, or one with nothing to check, is now explained in words instead of a Python error.
README names the version and the sidebar tab.
Discover more products like this
architecture proof light leak validation gaps Scene Cycles Render ArchViz Lighting walls Interior