Show the file that is currently being processed in the scanning/fixing status windowRV 3.5.1EnhancementFixed in: 3.5.0 WIP5 Today the scanning status window displays the last scanned file or directory.2
Loading RomCenter DATs causes crashRV 3.7.0CrashLoading RomCenter DATs causes RomVault to crash with an "index was outside the bounds of the array" error. These DATs supposedly worked with 3.5.1 but do not work with 3.6.4. 0
Corrupt CHDs crash RV scanRV 3.6.0CrashRV crashes with error HDERR on corrupt CHDs. This occurred when chdman.exe was present in the RV directory. The CHD that caused the crash was v4 with compression level 2. If you run the CHD through chdman verify directly a fatal error occurs, Example: chdman verify -i C:\Emulation\ROMVault3\ToSort\lasstixx.chd chdman - MAME Compressed Hunks of Data (CHD) manager 0.233 (mame0233) Error reading CHD file (C:\Emulation\ROMVault3\ToSort\lasstixx.chd): read error Fatal error occurred: 1 (screenshot)1
Empty directories and 0 byte files are deleted from locked branches and ToSortsRV 3.5.2Logic Issue Any branch or ToSort can be locked in the tree and is signified as such with a lock icon. This implies that the directory will not be modified and no files will be deleted. However, even if a directory like a ToSort is locked, 0-byte files and empty directories will be deleted during a fix. This issue is problematic for some collectors who keep 0-byte files or directories in their archives that they want to keep. For example someone may create a 0-byte file placed in a directory that has a filename that indicates where they found the content. Also, many old PC games present in TDC and eXoDOS sets contain intentional empty directories. Steps to reproduce: Create a 0-byte file and place it in a non-Primary ToSort Create an empty directory and place it in your non-Primary ToSort Lock the ToSort directory in the tree Scan the ToSort so that the file and directory are logged in RV's cache Perform a fix while the ToSort is locked Notice that the 0-byte file and empty directory are deleted Expected behavior: 0-byte files and directories should not be deleted if the directory is locked as indicated in the tree1
ZipMove does not work when archive contains 0-byte files or empty directoriesRV 3.7.0FixingIn some cases, the ZipMove action does not work if the archive contains 0-byte files or empty directories. This behavior has frequently been observed with the Sega ALLS DAT when sets are renamed. This appears to be an issue with the order in which the files are processed. The archives which would need to be zipmoved are processed before the archive to be fixed due to alphabetical ordering. The archives which need to be used for the fix contain zero byte entries, which are normally deleted since they can be recreated. Thus when the deletions of zero byte files occur, the archive becomes ineligible to be zipmoved. 0
Corrupt CHDs marked as good after L1 then L2 scanRV 3.6.2ScanningIf a corrupt CHD is first scanned with a header-only scan it is recorded as good in the cache. If a regular scan is conducted afterwards, the scanning window will identify the CHD as corrupt, however the status will remain as good instead of corrupt. Steps to reproduce: Purposely create a corrupt CHD by modifying a few bytes somewhere in the middle of it with a hex editor Scan the CHD with a header-only scan and notice it is not detected as corrupt (expected) Rescan the CHD with a regular scan, and during the verification process the scanning window will show the CHD is corrupt (expected) After the scanning is complete, the corrupt CHD is not flagged with the appropriate corrupt status in the game list / rom details grids. 0
Missing text when using LinuxRV 3.6.0General UXLinuxMany parts of the RomVault UI are missing text when running with mono on Linux, particularly Ubuntu. The issue occurs on fresh installs of ubuntu 22.10, 23.04, and debian 12. Another user reported the same on debian with xfce so probably not kde that broke it. He mentions: "I'm erring towards libgdiplus and its dependencies (handles .net/mono's system.drawing mechanism which includes the fonts) being the culprit, it's the only reasonable change I can find, the distro's that work are using an 'older' version+dependencies, debian and ubuntu have significant dependency changes between version 6.0.4 and 6.1 of the libgdiplus package." Also, the font library dependency for mono changed on debian/ubuntu - likely the font and app window sizing is causing text not to be displayed now. Suggest maybe trying a smaller font that fits in the RV UI rows to see if that resolves the issue. (screenshot)0
datvault doesnt work under linux/monoRV 3.6.0CrashLinuxHard crash.. application just kills itself. Issue first introduced with 3.6.0 WIP1. cmdline shows error in UpdateMasterLists0
Split / Merged settings result in a crash with some No-Intro DATsRV 3.6.0CrashThere appears to be an issue with the handling of parent/clone relationships in RV 3.6 WIP builds. The standard No-Intro Nintendo DS DAT from DatVault may have invalid or references for P/C relationships that are not handled gracefully. Steps to reproduce: Download the standard No-Intro Nintendo DS DAT from DatVault Configure directory settings for that DAT to either Split or Merged RomVault will crash instantly without error Example Problematic DAT: https://cdn.discordapp.com/attachments/622121052364865591/1086751133919363144/Nintendo_-_Nintendo_DS_Decrypted_20230318-025455.dat0
ZipMove causes crash when fixing a set with NotCollected ROMsRV 3.7.0FixingCrashWhen ZipMove is used to fix a set that has NotCollected ROMs (E.g. using merged/split MAME listxml), RV will crash with an "Index was out of range. Must be non-negative and less than the size of the collection." error. 0
RV7Z archives are recompressed when "Convert all 7z to RV7Z" is enabledRV 3.6.4FixingA regressive defect was introduced in 3.6.2 where if the global setting "Convert all 7z to RV7Z" is enabled, RV will needlessly recompress RV7Z files.0
Missing status icon for MIA found but not used for fixRV 3.6.4FixingIn the scenario where you have just found an MIA rom that belongs to a set that cannot be completed due to other MIA roms, RV will display a missing status icon in the rom details grid. Steps to reproduce: Start with a redump dat that contains bin and cue files Search for any MIA file in the DAT, and manually flag the associated cue file in the set as MIA as well. Modify the directory rule for your dat to use the option to keep only complete sets Scan and find fixes so that the cue file you manually flagged as MIA is now listed as MIA Found in bright yellow Notice the rom details grid and the status icon for that fix action is missing. ("Found an MIA, but wont be used for a fix because the set would still be incomplete") 0
MIA status is sometimes lost when using "Merge" settingRV 3.6.2Logic IssueThe No-Intro PS Vita PSGameSD DAT contains MIA tags as expected, but the MIA status is not applied to some sets when Merge mode is used. Merged: Not Merged: 0
Cache can become corrupt with "Unknown Tree settings in DisplayTree" errorRV 3.6.0Logic IssueThe cache can become corrupt if Dats are rearranged and updated in a certain way. This issue was reproducible by one user by doing the following: Place two copies of the same DAT into your DatRoot like this: /Testing/dat1.xml /dat1.xml Ensure the directory rule applied to both DATs has "Don't auto add DAT directories" disabled Update DATs Add an additional copy of dat1 into the main directory so you now have three copies of the DAT like this: /Testing/dat1.xml /dat1.xml /dat2.xml Update DATs RomVault will trigger errors upon DAT update Note that this issue only occurs when doing a normal DAT update. If refreshing all DATs after step #4 then the normal dat merge conflict error occurs. (screenshot)0
DatVault can throw invalid JSON errorRV 3.5.2Logic IssueMalformed JSON can cause DATVault to throw an error1
Missing status for "In DAT merged, delete" in ROM details gridRV 3.5.2Logic IssueRomVault displays a broken image in the ROM details grid when a deduped ROM needs to be deleted. Steps to reproduce: Scan an archive Load a DAT for that archive that has a matching file flagged with the "dedupe" status Find Fixes and notice the broken image in the ROM details grid Expected behavior: A descriptive icon should display in the ROM details grid instead of a broken image icon. (screenshot)1
FixDATs are missing MIA flagsRV 3.5.2Minor BugWhen a FixDAT is created, RomVault omits the mia=yes flags for MIA files. Steps to reproduce: Add a DAT to your DatRoot that contains MIA flags, for example No-Intro Sinclair ZX Spectrum Select the DAT in the tree Click "Generate Reports" to create a FixDAT and save the file somewhere Open the newly created FixDAT and notice that the MIA roms are missing the mia=yes attribute Expected behavior: These flags should be preserved in FixDATs.1
CMP DATs are interpreted with incorrect character encodingRV 3.5.2Minor BugThere is a discrepancy between how characters are interpreted in CMP formatted DATs vs XML formatted DATs. XML dats are interpreted correctly with UTF-8 characters while CMP dats are not. Steps to reproduce: Refer to screenshots for an example Expected behavior: All characters should be interpreted with UTF-8 encoding regardless of the original dat format (screenshot 1 | screenshot 2)1
Crash occurs if a fix requires the 7z cache but no ToSort directory existsRV 3.5.2CrashIf a 7z file needs to be torrentzipped using the 7z cache, but a ToSort directory does not exist, then RomVault will crash. Steps to reproduce: Start a clean instance of RomVault with no default directories Add a dat to your DATRoot Add a solid 7z archive that contains files needed by the DAT somewhere in your RomRoot in an incorrect directory Scan your ROMRoot so the 7z archive is hashed Check with explorer and ensure no ToSort folder exists, delete it if it does exist Fix ROMs Notice that RV crashes when attempting to decompress the 7z archive to the Primary ToSort Expected behavior: If the Primary ToSort directory does not exist, it should automatically be created at the time of the fix, AND If a cache ToSort is defined but does not exist, it should automatically be created at the time of the fix. (screenshot)1
Crash occurs if a RV temp archive cannot be deletedRV 3.5.2File AccessIf a RV temp file is encountered during a scan, RV will try to delete it. A crash will occur if the temp archive is open by another process. Steps to reproduce: Perform a fix that will have RomVault create a large zip archive, for example a compressed DVD-sized ISO While RomVault is compressing the archive, force the application to close using the task manager Open the temporary archive in another application so that the file is locked Test that the file is properly locked by trying to delete the temp archive with explorer After you confirm the file is locked, start RomVault back up Scan the directory where the temp archive resides When the scan reaches the archive, RV will attempt to delete the temp file and crash Expected behavior: RomVault should present the user with a halting error notifying that the temporary file could not be deleted, OR RomVault should flag the file as locked and proceed with the rest of the scan. (screenshot)1
Crash occurs when generating Fix DATs for directories using Single ArchiveRV 3.5.2CrashIf you generate fixDats on directories that are using the Single Archive setting with “Add SubDirs if multiple roms” with File as the archive type then RomVault will crash with an error. The text reports will not cause a crash, but the reports will not include any information from the directories using Single Archive. This may also occur under other directory setting scenarios but this is unconfirmed. Steps to reproduce: Put the Redump PlayStation 3 DAT in your DATRoot Change the directory settings to: Archive Type = File + Override DAT, Single Archive = Add SubDirs if multiple roms (see screenshot 1 below) Apply the directory settings so the DAT is reprocessed Generate a fixDAT for the PS3 directory from the tree Notice a crash will occur Expected behavior: FixDATs should be generated properly using the original DAT settings (not the effective settings due to directory rules) (Screenshot 1, 2) 1
Clicking category reorder buttons causes crashRV 3.7.0CrashIf you edit a DAT rule and try to reorder categories when none exist, a crash occurs. Steps to reproduce: Setup a new instance of RV Edit the DAT Rule for the RomRoot and go to Advanced tab Click on either the up or down arrow for the category list RV will crash with an "Index was out of range" error 0
DatVault does not load tree and triggers errorRV 3.6.2DATVaultSometimes when loading DatVault the tree will not display and an invalid operation exception will trigger. This is not consistently reproducible and appears to be a race condition. This can easily be reproduced with a new RV setup after entering a valid DV key. 0
Repacking zips in ToSort modifies file timestampsRV 3.7.0FixingWhen an archive in a ToSort is repacked the files are raw copied but the modified timestamps for those files are set to TorrentZip dates, however the file is not actually a TZip file. This frequently occurs when cues are removed from a redump cue pack but there are some remaining cues left, which RomVault repacks. Expected behavior: Files within the repacked archive should retain the original modified timestamps. 0
Duplicate Directory Rules can be stored in the cacheRV 3.7.0Logic IssueIts possible for duplicate rules with the same DirKey to be stored in the cache. This can happen if you manually edit the config xml to create a duplicate rule with different settings from the one that is already stored in the cache. When you load RV and update DATs, the config file is updated and one of the rules is removed, however both will remain in the cache. To resolve this, you can remove one of rules and both will be deleted because they share the same DirKey. Expected behavior: RV should check for duplicate rules when processing the config XML and show the user an error.0