You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS: Win10 (x64)
GLideN64 seems to work when launching using m64py, but when I try to launch using the mupen64plus UI console, a blank window opens but is unresponsive. All of the other video plugins included with m64py seem to work fine when launching with the UI console except for GLideN64.
Here are some of the things I've tried:
*all R4300 modes
*all --emumode launch options (in the mupen64plus UI console)
*disabled OSD (for mupen and GLideN64)
*disabled per-game settings
*all combinations of RSP, input, and audio plugins included in m64py (GLideN64 works with nearly any combination of plugins when launched from m64py)
*disabled FB emulation
*compatibility modes (WinXP,Win7,etc.)
This is typically what the output looks like:
Mupen64Plus Console User-Interface Version 2.5.9
UI-Console: attached to core library 'Mupen64Plus Core' version 2.5.9
UI-Console: Includes support for Dynamic Recompiler.
Core: Using full mem base
Core: Goodname: F-ZERO X (U) [!]
Core: Name: F-ZERO X
Core: MD5: 753437D0D8ADA1D12F3F9CF0F0A5171F
Core: CRC: B30ED978 3003C9F9
Core: Imagetype: .v64 (byteswapped)
Core: Rom size: 16777216 bytes (or 16 Mb or 128 Megabits)
Core: Version: 1449
Core: Manufacturer: 43
Core: Country: USA
UI-Console Status: Cheat codes disabled.
UI-Console: using Video plugin: 'GLideN64' v2.0.0
UI-Console: using Audio plugin: 'Mupen64Plus SDL Audio Plugin' v2.5.9
Input: Using auto-config file at: 'C:\Users\liamg\games\$\emulators\n64\m64py-0.2.5\InputAutoCfg.ini'
UI-Console: using Input plugin: 'Mupen64Plus SDL Input Plugin' v2.5.9
UI-Console: using RSP plugin: 'Hacktarux/Azimer High-Level Emulation RSP Plugin' v2.5.9
Core: input plugin did not specify a render callback; there will be no on screen display by the input plugin.
Input: 0 SDL joysticks were found.
Input: N64 Controller #1: Forcing default keyboard configuration
Input: Using auto-config file at: 'C:\Users\liamg\games\$\emulators\n64\m64py-0.2.5\InputAutoCfg.ini'
Input: 1 controller(s) found, 1 plugged in and usable in the emulator
Input Warning: Couldn't open rumble support for joystick #1
Input Warning: Couldn't open rumble support for joystick #2
Input Warning: Couldn't open rumble support for joystick #3
Input Warning: Couldn't open rumble support for joystick #4
Input: Mupen64Plus SDL Input Plugin version 2.5.9 initialized.
RSP: RSP Fallback disabled !
Core: Using video capture backend: dummy
Core: Game controller 0 (Standard controller) has a Memory pak plugged in
Core: Game controller 1 (Standard controller) has a Memory pak plugged in
Core: Game controller 2 (Standard controller) has a Memory pak plugged in
Core: Game controller 3 (Standard controller) has a Memory pak plugged in
Core: Using CIC type X106
Core: Setting video mode: 800x600
Surely I'm doing something wrong, but I just really don't want to have to rely on a frontend to use GLideN64. Any help with this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
OS: Win10 (x64)
GLideN64 seems to work when launching using m64py, but when I try to launch using the mupen64plus UI console, a blank window opens but is unresponsive. All of the other video plugins included with m64py seem to work fine when launching with the UI console except for GLideN64.
Here are some of the things I've tried:
*all R4300 modes
*all --emumode launch options (in the mupen64plus UI console)
*disabled OSD (for mupen and GLideN64)
*disabled per-game settings
*all combinations of RSP, input, and audio plugins included in m64py (GLideN64 works with nearly any combination of plugins when launched from m64py)
*disabled FB emulation
*compatibility modes (WinXP,Win7,etc.)
This is typically what the output looks like:
Mupen64Plus Console User-Interface Version 2.5.9
Surely I'm doing something wrong, but I just really don't want to have to rely on a frontend to use GLideN64. Any help with this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered: