Forum Replies Created
- senkunParticipant04/06/2016 at 12:21Post count: 35senkunParticipant04/06/2016 at 12:07Post count: 35
will all the threads here be archived over to the new forums? be a shame if all the useful info be lost.senkunParticipant04/05/2016 at 22:38Post count: 35senkunParticipant04/05/2016 at 22:22Post count: 35senkunParticipant04/05/2016 at 22:20Post count: 35
[quote=122442]Read the attachment>
Thanks, that cleared up some niggling worries.senkunParticipant04/05/2016 at 22:12Post count: 35
[quote=122459]I actually managed to get it working. I saw a video on YouTube that showed you how to do it all. I’m just wondering how you get some games to work as some load and some don’t .
All your answers right here;senkunParticipant04/03/2016 at 21:43Post count: 35
[quote=122276]Sorry, don’t know the answer. What screen is that? Thanks
Very nice screen good bang for the buck, it’s a waveshare 3.2″ v4, 320×240 so it’s pretty snappy when configured right, minimal tearing.
[quote=122328]with help from Buzz, we’ve actually fixed this in the code now
so if you don’t mind waiting for about 30 minutes for mame to compile, you could avoid the above instructions by doing a build from source:
2) install individual emulators
4) from source
whoa! Thank you!senkunParticipant03/30/2016 at 18:40Post count: 35
quit emulationstation drop to terminal and update raspbian while your sdcard is still in your pi2 and connected to the net. Then when updated, swap sdcard to new pi3 and you should be good to go.
but of course, before anything else, backup everything first.senkunParticipant03/30/2016 at 18:05Post count: 35
meaning raspbian. apparently the newest updates to raspbian already has wifi power mngmt off by default, so if you have had updated it would mean your wifi issues are something else altogether.
keeping retropie itself updated, the conventional way is through the setup script accessed from the retropie menu in ES or from the terminal with sudo ./retropie_setup.sh and doing a binary or source update. not sure if the wifi “fix” is in them.senkunParticipant03/30/2016 at 12:44Post count: 35senkunParticipant03/27/2016 at 17:51Post count: 35senkunParticipant03/27/2016 at 17:41Post count: 35
I would not rule out bad cards just yet. If the only sd cards you have tried are just the two Sandisks, I would say get another verified compatible card (8/16/32gb) of a different brand before anything else. Make sure to get a legit card from a trusted seller, and check it with either H2testw / FakeFlashTest / ChipGenius first to confirm.senkunParticipant03/26/2016 at 10:33Post count: 35
[quote=121529]I know this is resolved but I feel a simpler/neater way to do this is to rename the “samples” folder “.samples” this will make it a hidden folder and it wont show up in the list of games. You will still have to edit mame.cfg and add the “.” to the samples pathname.
Thanks for the insight, just went through the same situation and ended up doing the same thing for .artwork and .samples directories.senkunParticipant03/25/2016 at 17:31Post count: 35
[quote=121431]Can someone tell me how to disable the retropie config screen in the main emulation selection section? my machine is almost done and I don’t want people to be able to go to the settings and make changes by accident…
comment out the entry for the retropie section in
/etc/emulationstation/es_systems.cfgsenkunParticipant03/25/2016 at 17:21Post count: 35
[quote=121362]changed Windows 7 to 10 and my cable supplier as well (with router change too) so I d notknow which of these is the problem.[/quote]
Oh well, then you’d have to isolate the cause down. No easy way if you had as you said,
changed Windows 7 to 10 … cable supplier as well (with router change too) …
Good luck mate.senkunParticipant03/24/2016 at 14:35Post count: 35
You need to be more specific, which Retropie version? Pi 2? or Pi 3?
“sometimes works but sometimes (the more) doesn’t”
“many times does not connect and little ones does, but soon disconects suddenly.”
sounds like you’re on a Pi 3, if you are try this first before anything else;
sudo iwconfig wlan0 power offsenkunParticipant03/21/2016 at 14:36Post count: 35
[quote=120906]I swear I really, REALLY tried abolutely everything about it before even asking for help.
-Im actually using Retropie 3.6 in Raspberry Pi 3.
It looks like the Raspberry is not connected to Wifi but…
…it is. Because it clearly show it here.
New install? Did you update Jessie after install? If not then your wifi connects but there’s a bug with power management that drops wifi after a couple of seconds. It will still show that you’re connected.
Before updating, try this quick fix and see if it works to get you connected. Open up terminal and type:
sudo iwconfig wlan0 power offsenkunParticipant03/18/2016 at 19:54Post count: 35senkunParticipant03/18/2016 at 19:02Post count: 35
I’m not sure why I had (similar) controller issues with dreamcast running retropie 3.6 on my Pi 2
but when I got my new Pi 3, only thing I had to do was set up my controller via the start up input configuration prompt, and all my buttons were perfectly mapped for dreamcast this time.
as a last resort setup your controller input again?
F4 exit emulationstation
the configuration prompt will appear again.senkunParticipant03/17/2016 at 08:32Post count: 35
Just in case it may help someone else, a temp fix (and explanation from herb) that worked for robboman and I can be found in this other thread:
Adding a delay before calling omxplayer seems to do the trick.
sudo nano /etc/init.d/asplashscreen
sleep 5(in my case I only needed a 1 second delay) in a new line just before the line where ‘omxplayer’ is called.senkunParticipant03/17/2016 at 08:23Post count: 35
ahaha I just found some time, settled in started digging in the logs, nothing unusual on mine except for waiting on dhcpcd and IPv6 for eth0 which I am not using since on wifi only. I thought I did see a flash of a message on bootscreen about a startjob for dhcpcd so that may be what was preventing the player from running.
sleep 1before calling onxplayer in /etc/init.d/asplashscreen and it worked flawlessly as a temp fix, giving it that one second pause gets me video splashscreen every time all the time now. So yea happy days thanks to robboman and herb.senkunParticipant03/16/2016 at 08:15Post count: 35
[quote=120502]Could be related to the boot sequence- possible some things aren’t loading in time for omxplayer to be called so it doesn’t work.
On both my Pis (Pi2 and Pi3) they have fresh installs of Retropie 3.6, the Pi2 I wiped the c4 8GB sdcard and reinstalled, the Pi3 is brand new with a brand new c10 16GB sdcard.
First thing I did was choose video splashscreen and reboot. After one or a couple of reboots the video stops showing. It’s just like the attached pic from retrocam, bootup then pauses for a bit and then the white ES loading splashscreen shows up.
On a fresh install, What could be the things which aren’t loading in time for omxplayer to be called? Any tips/ideas for us to troubleshoot this?
It’s not a big deal, but it sure would be nice to have a custom video playing :-)senkunParticipant03/16/2016 at 08:01Post count: 35senkunParticipant03/16/2016 at 07:54Post count: 35
yes I did have the same thought and did try carbon as well. I tried various videos, short lengths/small files to large/long duration vids, mostly .mp4 and some .mov, they do play but usually on first reboot and not after. I doubt it’s related to video file issues.
For me, it’s definitely not intermittent. It’s more like plays video at least once on reboot, sometimes second reboot (once I got it to show video 3 times in a row) and then nothing after.
So in my case, video splashscreens works for at least the first reboot after choosing custom. Sometimes it works once or twice after, then stops completely. I can’t say it’s stopped *permanently* as I gave up trying after the 7th or 8th reboot with no video showing.senkunParticipant03/15/2016 at 16:04Post count: 35senkunParticipant03/15/2016 at 16:00Post count: 35
Guess I’m not the only one having this issue. Same thing happening with video splashscreens on both my RPi 2 and 3, both running clean installs of latest Retropie 3.6.
The first reboot after selecting a custom video splashscreen, the video shows, and then perhaps it shows on the second/third reboot too (I wiped SD and reinstalled a few times) but without fail on subsequent reboots there will be no video. Yes, I get that same pause too and can tell that the video will fail to play.
If you turn of autostart of emulationstation and turn it back on, sometimes on reboot you get video splashscreen back and then on subsequent reboots no more video. You can also temporarily get video back if you disable fastboot but it doesn’t stick.
I have no idea how to fix this, so gave up and went with a custom static splashscreen instead of video.
I don’t see anyone else posting about this besides 2 other guys in this thread;
So, that makes 4 of us with this issue.senkunParticipant03/15/2016 at 09:09Post count: 35
[quote=120397]Is there a permanent solution?
If not, how do I create a script that will run this automatically every time it boots up? Or is there an existing script I can add this to?[/quote]
easiest way is to just add the line
sudo iwconfig wlan0 power off
make sure it’s added above
exit 0senkunParticipant03/14/2016 at 07:52Post count: 35senkunParticipant03/13/2016 at 18:20Post count: 35senkunParticipant03/13/2016 at 10:46Post count: 35
for the life of me, I cannot get video splashscreens to work. Never got it to work on my Pi 2, today I received my new Pi 3,
installed a fresh copy of Retropie 3.6 on it,
created a new folder named “video” in /home/pi/RetroPie/splashscreens
put a short 500Kb .mp4 video in it,
selected the folder “video” from the second option in the splash screen menu,
and just got bootup text. No video. On my Pi 2 when I tried it, I got video on first restart and then it just stopped showing thereafter. On my new Pi 3 I don’t even see it at all.
Am I the only one with this issue? Can anyone help?senkunParticipant03/12/2016 at 17:52Post count: 35
Not sure what you did there but try this for your configs/dreamcast/mappings/controller_TwinUSBJoystick.cfg
[emulator] mapping_name = Twin USB Joystick btn_escape = 296 [dreamcast] btn_a = 290 btn_b = 289 btn_c = btn_d = btn_x = 291 btn_y = 288 btn_z = btn_start = 297 btn_dpad1_left = 0x220 btn_dpad1_right = 0x221 btn_dpad1_up = 0x222 btn_dpad1_down = 0x223 btn_dpad2_left = btn_dpad2_right = btn_dpad2_up = btn_dpad2_down = axis_x = 0x00 axis_y = 1x01 axis_trigger_left = axis_trigger_right = [compat] btn_trigger_left = 292 btn_trigger_right = 293 axis_dpad1_x = 0x10 axis_dpad1_y = 0x11 axis_dpad2_x = axis_dpad2_y = axis_x_inverted = no axis_y_inverted = no axis_trigger_left_inverted = axis_trigger_right_inverted = axis_dpad1_y_inverted = no axis_dpad1_x_inverted = nosenkunParticipant03/11/2016 at 18:02Post count: 35
Just went through the same issue of trying to get the DPAD on my generic usb ps3 controller to work with dreamcast/reicast. It may be different for your setup but if I remember correctly this is what I did to finally get mine working;
Select the Dreamcast emulator from the frontend > start > menu > configure
then go through the whole setting up of your controller again, this will write to configs/dreamcast/mappings/nameofyourcontroller.cfg
This should by right map all your controller inputs to the .cfg file but somehow the DPAD and analog stick isn’t mapped and the entries are blank on mine.
Within the configs/dreamcast/mappings/ folder there is a controller_generic.cfg from which I copied and saved these entries over to my .cgf file.
btn_dpad1_left = 0x220
btn_dpad1_right = 0x221
btn_dpad1_up = 0x222
btn_dpad1_down = 0x223
axis_x = 0x00
axis_y = 1×01
The games I have tested working are:
Marvel vs Capcom 1 and 2
Only problem is the sound is choppy on my RPi2, just got my RPi3 today and will see how they run on that. Good luck with your controller setting. If you get your controller working let us know.senkunParticipant03/11/2016 at 17:22Post count: 35
Still trying to figure out why video splashscreen doesn’t work on my clean install. Disabled autostart of ES from the setup menu, then re-enabling it seems to fix the issue for a while, tried 2 or 3 system restarts and video came on fine. Then suddenly it stopped working again.
Can anyone help?senkunParticipant03/10/2016 at 17:18Post count: 35
I have a short .mp4 video in a folder, selected it as my custome splashscreen. Restarted system and it worked beautifully. The issue is that it only works that very first time, when I restart the system the splashscreen video doesn’t work anymore.
So I select the default splashscreen, restart the system, reselect my custom splashscreen video, restart system and it works again. But again only for that one time right after I select it. On subsequent restarts, the video doesn’t show anymore.