Code: Select all
[Input-SDL-Control1] # Mupen64Plus SDL Input Plugin config parameter version number. Please don't change this version number. version = 2 # Controller configuration mode: 0=Fully Manual, 1=Auto with named SDL Device, 2=Fully automatic mode: 0
Code: Select all
sudo ./mupen64plus.cht /home/pi/Desktop/N64Roms/SuperMario64.zip
Code: Select all
./mupen64plus.cht: 1: ./mupen64plus.cht: //: Permission denied ./mupen64plus.cht: 2: ./mupen64plus.cht: //: Permission denied ./mupen64plus.cht: 3: ./mupen64plus.cht: //: Permission denied ./mupen64plus.cht: 4: ./mupen64plus.cht: Syntax error: "(" unexpected
I would assume so as I'm unaware of any other solutions to N64 emulation on the RPi.mattmartinolc wrote:Is this the version that is included in the RetroPie setup script
Hard to say as I don't use RetroPie, but it shouldn't make any difference as all it would be doing is launching via Emulation Station (the Front End). How choppy is it? What is your overclock setting? A user posted a UTube Vid playing Mario64 at a High (1000MHz) O/C of an early Build, the sound accuracy has since been much improved, (Here - http://www.youtube.com/watch?v=fGkHx3CvLUo), with the current version you should be getting a similar level performance at 900MHz. Another UTube Vid with Shea Silverman (of PiMAME) running Star Fox 64 on an early build at a default 700MHz overclock (Here - http://www.youtube.com/watch?v=uMEhhIQqWJI), again, at higher O/C's it should be much improved (with the odd glitch when lots of polys are being drawn and effects applied). Perhaps reducing you GPU split to 128MEG would help giving the CPU more memory bandwidth?pomme wrote:A little late to the game here but I am attempting to get mupen64plus-rpi running via RetroPie/ES.
I've managed to get my ROM detected and launching with no issues but when the game starts it's extremely choppy/unplayable. I've read through this thread and tried adjusting settings where suggested but it doesn't seem to make a difference in performance.
I get that there isn't full support for all titles but I am having trouble with even the "Best Titles" such as Super Mario 64.
I've got my memory split to 256mb - What nooby thing am I overlooking here?
That's an interesting tit bit, haven't checked that (only when previously testing the dev branch for you to see if it crashed), will have to give that a go!ric_rpi wrote: 2. Run mupen64plus using sudo/root so that it can change its scheduler policy to 'hog' the CPU
Ah, that could be the answer as to why your experiencing performance issues. Analogue sound exacts a much greater overhead than Digital via HDMI on the RPi Hardware, noticeably so when trying to also emulate something as complex as the N64! Reducing the fidelity (frequency) of the sound should help, see previous posts for details.The buffer over run messages are common, even under HDMI.pomme wrote:Thanks guys, lowering the memory split to 128 and setting the O/C to 1000mhz made a marked improvement.
One problem seems to remain on most games, very distorted audio.. My video is coming out via RCA and I am using the 1/8" audio jack. Are the any special considerations for this setup? I am noticing a long string of Audio Buffer Over Run messages in the console when I exit. Cause for concern? Thanks again for your help.
Yes that's exactly what it means. The config Menu (sudo raspi-config) applies the RAM to the GPU depending on what value is used. So if the value 128 is used, 128MEG of available RAM (512 or 256 depending on your Model) is assigned to the GPU.whise wrote:Im sorry can you guys just explain something to me?
When you say 128 mb GPU/CPU memory split.
Does that mean 128 mb for the GPU?