Got it sorted ,I plugged the raspberry pi3 into my HD TV and the screen was able the handle the default 1920x1080 resolution.Then went into Kodi settings and set the resolution to the nearest to 1280x1024 which was 1280x720.
Another leason learned on the Pi.

Thanks guys for all your help and support.

@edmaul69 I changed the file permissions and it still didnt work. I read somewhere that the configs folder @ /RetroPie/configs/n64 is just a shortcut to /opt/RetroPie/configs/n64 so I changed that one too but no luck. The system changes it back to what it decides is best and none of my changes stick

So, I purchased a mini HDMI to a standard HDMI cable, and replaced the cable and adapter I had (the amazon basics mini HDMI to female full size HDMI adapter). Everything works perfect now. Thanks everyone!!

I'm new to this stuff myself, and it is happening to me also.
I mistakenly did a kernal update while trying to navigate around, and 20 minutes later I had no way to exit apps like Retroarch and only tested with GBA roms, but both I attempted would not work right for my NES30 Pro. I'm going to have to start over also. I hope they fix this issue soon. I've had to unplug twice because of this, and going to learn SSH before trying any more games.

I just ran through the first level of 'Virtual Boy Wario Land' using red/blue, red/cyan, red/green and green/magenta glasses and I couldn't personally tell a difference in the quality of the 3D effect. However, it seemed to me that the one that should be avoided the most would be red/green as it renders everything in in yellow tones and after extended play sessions, that will likely disrupt the ability to perceive color in the real world for a good ten minutes to half an hour afterwards in a big way.

BUMP

This is the only emulator I've had issues with – yes I get sound stuttering or dropping on the games I've played. I figured it was just too hard for the Pi (though that I would think might happen with the larger Playstation games), but I will look into this tweak.

Cheers Guys, thanks for the info.

I have the same issue with a PS4 controller. I tried three they where all connected to bluetooth. All have spasm while in game and also when it rests in the retropie menu. I can't find any solution online. I have two 8bitdo SFC30 controller and the work without a problem.

@cerealspiller delete the retroarch.cfg. Then reinstall the psx emulator to get your retroarch.cfg back.

@mediamogul heyyyy so its this kit right here

https://www.amazon.com/Raspberry-Essentials-Kit-board-Connectivity/dp/B01LWVVMUI/ref=sr_1_7?s=pc&ie=UTF8&qid=1488043332&sr=1-7&keywords=rasberry+pie+3

using xbox 360 controllers (they connected real easy)
no error messages just a straight freeze every 3 races or so. Tried 1 player nfl blitz its just extremely choppy. Using the guide off this website the video they supply. Using Retro pie 4.1

After further reading I'm almost definite that it's down to the Sandisk Ultra card not being fast enough for cd games. I only have 50 roms in each format at the moment and three in mega cd , so it's not a space issue.

Would a SanDisk Extreme SD card be up to the job, or are there other SD cards anyone would recommend?

Thanks.

@dunnieboy i dont have my pi to tell everything exact. After you set your controllers up back at the main menu i believe you go into the bottom option. If you go in there you can set save on exit and you can save your joystick config in there too. I think its in there where the option to set the menu button to the controller too.

@bluecaka69 glad you got it working. 👍🏻

@groviar

I guess I'll need to experiment.

Your best source of information on this will be on the actual Hatari information pages, as it's the same emulator running here. If you get it going, report back and either you or I can add it to the RetroPie wiki.

@Danorak1981 I actually made my own google doc of the steps necessary without game links.

If you need help still hit me up.

I see, thanks for the help! I do wonder why basic install seems to goof it though.

When you start a rom and when in game press select + x and look at what driver it uses for audio. I had the same problem with some of the emulators after updating everything. For some the driver for audio was changed from sdl2 to alsathread. I didn't have sound and got the above mentioned underun error.

It needs to be sdl2.

Hope it helps.