@mitu @caver01 Thanks guys!

ok i tried it. This is my config. But it didnt work. my idea for the select Button is to push the eft and right shoulder button at the same time

DPad U = hat(0 Up) DPad D = hat(0 Down) DPad L = hat(0 Left) DPad R = hat(0 Right) Start = button(9) Z Trig = button(7) A Button = button(6) B Button = button(8) C Button U = button(0) C Button D = button(2) C Button L = button(3) C Button R = button(1) Y Axis = axis(1-,1+) X Axis = axis(0-,0+) R Trig = button(5) L Trig = button(4) Select = button(4) button(5)

And oddly enough I am attempting to duplicate all of these steps on my Pi3 setup and I am back to where I began. Except now the WAD Header error has a lot more garbage at the end than ever before.

EDIT: This only reflects the Run Command method.

I came across this exact issue this weekend. My situation is, honestly I was curious about having OctoPi for my 3D printing and RetroPi to test some games.

To keep it short:

I was using a 128gb Samsung EVO SD card while dual booting (using berryboot)with Retropie and Octopi. After trying to get it working by uninstalling and re-installing amongst other things, I decided to try another 32GB SD card also a Samsung Evo. I installed RetroPie (From berryboot) first. Verified that the images booted successfully. I added the octopi image from the berryboot images page and copied that over successfully. I applied updates to RetroPie first then to OctoPi. After configuring OctoPi to the way I needed it (after many hours of researching) after rebooting, both images still booted with no issue. I made a backup of the SD card with my desired setup then restored that backup to the 128gb chip. I plan to test this chip to see if I have the same results.

Sidenote: In further research of this issue, the problem seems to be with permissions. This command seems to have worked for those getting the error. A reboot was required afterwards:

sudo usermod -a -G video yourusername

I have the same setup as you (mostly) and had the exact same problem. Do what @mitu said, set gpu memory split to at least 256MB.

Take a look at this recent topic - https://retropie.org.uk/forum/topic/22337/gamepad-calibration-problem/3. If the emulator is using the new evdev api to read/access the gamepad, then jscal doesn't have any effect.

Yeah that worked, thanks!

Let me know if you notice any PSX slowdown with rewind. I always assumed PSX would take quite a hit but have always been curious if it would slow it down a bunch.

@ApollGama said in USB Controller work on Emulstation but not in Raspi-config or to set up wifi/bluetooth etc... (Using Dualshock 4):

and I used a pre made imae

That's probably the reason why you're having this issue and that's one of the reasons we don't support such images.
Use the image from retropie.org.uk/download and you'll not have this problem.

@HairyAdmin I followed your instructions, but with your emulator string my roms will not even play. Using the emulator string from the article [link text]http://selsine.com/2016/10/16/how-to-live-stream-to-twitch-from-a-retropie/(link url), I can get the game to play, but it will not stream to twitch, or even register anything on twitch.

Here is what I have so far.

I am running 4.4 on a raspberry 3 b+.

/home/pi/RetroPie/Recording/Twitch.cfg

vcodec = libx264 acodec = aac pix_fmt = yuv420p threads = 2 scale_factor = 1 format = flv video_preset = ultrafast video_profile = main video_tune = animation video_bufsize = 512k video_minrate = 512k video_maxrate = 512k video_r = 60 video_g = 120 video_keyint_min = 60 sample_rate = 44100 audio_preset = aac_he_v2 audio_global_quality = 1

/opt/retropie/configs/nes/emulators.cfg

lr-fceumm = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fceumm/fceumm_libretro.so --config /opt/retropie/configs/nes/retroarch.cfg %ROM%" default = "lr-fceumm-record-twitch" lr-nestopia = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-nestopia/nestopia_libretro.so --config /opt/retropie/configs/nes/retroarch.cfg %ROM%" lr-quicknes = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-quicknes/quicknes_libretro.so --config /opt/retropie/configs/nes/retroarch.cfg %ROM%" lr-fceumm-record-twitch = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fceumm/fceumm_libretro.so --config /opt/retropie/configs/nes/retroarch.cfg --record rtmp://live . / $$STREAMKEY$$ --recordconfig /home/pi/RetroPie/recording/twitch.cfg %ROM%"

Any assistance would be swell, and please type slow, because I can't read fast.

@marcel151 There is a regression in the latest Linux stable kernel regarding bluetooth connections - you'll either have to wait for an update or downgrade your OS packages (kernel+firmwarre) as shown here.

@adamdicaprio There's no posting of copyrighted material in the forum, either ROM, BIOS files or otherwise. Please review the forum rules, if you haven't so.

@Efriim there is a better solution. Buy a dolphinbar and sync it to that. Remove all syncing of it previously done on the bluetooth first.

@mrsoczi We don't offer support for 3rd party images - https://retropie.org.uk/forum/topic/3/read-this-first.

For wireless controllers, take a look at the Controllers section in the Docs, you can use one of the PS3/PS4 controllers, an Xbox controller, 8Bit do controllers, etc.

Thanks, I'll try it!

@squishykoishi

am not using hires version and in fact locked the screen res for N64 games at 720x576

this can add lag as you’re forcing your tv to do an up scaling operation. see https://github.com/RetroPie/RetroPie-Setup/wiki/Input-Lag#use-hdtvs-native-display-resolution

retropie already runs (most) n64 games at 320x240 and then let’s SDL to a (fast) upscale using the GPU.

the rest of the input lag wiki may help you if there’s still an issue.

weird that gles2n64 etc fix the problem but they don’t have accurate emulation so may have incorrectly quick latency to start with? not sure

@Quaxo76 I think this is possible without additional software installation.
You can check for file in /dev/shm/runcommand.info
This file will be created if an emulator was started.
Or the timestamp of this file changes if there was annother emulator was started.

So you check every 10minutes with a cron job and count file presence or file change ;)

You can get a set of verified mount options from the docs. Try it - in your /etc/fstab file - and see if work with those options.

@Efriim
For me its stuck on video that u can see on loop (not white screen with sound).
In anycase i switch the screensaver to Images and it fix the problem (kinda solve).
Try to find your white screen video and switch it for sure.
If u find another solution will love to know