Mupen64plus core automatically crashes/hangs regardless of what I do

Using the latest nightly build of RetroArch 64-bit for Windows 7. Downloaded the latest mupen64plus core as well. Tried opening Super Mario 64, as well as checking out any other game available, but it automatically stops working/crashes back to desktop without an explanation when loading a rom. Tried creating and saving in a different configuration, and that still doesn’t work. Made sure all the directories are rightly named, and checked to make sure configuration and system files were put in the right place. Even then, that still didn’t fix the problem.

I’m at a loss here. I can’t seem to figure out why mupen64plus refuses to load in the first place. Any suggestions?

Try launching from a command line with -v or --verbose and it will hopefully tell us a bit more about what’s going on.

So I’ve launched retorarch.exe with the -v command, and I’ve snapped these two logs. One with mupen64plus.ini and one without it.

Right. Sorry for taking so long (other reasons), but here’s a log I’ve gotten from with that verbose command:

C:\RetroArch>retroarch -v rarch_main_init: === Build =======================================RetroArch: rar ch_get_cpu_features: [CPUID]: Vendor: GenuineIntel RetroArch: rarch_get_cpu_features: [CPUID]: Features: MMX MMXEXT SSE SSE2 SSE3 SSSE3 SSE4 SSE4.2 AES AVX☺MMX MMXEXT SSE1 SSE2 SSE3 SSSE3 SSE4 SSE4.2 AVX AES Built: May 18 2015 rarch_main_init: Version: 1.1 rarch_main_init: Git: 1970088 rarch_main_init: ================================================= RetroArch: rarch_get_cpu_features: [CPUID]: Vendor: GenuineIntel RetroArch: rarch_get_cpu_features: [CPUID]: Features: MMX MMXEXT SSE SSE2 SSE3 SSSE3 SSE4 SSE4.2 AES AVX RetroArch: parse_config_file: Loading config from: C:\RetroArch\retroarch.cfg. RetroArch: config_load_core_specific: Loading core-specific config from: C:\RetroArch\config\mupen64plus_libretro.dll.cfg. RetroArch [WARN] :: config_load_core_specific :: Core-specific config not found, reusing last config. RetroArch: load_symbols: Loading dynamic libretro from: “C:\RetroArch\cores\mupen64plus_libretro.dll” RetroArch: rarch_environment_cb: Environ SET_VARIABLES. RetroArch: rarch_verify_api_version: Version of libretro API: 1 RetroArch: rarch_verify_api_version: Compiled against API: 1 RetroArch: rarch_environment_cb: Environ GET_LOG_INTERFACE. RetroArch: rarch_environment_cb: Environ GET_PERF_INTERFACE. RetroArch: rarch_environment_cb: Environ SET_PIXEL_FORMAT: XRGB8888. RetroArch: rarch_environment_cb: Environ GET_RUMBLE_INTERFACE. RetroArch: rarch_get_cpu_features: [CPUID]: Vendor: GenuineIntel RetroArch: rarch_get_cpu_features: [CPUID]: Features: MMX MMXEXT SSE SSE2 SSE3 SSSE3 SSE4 SSE4.2 AES AVX RetroArch: rarch_get_cpu_features: [CPUID]: Vendor: GenuineIntel RetroArch: rarch_get_cpu_features: [CPUID]: Features: MMX MMXEXT SSE SSE2 SSE3 SSSE3 SSE4 SSE4.2 AES AVX RetroArch: load_content: libretro core requires content, but nothing was provided. RetroArch: rarch_environment_cb: Environ SYSTEM_DIRECTORY: “C:\RetroArch\system”. RetroArch: rarch_environment_cb: Environ SYSTEM_DIRECTORY: “C:\RetroArch\system”. RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: ROM Database: C:\RetroArch\system/mupen64plus.ini RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Unable to open rom database file ‘C:\RetroArch\system/mupen64plus.ini’. RetroArch: rarch_log_libretro: [libretro INFO] :: EmuThread: M64CMD_ROM_OPEN RetroArch [ERROR] :: rarch_log_libretro :: [libretro ERROR] :: mupen64plus: Failed to load ROM RetroArch [ERROR] :: rarch_log_libretro :: [libretro ERROR] :: Running Dead N64 Emulator C:\RetroArch>

This is what I get without the mupen64plus.ini filed within my system directory. But with the .ini file in my system directory:

RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: ROM Database: Unknown property on line 5422 (SPAMS THIS LINE TO INFINITY) RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: ROM Database: Unknown property on line 15758 RetroArch: rarch_log_libretro: [libretro INFO] :: EmuThread: M64CMD_ROM_OPEN RetroArch [ERROR] :: rarch_log_libretro :: [libretro ERROR] :: mupen64plus: Failed to load ROM RetroArch [ERROR] :: rarch_log_libretro :: [libretro ERROR] :: Running Dead N64 Emulator C:\RetroArch>

As noted, with the .ini file, it just continuously spams the “unknown property on line XXX” over and over before it crashes.

