ccgreen13 / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

mupen64plus.ini file keeps savestates from being saved/loaded #492

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Describe your system:
 - Windows XP Home SP3 32-bit
 - Mupen64Plus 1.99.5 Windows
 - Default plugins used

Describe the problem:
If I have this file in my directory, I cannot save or load states with F5/F7.  
The reason for this seems to be the existence of some kind of entry for each 
game; if I remove the individual entry for the game I'm playing from this file, 
then I can use savestates just fine.  For example, if I remove everything that 
uses the MD5 of the version of Super Mario 64 that I'm playing (including any 
game with a RefMD5 line linking it to the one I'm playing), I can save states, 
and I don't get any eeprom errors in the console.  Once ANYTHING in that file 
links to the game I'm playing, it all goes to hell.  I still don't understand 
why this file even exists.  It creates so much grief and does literally nothing 
for the emulator, pointlessly keeping some sort of database of ROM files that 
nobody is ever going to use.

Original issue reported on code.google.com by written_...@yahoo.com on 6 Apr 2012 at 5:35

GoogleCodeExporter commented 9 years ago
Issue 491 has been merged into this issue.

Original comment by s...@narfation.org on 6 Apr 2012 at 8:31

GoogleCodeExporter commented 9 years ago

Original comment by s...@narfation.org on 6 Apr 2012 at 8:31

GoogleCodeExporter commented 9 years ago
The mupen64plus.ini file contains data which is useful for front-end 
applications (number of players, rumble support, good name, etc) and some data 
which is used by the emulator core (eeprom size).  I tried to replicate this 
bug on my 32-bit WinXP laptop and was unable to.  I was able to save and load 
states with F5/F7 with Mario Kart. Can you please provide the following 
information to help diagnose the problem?

1. What ROM(s) did you use to produce this problem?
2. In what directory is Mupen64Plus installed?
3. How are you running Mupen64Plus? (ie, from DOS prompt, from shortcut).  If 
using a shortcut, please attach the file to this bug report.
4. Please attach your 'mupen64plus.cfg' file to this bug report.

Thanks.

Original comment by richard...@gmail.com on 8 Apr 2012 at 11:09

GoogleCodeExporter commented 9 years ago
Unfortunately, the user did not reply with the necessary information and it was 
not possible to reproduce the problem

Original comment by s...@narfation.org on 18 Dec 2013 at 11:54