Differences

This shows you the differences between two versions of the page.

--- global_settings [2022/11/20 10:52] – [Debug Logs Enabled] johnsanc
+++ global_settings [2024/04/14 16:45] (current) – johnsanc
@@ Line 15: / Line 15: @@
-===== Filenames not to remove from Dirs =====
+===== Filenames not to remove =====
 This setting allows you to specify rules for files to ignore in your ToSort folders. Any ignored files are still scanned by RomVault, but they are flagged with an "ignore" status and will not be removed or used for fixes. To force the scanning engine to completely ignore files and not attempt to scan, prefix the the rule with ''ignore:''. Some examples include:
@@ Line 32: / Line 32: @@
-===== Double Check Delete =====
+===== Double check file exists elsewhere before deleting =====
 Enabling this setting ensures that a good copy of the file to be deleted exists elsewhere before deleting. This setting makes delete actions a bit slower which is a tradeoff for ensuring files are not deleted due to a misconfiguration. You should only disable this if you are sure your Directory Rules are mapped correctly and you do not have multiple DAT paths mapping to the same directory.
   * Default: Enabled
-<WRAP info>Its highly recommended to keep this setting enabled. When this option is enabled RomVault does not blindly trust the information in cache for delete operations. For example, if you scanned a directory of files then RomVault would store the information about those files in the cache. If you then moved that directory or deleted the files without performing another scan, then RomVault still assumes you have those files in that location. In this scenario, if Double Check Delete were set to "Disabled" then RomVault may delete the only copy of that file you have instead of moving it to your Primary ToSort.</WRAP>
+<WRAP info>Its highly recommended to keep this setting enabled. When this option is enabled RomVault does not blindly trust the information in cache for delete operations. For example, if you scanned a directory of files then RomVault would store the information about those files in the cache. If you then moved that directory or deleted the files without performing another scan, then RomVault still assumes you have those files in that location. In this scenario, if the setting was "Disabled" then RomVault may delete the only copy of that file you have instead of moving it to your Primary ToSort.</WRAP>
@@ Line 48: / Line 48: @@
-===== Convert all 7z to RV7z =====
+===== Dark Mode =====
-Enabling this setting will recompress all 7z archives to RV7z format during a fix operation
+Enabling this setting will make RomVault's color palette a dark theme. A restart of the application is required.
   * Default: Disabled
-<WRAP info>If this is disabled then existing 7z or torrent7z archives will remain as is. However, any new or modified 7z archives will be written as RV7z. RomVault can read regular 7z and torrent7z archives but it only supports writing RV7z archives.</WRAP>
+===== Max ZSTD workers =====
+RomVault uses a multithreaded implementation of zstd. This setting specifies the maximum number of workers to spawn per compression stream.
+  * Default: Auto (Detected CPU cores minus 2)
-===== Detailed Fix Reporting =====
+<WRAP info>RomVault uses zstd level 19, which has a job size of 32 MiB. Each worker or thread will process a 32 MiB chunk of the data stream. Smaller files will compress slower than a single large file because fewer workers are spawned. This behavior is normal and is apparent if you monitor CPU utilization during a Fix.</WRAP>
-Enabling this setting will display more verbose logging while a fix is running. This primarily includes Delete actions and has no impact on fixing performance.
-  * Default: Disabled
+===== Default 7z type =====
+This setting specifies how RomVault should pack 7z archives in ToSort directories in the event that the 7z archive needs to be modified.
+  * Default: ZSTD Non-Solid
-===== Send Found MIA (DATVault Users Only) =====
-Enabling this setting will send a notification to DATVault whenever you find an MIA ROM. This will then remove the MIA status from the DAT during the next scheduled DATVault update which normally occurs at least once per day.
+===== Send Found MIA notifications =====
+Enabling this setting will send a notification to DATVault whenever you find an MIA ROM. Once enough people have found the ROM, the MIA status will be removed from the DAT during the next scheduled DATVault update which normally occurs at least once per day.
   * Default: Enabled
+===== Send anonymously =====
+This setting is a modifier to the Send Found MIA notifications setting. It allows DATVault users to send MIA notifications without any association to their DATVault key. This effectively makes Patreon supports appear like anonymous RV users. This setting has no effect for users without a DATVault key since they are already anonymous.
+  * Default: Disabled
+===== Delete previous Cue file zips in ToSort =====
+This setting is mainly for DATVault users who collect a subset of redump.org discs and use the "Keep only complete" DAT Rule setting. When "Keep only complete" is used, partial sets are not stored in your RomRoot. The most common culprit for a partial set is the cue file. This setting simply deletes old cue packs from ToSort so they do not pile up with files that are purposely ignored since they would result in an incomplete set. This setting has no effect for people who do not use DATVault.
+  * Default: Disabled
+===== Show detailed actions in Fixing Status window =====
+Enabling this setting will display more verbose logging while a fix is running. This primarily includes Delete actions and has no impact on fixing performance.
+  * Default: Disabled
-===== Debug Logs Enabled =====
+===== Enable Debug logging =====
-Enabling this setting will write debug log files to the "Logs" directory relative to the RomVault EXE
+Enabling this setting will write debug log files to the "Logs" directory relative to the RomVault executable
   * Default: Disabled
 <WRAP info>Do not enable this unless you are troubleshooting an error. If you are asking for support on the RomVault Discord, please try to reproduce the issue with debug logs enabled as it will help others help you with the issue.</WRAP>