Like I said, I can’t seem to figure out what the problem is and I’m at a loss at what to do.

I don’t have a mupen64plus.ini, so I don’t think you need one.

As for your log, it doesn’t appear to be loading a ROM, so try adding --menu to your launch line and then choose your core/ROM and see what it says.

[QUOTE=hunterk;23200]I don’t have a mupen64plus.ini, so I don’t think you need one.

As for your log, it doesn’t appear to be loading a ROM, so try adding --menu to your launch line and then choose your core/ROM and see what it says.[/QUOTE]

Alright. I got rid of mupen64plus.ini from the system directory, and tried to load up Super Mario 64 with the latest mupen64plus core. This is what I got:

C:\RetroArch>retroarch --menu RetroArch [WARN] :: config_load_core_specific :: Core-specific config not found, reusing last config. RetroArch [WARN] :: patch_content :: Did not find a valid content patch. RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: ROM Database: C:\RetroArch\system/mupen64plus.ini RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Unable to open rom database file ‘C:\RetroArch\system/mupen64plus.ini’. RetroArch: rarch_log_libretro: [libretro INFO] :: EmuThread: M64CMD_ROM_OPEN RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: SUPER MARIO 64 INI patches applied. RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Goodname: SUPER MARIO 64 RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Headername: SUPER MARIO 64 RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Name: SUPER MARIO 64 RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: MD5: 20B854B239203BAF6C961B850A4A51A2 RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: CRC: 635a2bff 8b022326 RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Imagetype: .v64 (byteswapped) RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Rom size: 8388608 bytes (or 8 Mb or 64 Megabits) RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: ClockRate = f RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Version: 1444 RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Manufacturer: Nintendo RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Cartridge_ID: 4d53 RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Country: USA RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: PC = 80246000 RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Save type: 0 RetroArch: rarch_log_libretro: [libretro INFO] :: EmuThread: M64CMD_ROM_GET_HEADER ReadSpecialSettings: DEFAULT plugin_start_gfx success. RetroArch: rarch_log_libretro: [libretro INFO] :: EmuThread: M64CMD_EXECUTE. RetroArch: rarch_log_libretro: [libretro INFO] :: mupen64plus: Memory initialized Gfx RomOpen. ReadSpecialSettings: DEFAULT ReadSpecialSettings: SUPER MARIO 64 RetroArch: rarch_log_libretro: [libretro INFO] :: Detected RDRAM size: 007fffff C:\RetroArch>

I still don’t know what the hell the problem could be. For the record, I do have a core config file for mupen64plus saved in my config directory.

Well, everything looks fine there. It’s not coughing up an error or anything. Can you try backing up and deleting your retroarch-core-options.cfg file to see if something went wonky with an option somewhere?

Did that and still no good. Still hangs and crashes when trying to load a game.

This is really beginning to piss me off…

Hmm. Yeah, frustrating.

I guess you could try switching from gl to the d3d driver under settings > driver settings. I’ll see if anyone else has any suggestions.

I finally managed to solve the problem.

For some odd reason, unknown to both science and the universe, the emulator crashes if the windowed video scale is set at anything below or above 3x. I changed this setting at first because I didn’t like the windowed output at 3x scale, but its this reason alone why the mupen64plus core kept crashing all along.

So the window scale is set back at its default 3x factor. So whenever I start an N64 game, I immediately press F1 into the rgui and double click to scale into windowed full screen output.

While I have absolutely no problem with this , one question remains: How the hell is the core so unstable that the goddamn thing crashes because of a little video scale change? And why the hell does mupen64plus crash if I try to move the window around my desktop?

Talk about two massive oversights. At least I can finally run the N64 core now.

EDIT: I just make sure my mupen64plus config defaults at full screen when booting up a game now. Much better than having to deal with “windowed full screen” output. Still doesn’t change the fact that this became a problem to begin with.

It doesn’t crash here though…

And yet it did for me.

Problem’s fixed now. I just make sure mupen64plus defaults to full screen instead of windowed when opening up a game, so it doesn’t crash for me.

I’ve had the window-moving crash in Win7 before but I don’t know what causes it. It doesn’t happen in Linux and I don’t know how to debug worth a damn in Windows. Never had any issues with scale factors other than 3x, though.

It’s a bit melodramatic to call an issue no one else has reported or even experienced (as far as we know) “a massive oversight”…

I might’ve been a little melodramatic there, but you can’t really say that I was the only one having these problems. The fact that the window-moving crash on Windows 7 also happened to you means that someone else has reported, or at least experienced these issues.

Note that this only happens with mupen64plus. The other cores I’ve downloaded for NES, SNES, Genesis, Game Boy, and DOSBox, don’t seem to crash in windowed mode. Why mupen64plus has this problem is beyond me.

mupen64plus is a libretro-gl core, which works significantly differently from the various 2D cores. You might see if you have the same issues with the PPSSPP core, which is also libretro-gl.

I have the same issue, still not fixed. Sad.

edit: using x64 retroarch and it works fine.