Proof Suite — Twelve Checks, One Verdict on the Whole Delivery
Carries all twelve tools: Cache Commander at 1.2.3 and the other eleven at 1.2.2. The Whole Delivery folder check no longer replaces a file in the folder you pick: if <tool>_report.html (or the baseline file) is already there, it is left as it is and the new file takes the next free name (<tool>_report_2.html and so on); the message names the file written, the report and baseline keep one number, and a folder that cannot be written to is refused in words, a folder that has the report's name is skipped, no empty report is left when the baseline cannot be created, a file whose check prints a lot no longer stalls the run on Windows, and a file that cannot be opened or has nothing to check is explained in words (before, the closing message often ended in a Python error instead). SampleProof: the tooltip of Measure The Denoiser now says the extra frame is rendered with the opposite denoiser setting to your scene's. No other changes.
Maintenance release. Carries all twelve tools: Cache Commander at 1.2.2 and the other eleven at 1.2.1.
Every package now ships the full GPL-3.0 licence text (before, a short notice with a link) and a README with install, first-run and uninstall steps.
Rig Inspector lost a duplicated internal helper. No changes to any check.
Verified: all twelve install and enable together on Blender 4.2.9 and 5.2.0.
Carries all twelve tools, with Cache Commander at 1.2.1 and the other eleven
unchanged at 1.2.0.
Cache Commander's move to another folder is now safe for whatever is already in
that folder. The folder you pick is usually an external drive with other work on
it, and the move wrote straight to the destination filename without asking
whether it was free: a cache from another project, or an Alembic file of the
same name, was overwritten without a word, and a failure partway through could
then delete that file as well. A destination name is now taken only when the
filesystem says it is free, a collision is stored under the next free name and
reported, copies are verified beside the destination and put into place in one
move, the clean-up after a failure removes only files the operation created, and
a cache that could not be repointed keeps the settings it had.
The same testing found that moving a cache a second time read the frame number
from the wrong end of the filename, so any cache whose name contained an
underscore was written under a name Blender does not look for and stopped
playing. That is fixed and covered by a test that moves twice and compares the
frame vertex for vertex.