@linbeg said in N64 mapping - everything works, but C up and down:

I’ve attached the Pork One mapping below ...

You perhaps forgot to include it. Also please take some time to describe your setup as asked in https://retropie.org.uk/forum/topic/3/read-this-first.

@quicksilver said in mupen64plus-gliden64 with verbose logging?:

Is it possible to run standalone mupen64plus-gliden64 with verbose logging? I see that the emulator supports --verbose as a command line option but not sure how to enable it through retropie.

You can't use the runcommand menu for verbose logging since that's only available for the libretro cores, but you can:

Look in the log file - /dev/shm/runcommand.log - and note the command line used to execute the emulator Copy the command used and then run it manually, outside of EmulationStation, appending the --verbose parameter so you get extra information printed during execution.

Did you try to ask the vendor if they have Linux support ? Is the controller you have the Brawler64 BT NSO Edition - the one that's created for the Switch ?

Please also add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

@Slick I suggest opening a separate topic with recommended information: https://retropie.org.uk/forum/topic/3/read-this-first

@mitu

It was in fact that I had not updated retro pie on installation - I can’t believe I did not think of that.

The rom was also no good, I did try the correct one earlier, and it didn’t work so I went searching for that one.

But the rom is working now!
Thank you very much.

@MAHER said in Problem with n64 Rom:

Is there a way to resolve this issue?

AFAICT, only by installing the upstream libretro core ?

Can I manually install the core I need?

You can modify the scriptmodule for lr-parallel64 to get the sources from the libretro repository and try installing it from source. There's no guarantee that installation will work or that the core will run on an ARM device with reasonable performance.

I'm still unsure about what you mean when you refer to the "fork."

fork in this context means copy. RetroPie installs an older (and probably ARM optimized) copy of the Parallel 64 core.

@sugarfree wow, its amazing how you just solved my problem with only two lines of code. Thank you so much, words fail to express the relief you just brought me lol

I first thought, can we use function copyDefaultConfig here when placing the file? Except, when I updated this last time it also added a couple new entries, which I suppose we would not want to miss out on.

You can't use copyDefaultConfig because the file is updated upstream and updates will not copy when a new version is added.

So could we use sed or something, then, to add the fix automatically? Or, why do we even have to do this manually, why is this just not the default already; is the glitch specific to a certain hardware/platform?

The default is the opposite (copyDepthToRDRAM=1), so it's clearly a platform (RaspberryPi / GLES3) glitch

[DONKEY%20KONG%2064] Good_Name=Donkey Kong 64 (E)(J)(U) frameBufferEmulation\copyDepthToRDRAM=1 frameBufferEmulation\N64DepthCompare=0

The launch script has some overrides for games, but copyDepthToRDRAM is not among the settings considered. Maybe it would be useful to have a GLideN64.local.conf and merge the settings from it in GLideN64.custom.conf, during installation/configuration.

I got it to work by researching kernel. I ran lr-parral64 and edited a line in retroarch config. Thank you for your help!

@manD0rk Please, start a new topic and add the necessary info, see: https://retropie.org.uk/forum/topic/3/read-this-first.

@grazzii said in Trouble installing Mupen64 core:

Would installing the 32Bit system give better performance results in your opinion?

No, but it will consume less memory for the same tasks. You can stick with 64bit, but if you intend to use it also as a desktop computer then memory size may become an issue (regardless of the 32bit/64bit choice).

@mitu

Solved
I added

mupen64plus-next-cpucore = "cached_interpreter" parallel-n64-cpucore = "cached_interpreter"

in

/opt/retropie/configs/all/retroarch-core-options.cfg

I was able to convert my .srm save file from lr-mupen64plus-next to an .sra file with this online tool.

https://drehren.github.io/ramp64-convert-web/

I then copied the .sra file into /opt/retropie/configs/n64/mupen64plus/save/

Then I launched ocarina of time with mupen64plus-GLideN64 and played it nonstop for about 2 hours without any crashes or major issues. GLideN64 may have had a few more video glitches than lr-mupen64plus-next was having, but not a single crash for that entire period of time, and that was picking up the game where I left off playing with lr-mupen64plus-next.

So it seems that I don't have these crashes with standalone emulators, but do with libretro emulators.

@WhiteT982

Haven't made my way yet to N64.

Still trying to settle the texture packs for the NES.

Thanks for the folder directory location though.

It will be easier now that I know where those will go.

@DominicSD when you select the game it gives you a grey box asking you to press A if you wish change any resolution or emulator settings. If you press A then it should bring you to a menu and a list of emulators to choose from. If you're saying you've already tried Gliden and the others then that's the best the Rp4 can do for now for n64