Bedwyr Posted February 20, 2017 Posted February 20, 2017 This did not happen on a previous 1.4.1 setup. I have savestate set to hotkey activation such that on my XB1 controller, holding down the right stick activates hotkeys and d-pad down saves state. With a game loaded on mupen64plus core only, this crashes Retroarch immediately. Changing savestate slot and loading do not do this. I have tried experimenting with the keyboard commands and get the same behavior. I'll try backing up one more copy of the 1.4.1 directory contents to see if this repeats (a previous 1.4.1 install had different issues). Any known issues? Quote
Bedwyr Posted February 20, 2017 Author Posted February 20, 2017 After looking at a previous backup folder, I noticed that the Mupen64plus core in the new download was about 5MB while the backup core was about 11MB. I copied over the 5MB core and it now saves correctly. Something happen with the online updater maybe? Quote
SentaiBrad Posted February 20, 2017 Posted February 20, 2017 It could have been built to git wrong and published like that on accident. Quote
DOS76 Posted February 20, 2017 Posted February 20, 2017 Your lucky it is working at all currently Mupen64Plus crashes RetroArch on every machine I test it on Quote
SentaiBrad Posted February 20, 2017 Posted February 20, 2017 Yea it sounds like something got messed up in the migration. Quote
Bedwyr Posted February 20, 2017 Author Posted February 20, 2017 (edited) current working dll core backed up to utilities folder. Cause y'never know. I wrote the issue up on the mupen64plus github page. So at least they know. Edited February 20, 2017 by Bedwyr Quote
Zombeaver Posted February 20, 2017 Posted February 20, 2017 Yeah I was testing the mupen64plus core last night... went back to glupen64 pretty quick haha. The mupen64plus one definitely seems to be having some issues in its current state - I was getting crashes on save states and slightly worse performance with identical settings to glupen64. Quote
Bedwyr Posted March 3, 2017 Author Posted March 3, 2017 According to github this issue is now fixed. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.