@unknown nah the memory is emulated, don't think a proper emulator could read the data from a real memory card; that would be cool though.

@stevenrice please fill out https://retropie.org.uk/forum/topic/3/read-this-first

but again note that it doesn't support .zip files. the behaviour that you're seeing can be caused by incompatible file types. if you're using .zip, extract the files.

@breadpie said in N64 on a Pi 3B+:

I have my Pi 4 (which is great), but I also have an older Pi 3B+ where the microSD became corrupted and I finally got around to putting in a fresh one. I grabbed the download from the retropie website, put it on a new card, etc. But, I noticed two things: 1) that mupen64plus (not lr-mupen64plus, and not lr-mupen64plus-next which wasn't installed by default) is the default for N64; and 2) that updates were available for mupen64plus. The stock build seems to have mupen64plus current as of Oct 2020, if I recall correctly. Normally I would update a package reflexively, but I also remember concerns about regressions with an N64 update from around last year. So, my questions, specifically for a Pi 3B+:

Should mupen64plus stay as default?

yes. standalone is fastest and most compatible. lr-mupen64plus (NOT -next) or mupen64plus-gles2n64 or even lr-mupen64plus-parallel may be faster in some scenarios, but the best balance is mupen64plus-auto (which i believe is the default for pi3), which selects the appropriate video plugin for mupen64plus-standalone, per game.

Is there any potential downside to installing the latest updates (since the most recent stock install) to these emulators on a 3B+?

not that i'm aware of, but as always, always back up before any updates. do note that n64 emulation is probably only going to get slower with updates, as emulation gets more accurate, compatible, etc.

@alinktotao said in Anyone know how to set up N64 raphnet adapter with the "raphnetraw plugin" on RetroPie??:

@mitu said in Anyone know how to set up N64 raphnet adapter with the "raphnetraw plugin" on RetroPie??:

Looks like the input plugin is detected and loaded, but the plugin errors out while opening the controller:

... Opening device path: '/dev/hidraw2' Input Error: Could not open gcn64 device serial '109634'. Skipping it. Input Error: No adapters detected

Maybe there's a permission error ? Check if the /dev/hidraw* devices are available to the pi user, by running the command:

ls -l /dev/hidraw*

pi@retropie:~ $ ls -l /dev/hidraw*
crw------- 1 root root 244, 0 Aug 7 18:58 /dev/hidraw0
crw------- 1 root root 244, 1 Aug 7 18:58 /dev/hidraw1
crw------- 1 root root 244, 2 Aug 7 18:58 /dev/hidraw2
crw------- 1 root root 244, 3 Aug 7 18:56 /dev/hidraw3
crw------- 1 root root 244, 4 Aug 7 18:56 /dev/hidraw4
crw------- 1 root root 244, 5 Aug 7 18:56 /dev/hidraw5
crw------- 1 root root 244, 6 Aug 7 18:56 /dev/hidraw6
crw------- 1 root root 244, 7 Aug 7 18:56 /dev/hidraw7

OH MY GOOODNESS!! THAT DID IT! THANK YOU SOOOO MUCH!!!

@mitu said in N64 Controller Setup - Inconsistent Documentation:

@busywait said in N64 Controller Setup - Inconsistent Documentation:

If you don't have a 'retropad A' button defined, of course it's not going to work in the menu . My remark was:

How the button is mapped to the underlying core doesn't matter for the menu (RGUI or otherwise).

I agree, but the reason that I don't have a retropad A button defined is because the core doesn't use it for it's logical function in the mapping. I could have had both [N64 "A" and RGUI "A"] if the core used different bindings.

Obviously this is a minority problem for people trying to use pads without the full set of retroarch inputs, and I can still navigate the RGUI using a keyboard in my case :)

Could find the solution on my own.

The correct syntax is J0B4/H0VX
where the "X" is set to be 1(up) 2(right) 4(down) or 8(left) depending on the direction.

Well, you guys are awesome. Once I figured out where to change input settings in Retroarch..and then how to save my configuration...I got it working. The mappings for the left analog stick were blank, somehow. Note: I edited the main RetroArch config, and not Core configs. Both were blank, but I wanted it to correct every N64 rom.

I assume that means the Dpad was working, and it just wasn't being needed by Mario64, which I was testing on.

The mappings for N64 are described in the emulators doc page - https://retropie.org.uk/docs/Nintendo-64/. If you wish to change it, you can either use RetroArch's input remapping for the lr-mupen64/lr-mupen64-next emulators or editing the InputAutoCfg.ini for the standalone mupen64plus emulator.

@omission229 No, sorry, otherwise I would have said so.

@dankcushions I would think these tweaks would be saved in a ini or text file somwhere.

Use the image from retropie.org.uk/download and it should work fine, we don't support 3rd party images.

Adapter seems to be working great, tried out some more games over the weekend and I'm loving it so far. I was also able to map the table of hotkey combos (updated above), except the "Input State Slot Increase/Decrease" triggers at the same time that I go to Save or Load which is mapped to D-Pad right/left.

All retroarch.cfg:

input_state_slot_increase = "right" input_state_slot_decrease = "left"

N64 retroarch.cfg:

input_state_slot_decrease = "nul" input_state_slot_decrease_axis = "-3" input_state_slot_decrease_btn = "nul" input_state_slot_decrease_mbtn = "nul" input_state_slot_increase = "nul" input_state_slot_increase_axis = "+3" input_state_slot_increase_btn = "nul" input_state_slot_increase_mbtn = "nul"

-3 and +3 are C-Button left and right. If I set the All config to "nul", they won't work in any other emulator, correct? Should -3 and +3 be mapped to input_state_slot_increase/decrease instead of the ones with "_axis"?

@stephenrossi20 said in N64 games running slow on Rasberry Pi 4..Help!!:

is there a way to make them run more smooth?? all options are on the table

Overclock your GPU and via the Runcommand, select a recommended N64 Emulator, Resolution, Setting per Rom/Game as detailed in this list below ...

https://docs.google.com/spreadsheets/d/1Rq4shU1RUSdcc7cTVWeORMD-mcO6BwXwQ7TGw8f5_zw/view#gid=1983504515

@dankcushions

you're right, that's a quicker way of checking :-)

to answer your question, I was referring to per-game override configs that only contain a one line pointing to the overlay config (which in turn points to the graphics), if that makes sense.

We may have to amend the docs and don't recommend ds4drv anymore. Try with regular bluetooth pairing again - it should work.

@crush Yeah, I think Vilros was going for the original 6 button layout rather than the extra features Retro-bit did. The Retro-bit controllers are admittedly a nicer option as far as Genesis goes.

I think I'd prefer my 8bitDo SN30 pro for SNES and Playstation. But I plan to get this set for the NES and N64 options, and the rest can be used as controllers by friends/family. I've yet to decide what I want to do for Sega, but I may just get this one and get the Retro-bit when I have the luxury of extra game budget.

@quicksilver thanks a lot for this. Worked a treat on the crackling sounds I was experiencing

@dankcushions Ok, now i see, thanks