[retrocam]

Fantastic! Thanks so much everyone! :)

This is exactly what fixed it for me:

sudo nano /etc/init.d/asplashscreen

and add sleep 1 in between rm -f /tmp/writable and omxplayer -b --layer 10000 "$line"

10 restarts and still playing :)

[retrocam]

Interesting. Slightly different behavior to me. All my tests have been no WiFi, always ethernet. I’m also convinced the same card is fine on a Pi2, I’m going to test that again tonight.

[retrocam]

senkun and dbalkz

Just to clarify. If you have set the video to the the carbon standard (just to rule out specific video file issues) and reboot 10 times. It won’t ever work? You mentioned that it works for a while then stops but do you mean it stops permanently? My experience is 100% intermittent. 3/5 times it works.

[retrocam]

So let’s rule out power, I’ll be double sure when I get my 2.5A power supply.
– I’ve tried a new SD card
– I just replaced my video with the RetroPie_Carbon_SplashVid-02.mp4 in case there was a size or format issue with our custom videos. It lasted 3 reboots and on the 4th didn’t play.

[retrocam]

Perfect!!!! Wooo! Well done. :)

[retrocam]

Aaah yes. I had that thought too. Well I prefer that it saves the play counts etc when rebooting so I’m happy to wait. :)

[retrocam]

Off

I remember when I first discovered turning filtering or smoothing off in an emulator. Say goodbye to fuzz. Say hello to pixels. :)

[retrocam]

That did the trick! Fantastic, thanks so much. :)

[retrocam]

[quote=92155]With your current config, the framebuffer is left in an unusable state when you exit DosBox. To fix, add runcommand.sh to your es.systems.cfg so the <command> tag now reads:

<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 "%ROM%"</command>
More info at Run DOS games in Retropie
[/quote]

Thanks so much dudleydes! That did the trick. I read your blog about setting it up but I must have missed that bit.

[retrocam]

[quote=87031]Hmmm… Question, are you guys using option 1 from here?
https://github.com/retropie/RetroPie-Setup/wiki/Setting-up-the-XBox360-controller

At first glance, option 3 looks like it may make the D-Pads work better than the other two options. I’m currently using option 1. Any thoughts?
[/quote]
I have installed the xbox 360 wireless drivers from the script retropie_setup.sh. Then etc/rc.local has:

xboxdrv --daemon --id 0 --led 2 --deadzone 4000 --silent --trigger-as-button --next-controller --id 1 --led 3 --deadzone 4000 --silent --trigger-as-button --dbus disabled --detach-kernel-driver &
exit 0
xboxdrv --trigger-as-button --wid 0 --led 2 --deadzone 4000 --silent &
sleep 1

I’m not exactly sure if I added that or it did it with the script. I also blacklisted xpad in /etc/modprobe.d/raspi-blacklist.conf as I was trying to fix up the constant chasing/blinking LED’s on my controller. This also removes the green text that appears when you start a RetroArch emulator which was annoying me.

[quote=87038]I had trouble getting my arcade stick working too, which could be similar to the Dpad since they’re basically the same, and the fix for me was adding these lines to the xboxdrv line in /etc/rc.local
–detach-kernel-driver
–dpad-as-button
Then I just had to remap the controls in Mame4allpi by pressing TAB and edit the general input and all games could be controlled with the stick.[/quote]
I attempted to add -dpad-as-button. Can’t seem to get it to work. I noticed that all the other settings are — so I tried –-dpad-as-button in various places with no luck.

[Author]

Posts