EFDos / mupengui

Mupen64plus frontend designed based on Elementary OS guidelines.
GNU General Public License v3.0
11 stars 6 forks source link

Crashes on opening any ROM #8

Closed dar5hak closed 5 years ago

dar5hak commented 5 years ago

I'm on Juno, and am unable to start any ROM. A black screen appears with a zoomed-in titlebar, stays for a couple of seconds, and then the MupenGUI window closes.

This happens with or without a game controller connected, with or without the Fullscreen preference turned on.

Launching com.github.efdos.mupengui from the CLI without any arguments produced this output:

JoyAPI Info: Joystick detected: 8Bitdo SN30 GamePad
    8 axis
    16 buttons

JoyAPI Info: Total joysticks detected: 1
M64API Info: Loading Core functions.
M64API Info: Loading Config functions.
M64API Info: Opening Config handles
CoreDebug: Goodname: Mario Kart 64 (E) (V1.1) [!]
CoreDebug: Name: MARIOKART64         
CoreDebug: MD5: 2BB149A583FDEFEA96805F628FE42FD9
CoreDebug: CRC: 2577C7D4 D18FAAAE
CoreDebug: Imagetype: .z64 (native)
CoreDebug: Rom size: 12582912 bytes (or 12 Mb or 96 Megabits)
CoreDebug: Version: 1446
CoreDebug: Manufacturer: Nintendo
CoreDebug: Country: Unknown (0x150)
GFX_PLUGIN M64API Warning: No version number in 'Rice-Video' config section. Setting defaults.
GFX_PLUGIN M64API Warning: Old parameter config version detected : 0, updating to 1;
INPUT_PLUGIN: 1 SDL joysticks were found.
INPUT_PLUGIN M64API Error: No auto-config found for joystick named '8Bitdo SN30 GamePad' in InputAutoConfig.ini
INPUT_PLUGIN: N64 Controller #1: Forcing default keyboard configuration
INPUT_PLUGIN: 1 controller(s) found, 1 plugged in and usable in the emulator
INPUT_PLUGIN M64API Warning: Couldn't open rumble support for joystick #1
INPUT_PLUGIN M64API Warning: Couldn't open rumble support for joystick #2
INPUT_PLUGIN M64API Warning: Couldn't open rumble support for joystick #3
INPUT_PLUGIN M64API Warning: Couldn't open rumble support for joystick #4
INPUT_PLUGIN: Mupen64Plus SDL Input Plugin version 2.5.0 initialized.
RSP_PLUGIN M64API Status: INITIATE RSP
GFX_PLUGIN: SSE processing enabled.
GFX_PLUGIN: ROM (CRC d4c77725aeaa8fd1-50) not found in INI file
GFX_PLUGIN: Enabled hacks for game: 'MARIOKART64'
GFX_PLUGIN: Initializing OpenGL Device Context.
CoreDebug: Setting 32-bit video mode: 640x480
GFX_PLUGIN M64API Warning: Failed to set GL_SWAP_CONTROL to 0. (it's 24)
GFX_PLUGIN M64API Warning: Failed to set GL_BUFFER_SIZE to 32. (it's 24)
GFX_PLUGIN M64API Warning: Failed to set GL_DEPTH_SIZE to 16. (it's 24)
GFX_PLUGIN: Using OpenGL: Intel Open Source Technology Center - Mesa DRI Intel(R) Ivybridge Mobile  : 3.0 Mesa 18.0.5
AUDIO_PLUGIN: Initializing SDL audio subsystem...
INPUT_PLUGIN M64API Warning: Couldn't open rumble support for joystick #1
INPUT_PLUGIN M64API Warning: Couldn't open rumble support for joystick #2
INPUT_PLUGIN M64API Warning: Couldn't open rumble support for joystick #3
INPUT_PLUGIN M64API Warning: Couldn't open rumble support for joystick #4
CoreDebug: Starting R4300 emulator: Dynamic Recompiler
CoreDebug: R4300: starting 64-bit dynamic recompiler at: 0x7fbb05c69860
CoreDebug M64API Error: VidExt_ResizeWindow() called in fullscreen mode.
CoreDebug M64API Error: VidExt_ResizeWindow() called in fullscreen mode.
GFX_PLUGIN M64API Error: Failed to set 32-bit video mode: 640x480
[1]    3540 segmentation fault  com.github.efdos.mupengui

Let me know if I can provide any further information.

EFDos commented 5 years ago

Hello!

It seems the rice-video-plugin crashed for some reason.. Was the fullscreen option enabled when you got this output? If it wasn't, then I might have a bug when managing the settings.. But it shouldn't have crashed the video plugin anyway

Have you tried running it with the different video plugins?

dar5hak commented 5 years ago

Hi!

The fullscreen option was not enabled when I got this output.

Didn't notice the video plugins option, but I am able to play with glide64 and glide64mk2. z64 got stuck on a black screen and arachnoid displayed a cropped video.

Since glide64 works, feel free to close this.

EFDos commented 5 years ago

At the current state, the program is not checking the saved Mupen64Plus options to update the Settings pages, so if you enabled Fullscreen at some other point while testing around, that's probably why it tried to run Fullscreen even though it appeared as disabled.

I'll open a new Issue for that and I'm closing this one since the problem seems to be only related to Mupen64 plugins.