M64py not working anymore since python updates

linux_dream · 2021-12-18 15:49:46

I used to run M64py everyday without problems until the last python updates. I have rebuilt all the related packages in the AUR, but running m64py from the terminal yields:

m64py
__ __ __ _ _ ____ _
| \/ |_ _ _ __ ___ _ __ / /_ | || | | _ \| |_ _ ___
| |\/| | | | | '_ \ / _ \ '_ \| '_ \| || |_| |_) | | | | / __|
| | | | |_| | |_) | __/ | | | (_) |__ _| __/| | |_| \__ \
|_| |_|\__,_| .__/ \___|_| |_|\___/ |_| |_| |_|\__,_|___/
|_|

M64Py - A frontend for Mupen64Plus version 0.2.5

Frontend: INFO: attached to library 'Mupen64Plus Core' version 2.5.0
Frontend: INFO: includes support for Dynamic Recompiler.
Unhandled Python exception
Aborted (core dumped)

Which is... cryptic to say the least. No idea where the problem is.

Here are the packages I have installed: community/mupen64plus, aur/m64py, aur/mupen64plus-video-gliden64-git 4.0.r165.gfbd1ad1a-1, and python-pysdl2 (yes, I had to reinstall it, because m64py would return an error about sdl2 missing...)

Any help to get m64py working again would be utterly appreciated.

Edit: Here is the verbose message:

m64py -v
__ __ __ _ _ ____ _
| \/ |_ _ _ __ ___ _ __ / /_ | || | | _ \| |_ _ ___
| |\/| | | | | '_ \ / _ \ '_ \| '_ \| || |_| |_) | | | | / __|
| | | | |_| | |_) | __/ | | | (_) |__ _| __/| | |_| \__ \
|_| |_|\__,_| .__/ \___|_| |_|\___/ |_| |_| |_|\__,_|___/
|_|

M64Py - A frontend for Mupen64Plus version 0.2.5

Frontend: INFO: attached to library 'Mupen64Plus Core' version 2.5.0
Frontend: INFO: includes support for Dynamic Recompiler.
Video: Getting value card_id
Video: Getting value force_polygon_offset
Video: Getting value polygon_offset_factor
Video: Getting value polygon_offset_units
Video: Getting value vsync
Video: Getting value ssformat
Video: Getting value show_fps
Video: Getting value clock
Video: Getting value clock_24_hr
Video: Getting value wrpResolution
Video: Getting value wrpVRAM
Video: Getting value wrpFBO
Video: Getting value wrpAnisotropic
Video: Getting value ghq_fltr
Video: Getting value ghq_cmpr
Video: Getting value ghq_enht
Video: Getting value ghq_hirs
Video: Getting value ghq_enht_cmpr
Video: Getting value ghq_enht_tile
Video: Getting value ghq_enht_f16bpp
Video: Getting value ghq_enht_gz
Video: Getting value ghq_enht_nobg
Video: Getting value ghq_hirs_cmpr
Video: Getting value ghq_hirs_tile
Video: Getting value ghq_hirs_f16bpp
Video: Getting value ghq_hirs_gz
Video: Getting value ghq_hirs_altcrc
Video: Getting value ghq_cache_save
Video: Getting value ghq_cache_size
Video: Getting value ghq_hirs_let_texartists_fly
Video: Getting value ghq_hirs_dump
Video: Getting value alt_tex_size
Video: Getting value use_sts1_only
Video: Getting value force_calc_sphere
Video: Getting value correct_viewport
Video: Getting value increase_texrect_edge
Video: Getting value decrease_fillrect_edge
Video: Getting value texture_correction
Video: Getting value pal230
Video: Getting value stipple_mode
Video: Getting value stipple_pattern
Video: Getting value force_microcheck
Video: Getting value force_quad3d
Video: Getting value clip_zmin
Video: Getting value clip_zmax
Video: Getting value fast_crc
Video: Getting value adjust_aspect
Video: Getting value zmode_compare_less
Video: Getting value old_style_adither
Video: Getting value n64_z_scale
Video: Getting value optimize_texrect
Video: Getting value ignore_aux_copy
Video: Getting value hires_buf_clear
Video: Getting value fb_read_alpha
Video: Getting value useless_is_useless
Video: Getting value fb_crc_mode
Video: Getting value filtering
Video: Getting value fog
Video: Getting value buff_clear
Video: Getting value swapmode
Video: Getting value aspect
Video: Getting value lodmode
Video: Getting value fb_smart
Video: Getting value fb_hires
Video: Getting value fb_read_always
Video: Getting value read_back_to_screen
Video: Getting value detect_cpu_write
Video: Getting value fb_get_info
Video: Getting value fb_render
Unhandled Python exception
zsh: abort (core dumped) m64py -v

Last edited by linux_dream (2021-12-18 19:54:49)

Lone_Wolf · 2021-12-19 13:49:45

You're not the only one with this issue, see https://github.com/mupen64plus/mupen64p … issues/191

linux_dream · 2021-12-19 18:12:12

Lone_Wolf wrote:

You're not the only one with this issue, see https://github.com/mupen64plus/mupen64p … issues/191

Well, it's myself.

