What's New:
New Features
- Add a way to purge old DATs
- Filter for MIA ROMs
- Create default directories for new setups (DatRoot, RomRoot, ToSort)
- Handle locked files better during scanning
Bug Fixes
- Empty directories and 0 byte files are deleted from locked branches and ToSorts
- DatVault can throw invalid JSON error
- Missing status for "In DAT merged, delete" in ROM details grid
- FixDATs are missing MIA flags
- CMP DATs are interpreted with incorrect character encoding
- Crash occurs if a RV temp archive cannot be deleted
- Crash occurs when generating Fix DATs for directories using Single Archive
- Cache can become unstable and trigger errors on every change
- Corrupt CHDs lose their corrupt status
- Some edge case statuses are missing images
- DATs with single archive directory settings are reprocessed on every DAT update
- Registration window uses default icon in task bar
- Elevated RAM usage after refreshing all DATs
- Files can be stuck in a "cyan" state until rescan
- Crash occurs when moving a file open by another process
- Readable corrupt zips that require fixes cause repeated errors
- DatVault can load with no Groups displayed, refresh causes crash
- Missing ROMs from "Single Archives" are included as orphaned ROMs in the wrong FixDAT
- The "In DAT merged, move to ToSort" scenario displays a broken image in ROM details grid
- Crash occurs if a RV temp archive is open by another process during a rename
- Crash occurs during Full DAT creation if DAT has missing rom names
- Crash can occur during a cache backup if not enough space
- ZipMove is sometimes not used if the archive to be moved contains a 0 byte file
- Fixes from 7z archives to Uncompressed sets do not use the 7z cache
- The Compress action is missing the filesize in the fixing status log
- The “_0” is inserted into the incorrect place to avoid naming conflicts if the set name contains periods
- Ampersand characters in the directory settings Dir Location are not displayed
- Recompressing to RV7Z shows a status of TrrntZipping in the status log
- An unaccounted for combination of ROM statuses can occur during a fix and throw an error
- A filesystem error occurs if RomVault tries to ZipMove an archive while it is open in another application