{"id":2601,"date":"2026-03-31T10:30:00","date_gmt":"2026-03-31T00:30:00","guid":{"rendered":"https:\/\/digitalbbq.au\/?p=2601"},"modified":"2026-03-30T18:08:20","modified_gmt":"2026-03-30T08:08:20","slug":"bim-cache-cleaner-3-5-3-update","status":"publish","type":"post","link":"https:\/\/digitalbbq.au\/index.php\/2026\/03\/31\/bim-cache-cleaner-3-5-3-update\/","title":{"rendered":"BIM Cache Cleaner 3.5.3 Update"},"content":{"rendered":"\n

Revit 2026 changed how cloud model caches can be configured, and BIM Cache Cleaner wasn\u2019t picking that up properly.<\/p>\n\n\n\n

In Revit.ini<\/span>, Revit now allows the cloud cache to be redirected using:<\/p>\n\n\n

[CloudModelCache]\nCacheLocation=...<\/code><\/span><\/pre>\n\n\n
On a few machines I tested, [Directories] ProjectPath<\/span> was empty, but CacheLocation<\/span> was set. BIM Cache Cleaner was still scanning the default location:<\/p>\n\n\n
%LocalAppData%\\Autodesk\\Revit\n<\/code><\/span><\/pre>\n\n\n
So it simply never saw the real cache.<\/p>\n\n\n\n
In 3.5.3<\/strong>, the scanner now checks CacheLocation<\/span> first. If it\u2019s present and valid, that\u2019s the path it uses. If not, it falls back to the default. That fixes cache discovery for Revit 2026 users who\u2019ve customised their setup.<\/p>\n\n\n\n
While fixing that, I did a small amount of internal cleanup to make future changes less brittle.<\/p>\n\n\n\n
I added a basic dotnet test<\/span> project so there\u2019s at least a sanity check without having to mockup cache folders for various Revit versions before shipping changes. It\u2019s not exhaustive, but it\u2019s better than relying on manual testing alone.<\/p>\n\n\n\n
I also wrapped filesystem access behind a simple IFileSystem<\/span> interface. That pulls file and directory operations (and timestamp handling) into one place and reduces duplication between the normal scan and the quarantine scan. Behaviour stays the same; the code is just easier to reason about when path logic gets weird.<\/p>\n\n\n\n
I also took this as an opportunity to try out Claude Code combined it with GLM5 to help investigate the Revit 2026 config and help with some of the refactor. First time using an AI coding tool, and it worked out quite well. I kept the scope tight, worked in small steps, and manually checked every change before it went anywhere near a release.<\/p>\n\n\n\n
Version 3.5.3<\/strong><\/p>\n\n\n\n