Daerandin · 2021-12-19 19:46:20

Not a fix but: If you are not averse to editing configuration files manually (with a text editor) you can simply ditch m64py as it does not really add anything to mupen64plus. It's just a graphical interface to the same configuration and everything can be modified manually, including which video plugin you would prefer to use.

I noticed the bug report Lone_Wolf linked to mentions graphical issues. Did you try plain mupen64plus with the glide64mk2 video plugin instead of the default rice plugin? glide64mk2 is installed with mupen64plus, and all you need to do is make a simple change in the config file, and potentially modify some values related to the video plugin.

linux_dream · 2021-12-19 20:56:27

Daerandin wrote:

Not a fix but: If you are not averse to editing configuration files manually (with a text editor) you can simply ditch m64py as it does not really add anything to mupen64plus. It's just a graphical interface to the same configuration and everything can be modified manually, including which video plugin you would prefer to use.
I noticed the bug report Lone_Wolf linked to mentions graphical issues. Did you try plain mupen64plus with the glide64mk2 video plugin instead of the default rice plugin? glide64mk2 is installed with mupen64plus, and all you need to do is make a simple change in the config file, and potentially modify some values related to the video plugin.

Yeah, that may be the quickest route for a "fix". I notice that my .config/m64py/m64py.conf file contains:

[General]
disable_screensaver=1
enable_vidext=0
keep_aspect=1
last_dir=/home/linux_dream/Download
recent_files="/home/linux_dream/..."
size=@Variant(\0\0\0\x7f\0\0\0\xePyQt_PyObject\0\0\0\0\x14\x80\x4\x95\t\0\0\0\0\0\0\0M|\aM\xdb\x3\x86\x94.)

[Paths]
Data=/usr/share/mupen64plus
Library=/usr/lib/libmupen64plus.so.2.0.0
Plugins=/usr/lib/mupen64plus
ROM=/home/linux_dream/Download

[Plugins]
b%27Audio%27=mupen64plus-audio-sdl.so
b%27Input%27=mupen64plus-input-sdl.so
b%27RSP%27=mupen64plus-rsp-hle.so
b%27Video%27=mupen64plus-video-glide64mk2.so

So I guess it's a matter or running mupen64plus with those settings. But, I also have save states, and I am unsure how to "call" them, or how to save a state while playing. And also, no idea how to configure the keys (I am guessing I should tweak another file, but this might become a problem when I get my new controller within the next 2 days...).

Last edited by linux_dream (2021-12-19 20:57:15)

Daerandin · 2021-12-19 22:01:51

Please use code tags when pasting code, as well as contents of config files.

mupen64plus will not read anything from that file, as that is specific for m64py. mupen64plus has its own config file which is normally found under ~/.config/mupen64plus/mupen64plus.cfg

This is documented in the man page for mupen64plus. All configuration, including controller setup is in this file. You will probably don't need to make many changes. Video plugin is probably one of the most important. If you don't know how to configure the keys, use some program that will let you see the keycodes of pressed keys/buttons, and then apply those keycodes to the configuration file.

I don't know if m64py puts save states in another place than what is default for mupen64plus, but you could simply check the default location (check the man page if you don't know where to look) and see if there's anything there. If the files are in the default location for mupen64plus, then they should be available when you play.

linux_dream · 2021-12-24 11:18:52

Daerandin wrote:

Please use code tags when pasting code, as well as contents of config files.
mupen64plus will not read anything from that file, as that is specific for m64py. mupen64plus has its own config file which is normally found under ~/.config/mupen64plus/mupen64plus.cfg
This is documented in the man page for mupen64plus. All configuration, including controller setup is in this file. You will probably don't need to make many changes. Video plugin is probably one of the most important. If you don't know how to configure the keys, use some program that will let you see the keycodes of pressed keys/buttons, and then apply those keycodes to the configuration file.
I don't know if m64py puts save states in another place than what is default for mupen64plus, but you could simply check the default location (check the man page if you don't know where to look) and see if there's anything there. If the files are in the default location for mupen64plus, then they should be available when you play.

Thanks a lot. It was actually harder than I thought. I installed a program to map the controller's buttons to strings in the config files, however this wouldn't work at all. Then I found some information in a forum, where someone faced the same problem, and it was because there was the keyboard part that was specified in the config file as well. By deleting the keyboard part, I could make the controller work (that's completely crazy...). However the graphics were not fixed with glide something, despite everything being specified in the config file. But thankfully some M64py dev fixed the problem in github, and switching to the git version of M64py (in the AUR) fixed the problem, now everything is working as it should.

Arch Linux

#1 2021-12-18 15:49:46

M64py not working anymore since python updates

#2 2021-12-19 13:49:45

Re: M64py not working anymore since python updates

#3 2021-12-19 18:12:12

Re: M64py not working anymore since python updates

#4 2021-12-19 19:46:20

Re: M64py not working anymore since python updates

#5 2021-12-19 20:56:27

Re: M64py not working anymore since python updates

#6 2021-12-19 22:01:51

Re: M64py not working anymore since python updates

#7 2021-12-24 11:18:52

Re: M64py not working anymore since python updates

Board footer