mupen64plus / mupen64plus-ui-python Goto Github PK
View Code? Open in Web Editor NEWA frontend for Mupen64Plus
Home Page: http://m64py.sourceforge.net/
License: GNU General Public License v3.0
A frontend for Mupen64Plus
Home Page: http://m64py.sourceforge.net/
License: GNU General Public License v3.0
This is not a bug but a feature request.
Due to the amount of python and qt5 files, it would be greate to move all this files in a separate folder to get a better overview in the root of the application folder (like a system or core folder).
When i change the key bindings in settings>plugins>input>configure they are not saved.
My changes are always reverted to default.
How about a "save as..." button for the input config?
Trying to run on ARM (odroid u3, Mali 400, lubuntu 14.04)
Traceback (most recent call last):
File "/usr/games/m64py", line 57, in <module>
from m64py.frontend.mainwindow import MainWindow
File "/usr/share/m64py/m64py/frontend/mainwindow.py", line 30, in <module>
from m64py.frontend.worker import Worker
File "/usr/share/m64py/m64py/frontend/worker.py", line 27, in <module>
from m64py.core.core import Core
File "/usr/share/m64py/m64py/core/core.py", line 32, in <module>
from m64py.core.vidext import vidext
File "/usr/share/m64py/m64py/core/vidext.py", line 36, in <module>
from m64py.SDL import SDL_WasInit, SDL_InitSubSystem, SDL_QuitSubSystem, SDL_INIT_VIDEO
File "/usr/share/m64py/m64py/SDL/__init__.py", line 30, in <module>
from .dll import private_function, function
File "/usr/share/m64py/m64py/SDL/dll.py", line 226, in <module>
_dll = SDL_DLL('SDL', 'SDL_Linked_Version')
File "/usr/share/m64py/m64py/SDL/dll.py", line 59, in __init__
_platform_library_name(library_name))
ImportError: Dynamic library "libo" was not found
Any idea?
The Cheats dialog only allows for two levels of nesting, seen in the hardcoded v. checks in frontend/cheat.py. If arbitrary levels of nesting were supported, that would be great.
It was working then suddenly nothing happened these errors:
M64Py - A frontend for Mupen64Plus version 0.2.1
Frontend: INFO: ScreenSaver not available: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ScreenSaver was not provided by any .service files
Frontend: INFO: No OpenGL_accelerate module loaded: No module named OpenGL_accelerate
Frontend: INFO: Unable to load registered array format handler numeric:
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/OpenGL/arrays/formathandler.py", line 35, in loadPlugin
plugin_class = entrypoint.load()
File "/usr/lib64/python2.7/site-packages/OpenGL/plugins.py", line 14, in load
return importByName( self.import_path )
File "/usr/lib64/python2.7/site-packages/OpenGL/plugins.py", line 28, in importByName
module = import( ".".join(moduleName), {}, {}, moduleName)
File "/usr/lib64/python2.7/site-packages/OpenGL/arrays/numeric.py", line 15, in
raise ImportError( """No Numeric module present: %s"""%(err))
ImportError: No Numeric module present: No module named Numeric
Frontend: INFO: Unable to load registered array format handler vbo:
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/OpenGL/arrays/formathandler.py", line 35, in loadPlugin
plugin_class = entrypoint.load()
File "/usr/lib64/python2.7/site-packages/OpenGL/plugins.py", line 14, in load
return importByName( self.import_path )
File "/usr/lib64/python2.7/site-packages/OpenGL/plugins.py", line 28, in importByName
module = import( ".".join(moduleName), {}, {}, moduleName)
File "/usr/lib64/python2.7/site-packages/OpenGL/arrays/vbo.py", line 33, in
from OpenGL import GL
ImportError: cannot import name GL
Frontend: INFO: Unable to load registered array format handler vbooffset:
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/OpenGL/arrays/formathandler.py", line 35, in loadPlugin
plugin_class = entrypoint.load()
File "/usr/lib64/python2.7/site-packages/OpenGL/plugins.py", line 14, in load
return importByName( self.import_path )
File "/usr/lib64/python2.7/site-packages/OpenGL/plugins.py", line 28, in importByName
module = import( ".".join(moduleName), {}, {}, moduleName)
File "/usr/lib64/python2.7/site-packages/OpenGL/arrays/vbo.py", line 33, in
from OpenGL import GL
ImportError: cannot import name GL
Frontend: INFO: attached to library 'Mupen64Plus Core' version 2.0.0
Frontend: INFO: includes support for Dynamic Recompiler.
Frontend: INFO: video extension enabled
Traceback (most recent call last):
File "/usr/bin/m64py", line 83, in
main()
File "/usr/bin/m64py", line 68, in main
window = MainWindow((opts, args))
File "/usr/lib64/python2.7/site-packages/m64py/frontend/mainwindow.py", line 88, in init
self.worker.init()
File "/usr/lib64/python2.7/site-packages/m64py/frontend/worker.py", line 56, in init
self.plugins_load()
File "/usr/lib64/python2.7/site-packages/m64py/frontend/worker.py", line 143, in plugins_load
self.core.plugin_load_try(plugin_path)
File "/usr/lib64/python2.7/site-packages/m64py/core/core.py", line 222, in plugin_load_try
plugin_handle = C.cdll.LoadLibrary(plugin_path)
File "/usr/lib64/python2.7/ctypes/init.py", line 443, in LoadLibrary
return self._dlltype(name)
File "/usr/lib64/python2.7/ctypes/init.py", line 365, in init
self._handle = _dlopen(self._name, mode)
OSError: libboost_filesystem-1_49.so.1.49.0: cannot open shared object file: No such file or directory
I was experimenting with the core mupen64plus and then I discovered this ui! It was working great for me. I experimented with a few different versions. I moved the app around to different folders and fairly quickly the links to the various dylibs were wiped. I was able to input them all correctly (I think), except I chose the wrong file for the first library. Now every time I launch the app, it just closes immediately. I was just curious where I could go to edit the file that I mislinked? Without being able to change it or remove it from my system, I have no idea how to use the app anymore (other than a complete system reinstall).
I'm on OS X. I imagine there's just a config somewhere that is linking that file. I checked the ~/.config folder and I saw it linking to everything except for the first one that is called library I think. Anyway, I even tried deleting the mupen64 folder inside of .config and it was to no avail. When it was recreated, the linking issue stood so I couldn't launch the app.
I think this would be helpful for others if they should make the mistake of linking the wrong file like I did (which I'm not 100% sure what the right one is but if I could edit it then I could at least do some trial and error).
FYI: There is some discussions involving m64py
https://groups.google.com/d/msg/mupen64plus/HeeSGSh3ie8/IXohUD8PiX4J
I guess related problems will appear in the future:
I've isolated the source of the problem. The SSSE3 version of the cx4d RSP plugin. Old version gave dips to 40Hz during intro. (Core Quad @ 3.2Ghz) New version dips to 30Hz. SSE2 version stays at 50Hz during intro. Factor 5 games are notoriously RSP-heavy. The other versions of the RSP plugin don't seem to be affected. On another note, m64py really doesn't like the new binaries. Emulator boots just fine, but then pressing any input will freeze the emulator. Also, m64py refuses to work with the 64 bit binaries. But this is likely normal. The mupen64plus-QT frontend isn't affected, IMO because it's just a command line-based front-end.
I don't have the details, feel free to close the ticket if this is not relevant. :)
python --version
Python 3.5.1
m64py from git.
To reproduce the problem you simply have to select the controller device in the input plugin window and close it.
python setup.py build_qt && ./m64py
with no starting mupen64plus.cfg
Unhandled Python exception
Now running with ipython m64py
Traceback (most recent call last):
File "/home/oiu7/mupen64plus-ui-python/src/m64py/frontend/input.py", line 62, in closeEvent
self.save_config()
File "/home/oiu7/mupen64plus-ui-python/src/m64py/frontend/input.py", line 136, in save_config
self.save_opts()
File "/home/oiu7/mupen64plus-ui-python/src/m64py/frontend/input.py", line 244, in save_opts
self.config.set_parameter("name", devicename.encode())
AttributeError: 'bytes' object has no attribute 'encode'
If you suspect this is an IPython bug, please report it at:
https://github.com/ipython/ipython/issues
or send an email to the mailing list at [email protected]
You can print a more detailed traceback right now with "%tb", or use "%debug"
to interactively debug it.
Extra-detailed tracebacks for bug-reporting purposes can be enabled via:
%config Application.verbose_crash=True
Traceback (most recent call last):
File "/usr/bin/ipython", line 5, in
start_ipython()
File "/usr/lib/python3.5/site-packages/IPython/init.py", line 118, in start_ipython
return launch_new_instance(argv=argv, *_kwargs)
File "/usr/lib/python3.5/site-packages/traitlets/config/application.py", line 591, in launch_instance
app.initialize(argv)
File "", line 2, in initialize
File "/usr/lib/python3.5/site-packages/traitlets/config/application.py", line 75, in catch_config_error
return method(app, *args, *_kwargs)
File "/usr/lib/python3.5/site-packages/IPython/terminal/ipapp.py", line 320, in initialize
self.init_code()
File "/usr/lib/python3.5/site-packages/IPython/core/shellapp.py", line 299, in init_code
sys.stderr.flush()
running with gdb python and the run m64py:
Unhandled Python exception
Program received signal SIGABRT, Aborted.
0x00007ffff737f5f8 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0 0x00007ffff737f5f8 in raise () from /usr/lib/libc.so.6
#1 0x00007ffff7380a7a in abort () from /usr/lib/libc.so.6
#2 0x00007ffff50261e1 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5
#3 0x00007fffec653081 in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtCore.so
#4 0x00007fffec94ea76 in ?? () from /usr/lib/python3.5/site-packages/sip.so
#5 0x00007ffff63c31b2 in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtWidgets.so
#6 0x00007ffff5b4f9c8 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5
#7 0x00007ffff63c25fb in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtWidgets.so
#8 0x00007ffff5b0c9ac in QApplicationPrivate::notify_helper(QObject_, QEvent_) () from /usr/lib/libQt5Widgets.so.5
#9 0x00007ffff5b11e86 in QApplication::notify(QObject_, QEvent_) () from /usr/lib/libQt5Widgets.so.5
#10 0x00007ffff63dd09e in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtWidgets.so
#11 0x00007ffff5219bab in QCoreApplication::notifyInternal(QObject_, QEvent_) () from /usr/lib/libQt5Core.so.5
#12 0x00007ffff5b4acad in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /usr/lib/libQt5Widgets.so.5
#13 0x00007ffff5b4e672 in ?? () from /usr/lib/libQt5Widgets.so.5
#14 0x00007ffff524831a in QMetaObject::activate(QObject_, int, int, void_) () from /usr/lib/libQt5Core.so.5
#15 0x00007ffff5ea75f2 in QAbstractButton::clicked(bool) () from /usr/lib/libQt5Widgets.so.5
#16 0x00007ffff5c09a94 in ?? () from /usr/lib/libQt5Widgets.so.5
#17 0x00007ffff5c0b0a9 in ?? () from /usr/lib/libQt5Widgets.so.5
#18 0x00007ffff5c0b224 in QAbstractButton::mouseReleaseEvent(QMouseEvent) () from /usr/lib/libQt5Widgets.so.5
#19 0x00007ffff63abb2b in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtWidgets.so
#20 0x00007ffff5b4f9c8 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5
#21 0x00007ffff63ac84b in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtWidgets.so
#22 0x00007ffff5b0c9ac in QApplicationPrivate::notify_helper(QObject_, QEvent_) () from /usr/lib/libQt5Widgets.so.5
#23 0x00007ffff5b12589 in QApplication::notify(QObject_, QEvent_) () from /usr/lib/libQt5Widgets.so.5
#24 0x00007ffff63dd09e in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtWidgets.so
#25 0x00007ffff5219bab in QCoreApplication::notifyInternal(QObject_, QEvent_) () from /usr/lib/libQt5Core.so.5
#26 0x00007ffff5b11492 in QApplicationPrivate::sendMouseEvent(QWidget_, QMouseEvent_, QWidget_, QWidget_, QWidget**, QPointer&, bool) () from /usr/lib/libQt5Widgets.so.5
#27 0x00007ffff5b69f3b in ?? () from /usr/lib/libQt5Widgets.so.5
#28 0x00007ffff5b6c4fb in ?? () from /usr/lib/libQt5Widgets.so.5
#29 0x00007ffff5b0c9ac in QApplicationPrivate::notify_helper(QObject_, QEvent_) () from /usr/lib/libQt5Widgets.so.5
#30 0x00007ffff5b11e86 in QApplication::notify(QObject_, QEvent_) () from /usr/lib/libQt5Widgets.so.5
#31 0x00007ffff63dd09e in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtWidgets.so
#32 0x00007ffff5219bab in QCoreApplication::notifyInternal(QObject_, QEvent_) () from /usr/lib/libQt5Core.so.5
#33 0x00007ffff555a5f1 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) ()
from /usr/lib/libQt5Gui.so.5
#34 0x00007ffff555c2b5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) ()
from /usr/lib/libQt5Gui.so.5
#35 0x00007ffff55416d8 in QWindowSystemInterface::sendWindowSystemEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /usr/lib/libQt5Gui.so.5
#36 0x00007fffeb8ec8c0 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#37 0x00007ffff46fadc7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#38 0x00007ffff46fb020 in ?? () from /usr/lib/libglib-2.0.so.0
#39 0x00007ffff46fb0cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
---Type to continue, or q to quit---
#40 0x00007ffff527054f in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQt5Core.so.5
#41 0x00007ffff521757a in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQt5Core.so.5
#42 0x00007ffff521f53c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#43 0x00007ffff63db9db in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtWidgets.so
#44 0x00007ffff79bca89 in PyCFunction_Call () from /usr/lib/libpython3.5m.so.1.0
#45 0x00007ffff7a34a01 in PyEval_EvalFrameEx () from /usr/lib/libpython3.5m.so.1.0
#46 0x00007ffff7a35df2 in ?? () from /usr/lib/libpython3.5m.so.1.0
#47 0x00007ffff7a35ed3 in PyEval_EvalCodeEx () from /usr/lib/libpython3.5m.so.1.0
#48 0x00007ffff7a35efb in PyEval_EvalCode () from /usr/lib/libpython3.5m.so.1.0
#49 0x00007ffff7a55074 in ?? () from /usr/lib/libpython3.5m.so.1.0
#50 0x00007ffff7a57585 in PyRun_FileExFlags () from /usr/lib/libpython3.5m.so.1.0
#51 0x00007ffff7a576f6 in PyRun_SimpleFileExFlags () from /usr/lib/libpython3.5m.so.1.0
#52 0x00007ffff7a6e504 in Py_Main () from /usr/lib/libpython3.5m.so.1.0
#53 0x0000000000400af7 in main ()
Manual import from http://sourceforge.net/p/m64py/tickets/19/
Installing the RPM in Fedora 20 x86_64 and there are multiple dependency issues.
I have the right roms according to datomatic.no-intro.org, same md5, but some of them are showing like bad dump, overdump or even hack translation:
1080 Snowboarding (JU) (M2) [f2][b1] , but md5 = 18381c8f37e2b29f5940eea9b5f96814
Legend of Zelda, The - Majora's Mask (U) [T-Rus0.50_Alex], but md5 = b0cc37a45bc1b6c76cd7f0b71fe2bb1f (man, I even know russian...)
Super Smash Bros. (U) [hI], but md5 = 3c4e65d9b7bf55338496108f04da7f41
And some without snapshot (but there are in /src/m64py/ui/snaphot/):
Banjo-Kazooie (U) (V1.1) [!]
Kirby 64 - The Cristal Shards (U) [!]
Pokemon Stadium 2 (U) [!]
Star Fox 64 (U) (V1.1) [!]
So I've tried compiling the other components from this repo, and they all worked fine, except the python front-end, here's what I get when I try to do what the instructions lead me to:
$ python setup.py installrunning install
running build
running build_qt
error: [Errno 2] No such file or directory
Am I missing some package?
Manual import from http://sourceforge.net/p/m64py/tickets/13/
@ssokolow wrote:
When trying to configure my joysticks, I found the input configuration far too sensitive and, in the end, found it MUCH easier to just stumble around enough to get a feel for the keywords written to the config file and then manually edit the file.
Rather than relying on the dead zone configuration (nonexistant under evdev, either broken or cripplingly fragile under joydev), I think it'd make much more sense for the input configurator to only accept an axis measurement as intended if it exceeds 50% of the axis's range in that direction.
That would also make it MUCH easier to ensure that, when I press a stick horizontally, it won't be mis-detected as vertical movement (or vice-versa) due to a bit of initial imprecision when pushing the stick.
Ubuntu 14.04 doesn't seem to support libboost1.46 anymore. Tried to install it instead of 1.54 but that doesn't seems to work. As a result trying to startup the interface results in the following error.
OSError: libboost_filesystem.so.1.46.1: cannot open shared object file: No such file or directory
Is there a way to bypass this?
Regards
Rand1-1000
ok so here's my dilema. Im trying to get m64py to save my manual controller config but it seems to not like me because it keeps reverting to auto config as soon as i leave controller input configuration. im using a snakebyte usb ps3 controller v1.1 ive looked through as many forums as i could find but im still coming up empty. also just to clarify ive tried to change the settings in autoconfig.ini except i cant seem to find it i look for my mupen64plus folder under /usr/share/ and all i find is m64py is it possible any one can help me because i take pride in my intellegence and right now i feel like a total imbecile
I downloaded the newest version of GlideN64 from emucr.
The issue is that M64Py is accessing a memory section which is invalid.
So if the user selects GlideN64 as gpu plugin and start a rom, the screen turns for a moment black and returns to M64Py splash screen. The log shows that an invalid memory access occurred.
I will post the log as soon as I have time.
If a custom resolution is specified in mupen64plus.cfg
located in the Windows AppData folder with either ScreenWidth
or ScreenHeight
and any of M64Py's Settings dialogues are opened, the custom resolution is reset. If a game is launched without opening any settings, the custom resolution is used as expected.
An example reproduction of this issue would be to change ScreenWidth
to 854
and ScreenHeight
to 480
, launch M64Py, select Settings
> Paths
, close the window and launch a game.
on freebsd
i have installed
devel/sdl20
devel/py-qt4
, the dependencies needed in order to install m64py
next i Run python setup.py install to install
just below the result :
"
Traceback (most recent call last):
File "setup.py", line 19, in
from m64py.core.defs import FRONTEND_VERSION
File "/mupen64plus-ui-python-master/src/m64py/core/defs.py", line 19, in
from m64py.platform import DLL_EXT
ImportError: cannot import name DLL_EXT
"
could you help ?
First of all, great work! This frontend should definitely be more popular.
On windows, most emulators have portable downloads instead of installers. It would be nice if this frontend also has a portable release version.
This is all I get from m64py. Even when I set the correct path in the configuration file and everything. I'm on the latest release.
An old ~/.config/m64py/m64py.conf. Can cause following crash:
__ __ __ _ _ ____ _
| \/ |_ _ _ __ ___ _ __ / /_ | || | | _ \| |_ _ ___
| |\/| | | | | '_ \ / _ \ '_ \| '_ \| || |_| |_) | | | | / __|
| | | | |_| | |_) | __/ | | | (_) |__ _| __/| | |_| \__ \
|_| |_|\__,_| .__/ \___|_| |_|\___/ |_| |_| |_|\__,_|___/
|_|
M64Py - A frontend for Mupen64Plus version 0.2.1
Frontend: INFO: No OpenGL_accelerate module loaded: No module named OpenGL_accelerate
Frontend: INFO: Unable to load registered array format handler numeric:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/formathandler.py", line 35, in loadPlugin
plugin_class = entrypoint.load()
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 14, in load
return importByName( self.import_path )
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 28, in importByName
module = __import__( ".".join(moduleName), {}, {}, moduleName)
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/numeric.py", line 15, in <module>
raise ImportError( """No Numeric module present: %s"""%(err))
ImportError: No Numeric module present: No module named Numeric
Frontend: INFO: Unable to load registered array format handler vbo:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/formathandler.py", line 35, in loadPlugin
plugin_class = entrypoint.load()
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 14, in load
return importByName( self.import_path )
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 28, in importByName
module = __import__( ".".join(moduleName), {}, {}, moduleName)
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/vbo.py", line 33, in <module>
from OpenGL import GL
ImportError: cannot import name GL
Frontend: INFO: Unable to load registered array format handler vbooffset:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/formathandler.py", line 35, in loadPlugin
plugin_class = entrypoint.load()
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 14, in load
return importByName( self.import_path )
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 28, in importByName
module = __import__( ".".join(moduleName), {}, {}, moduleName)
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/vbo.py", line 33, in <module>
from OpenGL import GL
ImportError: cannot import name GL
Traceback (most recent call last):
File "/usr/bin/m64py", line 83, in <module>
main()
File "/usr/bin/m64py", line 68, in main
window = MainWindow((opts, args))
File "/usr/share/m64py/m64py/frontend/mainwindow.py", line 82, in __init__
int(self.settings.qset.value("enable_vidext", 1)))
ValueError: invalid literal for int() with base 10: 'true'
The workaround is to delete ~/.config/m64py/m64py.conf - but this shoudn't happen in the first place. All settings.qset with string conversion have to be protected using try-except to avoid this problem
Alright, first of all, nice interface. I am really enjoying this very much, now here's the issue I am currently experiencing. With m64py It detects my 360 controller and when I go to set it as the controller I want to use for port 1 and then I load a rom it reverts automatically back to keyboard and mouse. Now I've tried running it as administrator (windows 7 sp1) and tried to set the controller port to use the 360 controller, again running (which still reverts) and then by setting, and closing the application and then reopening the app, which also does not seem to work.
Right now it seems I can't use my 360 controller to use this nice frontend for mupen64plus.
Does someone have a proper mapping for the PS4 Dualshock? I started editing InputAutoCfg.ini
in /Applications/M64Py.app/Contents/Resources/InputAutoCfg.ini
on Mac OS X with M64Py 0.2.3
but the changes are not applied.
$ lsusb
Bus 029 Device 007: ID 054c:05c4 Sony Corporation Wireless Controller
[PLAYSTATION(R)4 Controller]
[Sony PLAYSTATION(R)4 Controller]
[Sony Computer Entertainment Wireless Controller]
[Sony Corporation Wireless Controller]
[Wireless Controller]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
DPad R = button(5)
DPad L = button(7)
DPad D = button(6)
DPad U = button(4)
Start = button(3)
Z Trig = button(10)
B Button = button(15)
A Button = button(14)
C Button R = axis(2+)
C Button L = axis(2-)
C Button D = axis(3+)
C Button U = axis(3-)
R Trig = button(11)
L Trig = button(8)
Mempak switch =
Rumblepak switch =
X Axis = axis(0-,0+)
Y Axis = axis(1-,1+)
os x 10.9.4
downloaded mupen64plus-bundle-osx-2.0
downloaded m64py-0.2.1
both in a random folder .. also have zelda ocarina of time [n64] in the folder, this is what i am trying to launch
i can open m64py
the FILE and EMULATION menus are all faded/unclickable, so i cant simply OPEN ROM
under settings/paths i have no idea where to look for files or choose which directory
I'm running ubuntu GNOME 16.04 and when I try to run m64py I get the error:
Frontend: INFO: ScreenSaver not available: No module named dbus
Frontend: INFO: No OpenGL_accelerate module loaded: No module named OpenGL_accelerate
Frontend: INFO: Unable to load registered array format handler numeric:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/formathandler.py", line 35, in loadPlugin
plugin_class = entrypoint.load()
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 14, in load
return importByName( self.import_path )
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 28, in importByName
module = __import__( ".".join(moduleName), {}, {}, moduleName)
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/numeric.py", line 15, in <module>
raise ImportError( """No Numeric module present: %s"""%(err))
ImportError: No Numeric module present: No module named Numeric
Frontend: INFO: Unable to load registered array format handler vbo:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/formathandler.py", line 35, in loadPlugin
plugin_class = entrypoint.load()
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 14, in load
return importByName( self.import_path )
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 28, in importByName
module = __import__( ".".join(moduleName), {}, {}, moduleName)
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/vbo.py", line 33, in <module>
from OpenGL import GL
ImportError: cannot import name GL
Frontend: INFO: Unable to load registered array format handler vbooffset:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/formathandler.py", line 35, in loadPlugin
plugin_class = entrypoint.load()
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 14, in load
return importByName( self.import_path )
File "/usr/lib/python2.7/dist-packages/OpenGL/plugins.py", line 28, in importByName
module = __import__( ".".join(moduleName), {}, {}, moduleName)
File "/usr/lib/python2.7/dist-packages/OpenGL/arrays/vbo.py", line 33, in <module>
from OpenGL import GL
ImportError: cannot import name GL
Segmentation fault (core dumped)
Manual import from http://sourceforge.net/p/m64py/discussion/general/thread/c5d52139/
@legluondunet wrote:
hello,
I have 37 n64 roms in my folder and m64py can count them.
But it does not show all of them in the list:
https://lh3.googleusercontent.com/-NtFlVgVhO3M/Uq9dAms6eVI/AAAAAAAAARs/C1-Nf3VBvuA/w850-h692-no/Capture+d%2527%25C3%25A9cran+de+2013-12-16+19%253A59%253A50.png
thank you for your help.
LGDN.
"Disable ScreenSaver" does not work with Xfce.
M64Py git version, Xubuntu 14.04, 64 bits.
For example, I can use H or J keys but not G or X. m64py accepts any key when I press but just doesn't save the choice for some of them.
Mupen64Plus 2.5, m64py 0.2.3 (tried both with --sdl2 and without).
It seems the settings from the mupen64plus.cfg files are not detected and set properly.
If a user tries to change the controller configuration from Manual to Automatic, M64Py doesn't save this change to the cfg.
Also a feature to map multiple buttons to the N64 Controller would be good.
2 major issues with Xbox 360 controllers on windows
Manual import from http://sourceforge.net/p/m64py/tickets/17/
@bentley wrote:
In m64py 0.2.1 with default plugins on OpenBSD, along with mupen64plus-2.0 installed from packages, double-clicking to change to/from fullscreen causes a crash within Rice.
Is this a bug in m64py or in the Rice plugin itself?
(gdb) bt full
#0 strstr (s=0x0, find=0x31107fb452 "L_ARB_fragment_program")
at /usr/src/lib/libc/string/strstr.c:49
c = 71 'G'
sc = 22 '\026'
len = 22
#1 0x0000003110658710 in COGLGraphicsContext::IsExtensionSupported (this=Variable "this" is not available.
)
at ../../src/OGLGraphicsContext.cpp:344
No locals.
#2 0x0000003110649be1 in OGLDeviceBuilder::CreateColorCombiner (
this=0x30e2830680, pRender=0x30db6e3a00) at ../../src/DeviceBuilder.cpp:261
maxUnit = 2
pcontext = (COGLGraphicsContext *) 0x30e3e6b600
#3 0x000000311065feb7 in CRender (this=0x30db6e3a00)
at ../../src/Render.cpp:107
No locals.
#4 0x000000311065aeb9 in OGLRender (this=0x30db6e3a00)
at ../../src/OGLRender.cpp:48
No locals.
#5 0x0000003110649a95 in OGLDeviceBuilder::CreateRender (this=0x30e2830680)
at OGLExtRender.h:43
No locals.
#6 0x00000031106f8de3 in UpdateScreen () at ../../src/Video.cpp:149
lastTick = 0
frames = 0
#7 0x000000310783a591 in gen_interupt () at ../../src/r4300/interupt.c:382
No locals.
#8 0x00000030dad4475d in ?? ()
No symbol table info available.
#9 0x0000000000000000 in ?? ()
No symbol table info available.
Qt4 isn't maintained anymore since over a year. So please switch to Qt5 to make it possible to ship it in the future distributions.
It seems that some distributions (Debian) are already planning to drop Qt4: http://perezmeyer.blogspot.de/2014/09/qt5-in-jessie-we-will-release-with-532.html
I installed the newest M64py version.
Currently I am struggling with some issues concerning the settings.
Independent of the plugin, the settings are always different.
Means a special option is sometimes on top of the setting screen and other times at the bottom.
Furthermore the screensize of the option window is after some changes always very small.
So the size of the window is not stored.
Manual sync from http://sourceforge.net/p/m64py/discussion/general/thread/0ff958ff/
So I'm using a Dualshock 4 controller. I tried to run it both with SCP Server (which makes the Dualshock controller get recognized as a 360 controller) and without SCP Server. Well for one thing, the button inputs aren't right at all. The A button is bound to L3, the D-Pad Down button is bound to X, and the actual D-pad doesn't seem to work. Of course, that's the input plugin's fault, but when I try to change the input settings via the UI, I select the gamepad, and whenever I click on the buttons to change the mappings, one of two things happens:
The instant I click on it, the button mapping I choose immediately changes to "axis(0-)"
Or, it lets me press a button, but any button I press shows up as "axis(0-)"
the mupen64plus cli works fine though
Frontend: WARNING: Incompatible version of OpenGL_accelerate found, need at least (3, 1, 0) found (3, 0, 2)
Frontend: INFO: No OpenGL_accelerate module loaded: Old version of OpenGL_accelerate
Traceback (most recent call last):
File "/usr/bin/m64py", line 83, in <module>
main()
File "/usr/bin/m64py", line 67, in main
from m64py.frontend.mainwindow import MainWindow
File "/usr/lib/python2.7/site-packages/m64py/frontend/mainwindow.py", line 28, in <module>
from m64py.frontend.worker import Worker
File "/usr/lib/python2.7/site-packages/m64py/frontend/worker.py", line 28, in <module>
from m64py.core.core import Core
File "/usr/lib/python2.7/site-packages/m64py/core/core.py", line 31, in <module>
from m64py.core.vidext import vidext
File "/usr/lib/python2.7/site-packages/m64py/core/vidext.py", line 37, in <module>
from m64py.SDL import SDL_WasInit, SDL_InitSubSystem, SDL_QuitSubSystem, SDL_INIT_VIDEO
File "/usr/lib/python2.7/site-packages/m64py/SDL/__init__.py", line 32, in <module>
from .audio import *
File "/usr/lib/python2.7/site-packages/m64py/SDL/audio.py", line 11, in <module>
from .array import SDL_array, to_ctypes
File "/usr/lib/python2.7/site-packages/m64py/SDL/array.py", line 50, in <module>
_import_arrays(_array_names, locals())
File "/usr/lib/python2.7/site-packages/m64py/SDL/array.py", line 20, in _import_arrays
c_ubyte: array.uint8,
AttributeError: 'module' object has no attribute 'uint8'
When "Enable Video Extension" is checked, I get black screen (sometimes turning white) instead of proper video rendering.
There's a log line that may be important:
QOpenGLContext::swapBuffers() called with non-exposed window, behavior is undefined
When "Enable Video Extension" is turned off, the rendering is properly done in new window.
Video: Using OpenGL: NVIDIA Corporation - GeForce GTS 250/PCIe/SSE2 : 3.3.0 NVIDIA 340.76
Mupen64Plus 2.5, m64py 0.2.3, python-qt5 5.4, qt5 5.4.1. Linux, 32 bit.
Currently the 0.2.3 release (using the installer for windows 7) Does not execute at all. Loaded up task manager and even ran it via command line but showing no running process at all. Going to /try/ running the portable zip release.
EDIT: Same thing with the portable release. Nothing is running in the task manager
Currently m64py doesn't work with x64 builds.
Due to the SDL2 change, there are only x64 builds available.
If a user exchanges the files of m64py with an x64build of Mupen64plus, the emulator won't load any rom or m64py won't boot at all.
Hi i just got an Retrolink N64 Controller but when i try to map the controlls C buttons and the joystick wont map. It works fine on a PC.
vita@GNUvita ~/Escritorio/mupen64plus-ui-python-master $ python setup.py installrunning install
running build
running build_qt
Traceback (most recent call last):
File "setup.py", line 380, in
("share/applications", ["xdg/m64py.desktop"]),
File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/usr/lib/python2.7/distutils/command/install.py", line 601, in run
self.run_command('build')
File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "setup.py", line 344, in run
self.run_command("build_qt")
File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "setup.py", line 63, in run
self.compile_ui(join(dirpath, filename))
File "setup.py", line 34, in compile_ui
from PyQt5 import uic
ImportError: No module named PyQt5
vita@GNUvita ~/Escritorio/mupen64plus-ui-python-master $ python setup.py build_qt
running build_qt
Traceback (most recent call last):
File "setup.py", line 380, in
("share/applications", ["xdg/m64py.desktop"]),
File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "setup.py", line 63, in run
self.compile_ui(join(dirpath, filename))
File "setup.py", line 34, in compile_ui
from PyQt5 import uic
ImportError: No module named PyQt5
I have every package needed, including -dev packages.
m64py crashes with a Unhandled Python exception error when I select my joystick in the device section in the Mupen64Plus SDL Input plugin window and then click on close.
m64py 0.2.3-5
mupen64plus 2.5-2
archlinux.
I am using an original ps2 controller with a ps2tousb adapter. The controller works fine.
I patched m64py to include this commit.
https://github.com/alexhenrie/mupen64plus-ui-python/commit/6179216d898b7858b8c1a589ffebd50c504406d9
followup:
http://code.google.com/p/mupen64plus/issues/detail?id=198
I'd like to suggest adding some debugging features like breakpoints and other stuff for cheat-making.
M64py will not start, nor will it start when a rom is right clicked used the option open with m64py. Ubuntu 14.04
OSError: libboost_filesystem.so.1.46.1: cannot open shared object file: No such file or directory
eric@eric-GA-990FXA-UD7:/usr/lib/x86_64-linux-gnu$ ldconfig -p | grep libboost_filesystem.so
libboost_filesystem.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.54.0
On 10.10.2, m64py opens its window, but the menus remain for whatever app was previously running. Clicking on the finder (or any non-m64py window) and then back to m64py fixes this issue.
Maybe related, or maybe not, but when I launch a game, m64py plays the audio, but draws no graphics. When I run with mupen64plus on the same machine, it seems to work fine.
Core: Goodname: Legend of Zelda, The - Ocarina of Time (U) (V1.0) [!]
Core: Name: THE LEGEND OF ZELDA
Core: MD5: 5BD1FE107BF8106B2AB6650ABECD54D6
Core: CRC: ec7011b7 7616d72b
Core: Imagetype: .v64 (byteswapped)
Core: Rom size: 33554432 bytes (or 32 Mb or 256 Megabits)
Core: Version: 1449
Core: Manufacturer: 43
Core: Country: USA
Frontend: INFO: using Video plugin: 'Mupen64Plus OpenGL Video Plugin by Rice' v2.0.0
Frontend: INFO: using Audio plugin: 'Mupen64Plus SDL Audio Plugin' v2.0.0
Input: 0 SDL joysticks were found.
Input: N64 Controller #1: Forcing default keyboard configuration
Input: 1 controller(s) found, 1 plugged in and usable in the emulator
Input: Mupen64Plus SDL Input Plugin version 2.0.0 initialized.
Frontend: INFO: using Input plugin: 'Mupen64Plus SDL Input Plugin' v2.0.0
Frontend: INFO: using RSP plugin: 'Hacktarux/Azimer High-Level Emulation RSP Plugin' v2.0.0
Video: SSE processing enabled.
Video: Found ROM 'THE LEGEND OF ZELDA', CRC b71170ec2bd71676-45
Video: Enabled hacks for game: 'THE LEGEND OF ZELDA'
Video: Initializing OpenGL Device Context.
Cannot make QOpenGLContext current in a different thread
[1] 25132 abort (core dumped) m64py
I've been having this issue since 0.1.6, where when I edit the input configuration and close the program, it never seems to actually save and always reverts to something else. With the 0.2.3 version, I am getting an error from Python3:
Traceback (most recent call last):
File "/usr/share/m64py/m64py/frontend/input.py", line 61, in closeEvent
self.save_config()
File "/usr/share/m64py/m64py/frontend/input.py", line 135, in save_config
self.save_opts()
File "/usr/share/m64py/m64py/frontend/input.py", line 243, in save_opts
self.config.set_parameter("name", devicename.encode())
AttributeError: 'bytes' object has no attribute 'encode'
I am using Debian Jessie (recently Debian Wheezy) x64 Linux 3.16 and Mupen64Plus 2.0.0
It seems there were no release since a long time. But a lot of bug fixes have been gathered. Also the first release files should be uploaded to github after the move.
Please check if it is possible to create a release after the remaining pull requests are merged. At least this would be helpful before bigger changes get introduced.
I downloaded the latest source and ran the install script, it threw an error during the install process, but it appeared to create the m64py executable so I tried to run it, and got some more errors. The full output is as follows:
pi@raspberrypi ~/m64py/mupen64plus-ui-python $ python ./setup.py install
running install
running build
running build_qt
error: No such file or directory
pi@raspberrypi ~/m64py/mupen64plus-ui-python $ ./m64py
| / |_ _ _ __ ___ _ __ / /_ | || | | _ | |_ _ ___
| |/| | | | | '_ \ / _ \ '_ | '_ | || || |) | | | | / |
| | | | || | |) | __/ | | | (_) | | __/| | || __ \
|| ||,| ./ _|| ||**/ || || ||**,|/
||
M64Py - A frontend for Mupen64Plus version 0.2.2
Traceback (most recent call last):
File "./m64py", line 83, in
main()
File "./m64py", line 67, in main
from m64py.frontend.mainwindow import MainWindow
File "/home/pi/m64py/mupen64plus-ui-python/src/m64py/frontend/mainwindow.py", line 24, in
from m64py.frontend.dialogs import *
File "/home/pi/m64py/mupen64plus-ui-python/src/m64py/frontend/dialogs.py", line 22, in
from m64py.ui.about_ui import Ui_AboutDialog
ImportError: No module named about_ui
Any help with this would be greatly appreciated!
You have a lot of commands in the setup.py file, but uninstall isn't one of them. I have used the install command, but got frustrated with options not working as expected and would like to go back to command line. Unfortunately your setup script doesn't seem to provide an uninstall option and your sparse documentation says nothing about uninstallation. My only option is to reverse engineer the setup.py file and try to undo the steps it took during installation. Considering the unsurprising lack of documentation and comments, this is rather difficult. If you are going to add an "install" option then you should provide an "uninstall" option.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.