-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Machine output setting only works when enabled as a global setting #305
Comments
Because of the admittedly very unlikely but entirely possible scenario that someone could mix As far as I'm aware ROM managers don't care whether I figure |
The MAME Redump dats initially stopped using the I believe RomVault does seem to treat |
Okay, looks like I'll have to do a little testing there. As for the system settings: I don't have access to my dev machine at the moment, but this was working when I implemented the feature. If I were to take a wild guess, when I hooked up the MAME Redump DAT files to the Redump clone lists afterwards, Retool decided the files were actually from Redump. This means they would share settings with the official Redump DAT files, opening up the opportunity for clashes. If this is the case, a bit more plumbing will have to be put in to still be able to use the Redump clone lists, but identify the MAME Redump DAT files as their own thing. |
Fixed in 2.02.2. Additionally, whether a title is in a |
The "Use
<machine>
instead of<game>
in output DAT files" option does not work when enabled in "System settings". Only works when set in global settings.Also, was there a reason to not have this setting be derivitive from the source file? For example
"Use
<machine>
instead of<game>
in output DAT files if used in the original DAT."An option like that, I could set globally, and all my CHD Redump and NoIntro dats would all process fine in one sweep.
The text was updated successfully, but these errors were encountered: