RV alters the format of the FixDAT depending on the user's DAT settings. When the archive type is set to file, any paths in <rom> tags are converted to <dir> which creates a DAT that has malformed information which is skipped in RV's DAT processing logic.
Example Fix DAT with archive type set to Zip, notice the full path including the Proof folder:
Same Fix DAT with archive type set to File, notice the <dir> with a <rom> within it:
The impact is that "game > dir > rom" is invalid and not processed:
Whereas the first Fix DAT is proper and RV can see this file in the DAT:
Example of problematic FixDAT structure:
<game name="Black.Desert.iNTERNAL.READ.NFO.PS4-AUGETY">
<rom name="augety-black.desert.internal.read.nfo.ps4.nfo" size="9593" sha1="fd0bab5d07fc3e9122d614881ad4d0053cc3e65f"/>
<dir name="Proof">
<rom name="augety-black.desert.internal.read.nfo.ps4.jpg" size="2448325" sha1="624199f7bd84da218ab89ef5a89ed9afc7934189"/>
</dir>
</game>
johnsanc
last quarter
RV alters the format of the FixDAT depending on the user's DAT settings. When the archive type is set to file, any paths in <rom> tags are converted to <dir> which creates a DAT that has malformed information which is skipped in RV's DAT processing logic.
Example Fix DAT with archive type set to Zip, notice the full path including the Proof folder:
Same Fix DAT with archive type set to File, notice the <dir> with a <rom> within it:
The impact is that "game > dir > rom" is invalid and not processed:
Whereas the first Fix DAT is proper and RV can see this file in the DAT:
Example of problematic FixDAT structure: