-
Notifications
You must be signed in to change notification settings - Fork 51
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
Volume in ROMS gets reset when updating to new Vpinmame #342
Comments
You're talking about using the in-game volume controls, such as using the 8/9 keys in WPC games? If so, then the settings aren't stored in the ROM files themselves (since those are treated like what the name literally says, Read Only), which is why saving and restoring those makes no difference. The in-game settings via the ROM program are stored in simulated non-volatile RAM, which is in the .nv files in the NVRAM folder under PinMame. So saving and restoring those files should restore the settings. |
The actual ROM volumes using Vpinmame to alter. |
"official" rom settings changes, such as 8/9 in WPC, or similar, are stored in .nv file. This is equivalent with real hardware, where these settings are stored in a separate non-volatile-ram besides the game ROM. |
@Urkz Did you use the official VPinball installer to update? Cause then some nvram files may be overwritten. |
Sorry about bit late reply, ive been experimenting. I just tried it again just now with a cfg folder of loads of altered table data when i copy and paste it back , its reset. |
Hi,
I have tried asking on forums but no real positive answer, i thought this would be the place to get a definitive answer :)
I have altered the volume levels with a number of table roms , yet if i update my Vpinmame the volumes in the ROMs are reset to as they were.
(ive kept a backup folder of Vpinmame with my volume alterations)
I have tried just copying over the ROMs thinking that might be the issue, but the volumes are reset even though they are copied over from a backup folder where they were lowered.
Is this just what happens or is there a workaround ?
Cheers.
The text was updated successfully, but these errors were encountered: