[SOLVED] - N64 - something overriding my emu choice...?

mitu

@quicksilver is almost right, Yoshi is part of the blacklist for glesn64rice (defined here), but not gles2n64. I haven't got around testing it, but will try tonight to give it a go.

quicksilver

@mitu are u sure? I just checked and "story" is on my gles2n64 blacklist. Or is that referencing a different game?

mitu

@quicksilver Not sure yet, haven't got around testing on the Pi. A cursory look (hence the reply and the link) shows

    # these games do not run with rice
    local glesn64rice_blacklist=(
        yoshi
        rogue
        squadron
        gauntlet
    )

I don't see any entries for story in any blacklist present in the default mupen64plus.sh (https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/emulators/mupen64plus/mupen64plus.sh).

quicksilver

@mitu that's really odd. I'll check mine again. I may have updated from source a week or two ago but that wouldn't affect the mupen64plus.sh file right? That's maintained as part of retro pie correct?

mitu

@quicksilver said in N64 - something overriding my emu choice...?:

That's maintained as part of retro pie correct?

Yes, that's part of the mupen64plus emulator package, it's not part of the upstream source.

quicksilver

@mitu I just checked and Yoshi's story is not on my gles2n64 blacklist (could have sworn I saw it on there as "story", guess I'm losing it). However my list doesn't match what you posted, I have about 9 games on my gles2n64 blacklist.

mitu

@quicksilver I posted the list for glesn64rice, the glesn64 list has indeed more entries:

    local glesn64_blacklist=(
        zelda
        paper
        kazooie
        tooie
        instinct
        beetle
        rogue
        squadron
        gauntlet
)

quicksilver

@mitu man I'm just out of it today. I'm going to stop trying to help now haha

mitu

@Ranma ok, so the problem seems that yoshi appears in the glesn64rice_blacklist list, but the startup script tests the ROM blacklist for both glesn64rice and glesn64altogether. Since yoshi appears in one of them, the video plugin is overriden and switched to mupen64plus-video-GLideN64 (which is what you noticed).

From the startup script

    "mupen64plus-video-n64"|"mupen64plus-video-rice")
            for game in "${glesn64_blacklist[@]}"; do
                if [[ "${ROM,,}" == *"$game"* ]]; then
                    VIDEO_PLUGIN="mupen64plus-video-rice"
                fi
            done
            for game in "${glesn64rice_blacklist[@]}"; do
                if [[ "${ROM,,}" == *"$game"* ]]; then
                    VIDEO_PLUGIN="mupen64plus-video-GLideN64"
                fi
            done

It looks like a bug, but there may be another reason why this was coded this way. @gizmo98 was this on purpose or it's just a bug ? If we switch the test for the video plugin blacklist individually, when starting with mupen64plus-video-64, the ROM would not be tested with glesn64rice_blacklist and the video plugin override would not be applied.

Ranma

That is very interesting. All I can tell you is that when it did work at first, Yoshi ran extremely well on gles2n64. The best I'd ever seen it run tbh, so I'm sad this has been coded this way. Can I change this manually? Also, thanks again to Mitu for your Holmesian work here. :-)

We have our men working on it now...

mitu

The thing is, I don't understand how it run in the first place ? If my 'analysis' is correct, you wouldn't have been able to run it - when I started it myself it would still load the Glide64 plugin.

mitu

You can change

"mupen64plus-video-n64"|"mupen64plus-video-rice")
            for game in "${glesn64_blacklist[@]}"; do
                if [[ "${ROM,,}" == *"$game"* ]]; then
                    VIDEO_PLUGIN="mupen64plus-video-rice"
                fi
            done
            for game in "${glesn64rice_blacklist[@]}"; do
                if [[ "${ROM,,}" == *"$game"* ]]; then
                    VIDEO_PLUGIN="mupen64plus-video-GLideN64"
                fi
            done

to

"mupen64plus-video-n64")
            for game in "${glesn64_blacklist[@]}"; do
                if [[ "${ROM,,}" == *"$game"* ]]; then
                    VIDEO_PLUGIN="mupen64plus-video-rice"
                fi
            done
  ;; 
"mupen64plus-video-rice")
            for game in "${glesn64rice_blacklist[@]}"; do
                if [[ "${ROM,,}" == *"$game"* ]]; then
                    VIDEO_PLUGIN="mupen64plus-video-GLideN64"
                fi
            done

and it should work - no more GLideN64 override.
The file is /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh. It will be overwritten when you update the mupen64plus package, but hopefully we can find a fix for it and update the package - if it's just a bug.

Ranma

@mitu Hmmm, yeah that is odd. Maybe I'm mistaken but it definitely did not run the Gliden64 plugin on my first play. I got to about level three (lightweight!), chuffed to bits with the performance, before powering down for the evening. I had also tried other emulators before settling on gles2n64.

Thanks so much for your fix above Mitu and all the assistance you have given me here on Retropie Forums. You are always one of the first to reply and always get it sorted for me. :-)

quicksilver

@Ranma so I removed Yoshi's story from the rice blacklist and I was able to run it with gles2n64 but it runs terribly. Missing textures and backgrounds make it pretty much unplayable. Are you sure it was gles2n64 you were using?

Ranma

Well I feel like a right wally. I applied your code above and it works! However, I must have been mistaken as Yoshi runs awfully with gles2n64 as the emu. I imagine this is why the author blacklisted it. Most of the screen is black, and when you can see elements you only get bits here and there.

God only knows what I was thinking. Apologies to Mitu for taking up your valuable time with this. :-(