Well, i must say, i suddenly found a solution that works for now.
The analog stick is working, D-pad still no response.
Anyway, i changed the controller settings but did not change the up, down, left right. Just left it as the default values.
UP : up
DOWN: down
LEFT: left
RIGHT: right

I only have changed the buttons. this setting seems to work.

@cyperghost I agree with you...wish I would have thought of that myself! xD

@mtume only v64 is a n64 ROM the rest are savegames. The ! Means a good ripped ROM file

@coloq said in N64 button mapping woes:

So... ... still having the issue despite what documentation says I should do...

As I mentioned before, if you map the physical “a” button to the virtual “b” button and the physical “b” button to the virtual “y” button it will work as you want.

Pretty much any controller is supported, I have a wireless PS3 style controller and a wired PS3 real controller and both are detected and work perfectly with everything I use

Some games may be a bit awkward to play without specific controllers, but if you can get an N64 controller there are people that use specific controllers for specific systems and one just for everything else

Not all N64 games work, but the vast majoirt do. I have N64 games, but only those they are verified and tested working 100%

This is an outdated list now, but wil give you a good idea to what is possible on the PI3 N64. Quite a lot does work though, mainly concentrating on the popular games for 100% compatibility and support

https://wiki.gbatemp.net/wiki/Wii64_Compatibility_List

Wii/GameCube is really a "proof of concept". It will work, but so incredible sluggish and terrible it really isn't work trying (and probably never will) on the PI hardware. 3DO and SEGA Saturn emulation is also possible and supported. They WILL work but just not quick enough to actually be usable

Update: changing the advmane.rc from alsa to sdl fixed the no audio problem right away. Tested it by loading some games into the advmame folder, reloading emulation station and firing up the emulator with a game. Yes! Success! Thank you all. :-)

The issue has been fixed in the latest dev release, can you grab the @jdrassa's continuous build for Windows and check it out ?

@87th-e You should get the latest Emulationstation for Windows and see if the problem is solved.

Hi @sixspeeddeath

Im trying the same thing on my tv. The crosstalk you are talking about is caused by the distance between eyes, you need to move the warning message so if you see it without 3d lenses it overlaps with each other.

I edited the first lines of the glsl to this

#define eye_sep 0.605
#define y_loc 0.32
#define ana_zoom 1.3
#define WIDTH 2.4
#define BOTH 0.52
#define HEIGHT 2.4
#define palette 1.0
#define warpX 0.00
#define warpY 0.00

and now its almost perfect on my tv anyway (and LG 3d with passive lenses).
The only problem I have now its that the result image only uses 50% of the tv realstate

@gomezdad If you get white noise from the 3.5 jack, you can try another audio driver by adding this line to your /boot/config.txt:

audio_pwm_mode=2

It's said to be experimental, but it improved the 3.5mm sound on my Pi 3b significantly.

You can also look at White Noise Fix in the Docs for more solutions.

@lurker

I do not listen to a book I have visually read because the narrator will never fit my inner voice.

I know exactly what you're talking about. The one time I tried this was with 'Ready Player One'. Whenever I commit to reading a book, I generally like it to be something new, but I wanted to revisit RP1 not long after I read it the first time. I thought the audio book would be a good way to do that, but while I have nothing against Wil Wheaton, I had real difficulties accepting him speaking for the characters in a different way than I perceived them. I finished it out, but I wouldn't do it again.

I thought it 'meh' anywhere.

That's perfectly fair. Interestingly enough, the original story that would become 'Dracula' was actually written on the same rainy night as the story that would become 'Frankenstein' as a parlor game to see who could write the best scary story. Even then, the three participants agreed that 'Frankenstein' was the more compelling tale. In an even greater coincidence, the third story went on to become the plot for 'The Sisterhood of the Traveling Pants 2'.

Not to give up on the classics I think I will try H.G. Wells "The Invisible Man" next.

Oh man, what a great choice. I was just thinking the other day that I should read 'The Time Machine' again. I haven't read it since high school.

@Riverstorm

In your thoughts everything is precisely as you perceive it. Hearing others perception is the fun and interesting part.

Well said also. I definitely agree.

@mitu I fixed the issue! I knew that the issue was coming from the retroarch.cfg in the gen/ps1 system and snes worked fine so by using that retroarch.cfg it worked great! Thanks for the help on figuring that out.

So what happened was, I didn't think I wanted ALL of RPie when I started. So I cloned a Emulationstation repos...

with retropie-setup you can install as little or as much of retropie as you like.

Lucky for the raspberry users, we can create scripts like this one and test all the roms.
Hope you like it.
Create this file using "sudo nano checkroms.sh" and paste the contents.
Turn it into an executable using "sudo chmod a+x checkroms.sh" and execute it using "./checkroms.sh"
(Tested on Linux Mint)

#!/bin/bash

# adjust the roms path here
for i in `ls /home/retropie/mame/roms`; do

filename=`echo "$i" | cut -d"." -f1`
echo "Testing file $i:" >> cr_output.txt

# Here we will execute mame calling each rom
mame $filename 2>> tmp.out & export APP_ID=$!

# and kill the process after 2 seconds
sleep 2

kill -9 $APP_ID

# test to see if an error occured
size=$(du tmp.out | awk '{ print $1}')
if ((size > 0)); then
echo "rom $filename is not working" >> cr_rom_error.txt
rm tmp.out
else
echo "rom $filename is OK!" >> cr_rom-OK.txt
fi
done;

# End of script

After executing this script, you'll have two files. One with he roms that did not work, and another with the roms that worked.

Sorry, I thought I did. But that was in another post.

That said, compiling on a threadripper 2990WX with -J80 is almost hilarious. :-)

Thanks

Thanks guys!
As much as I wanted an external drive I still did go for a (64GB) Micro SD (Samsung Evo+ as per benchmark).

I will be moving my Rpi in Nespi Case+ from downstairs to the bedroom quite often so portability is "everything" to me.

@southblazia You don't need to install any additional drivers for a DS4, as soon as your pair it via Bluetooth it should be ready to be configured in ES. Please give more information about your setup as requested in https://retropie.org.uk/forum/topic/3/read-this-first.