@Rcs we have no clue what version of retropie, raspberry pi (also what version of pi) or pc or any of the other stuff that readme says you need to give us info on. If you give us something to start with then maybe someone can help. I would start by going into the file /boot/config.txt and removing the hashtag from the beginning of this line:

#hdmi_drive=2

So it looks like this:

hdmi_drive=2

Then save and exit and then reboot. If you are using a raspberry pi and you dont ftp into your pi then plug in a keyboard and hit f4 to get to the command line. Now type:

Sudo nano /boot/config.txt

Now scroll down and until you find the line that says:

#hdmi_drive=2

Then remove the hashtag so it looks like this:

hdmi_drive=2

Then save and exit by hitting "ctrl & x"at the same time then "y" to save. Then type

sudo reboot

in the command line. Also when in emulationstation hit your start button on your controller, go into sounds and change the volume from 77% to 100%.

If that doesnt work then you need to give us more info on your setup just like that "read this first" link tells you what all info we need.

I’m not sure why my perl installation got broken, but I was not able to fix it. I ended up with a fresh Raspbian installation. Now everything works fine egain.

@trekdrop said in Daphne black screen:

One big question... Do you have badlands running?

I just tried Bandlands. I cannot get it to work. Same issue. Same weird writes in the log file. Black screen.

I did remove the DAT file and it actually did the parsing just fine and when it first started, I saw a glimpse of the "Wanted" sign, which is the first image you see when the game loads, but after maybe a frame of that video, it went black and stayed black. I exited after waiting 10 minutes or so.

I'm sure someone must know??

Thanks a lot!

Think there is ever the chance that the devs might add in before configuring a console controller the option to configure a non-console encoder like iPacs are?

@dankcushions thanks!

Just an update, I fixed the issue and now it's running beautifully. It turns out I was following the directions correctly, but I had no idea I had to remove the #. If I hadn't asked, I wouldn't have known so thank you guys for all your help!

Thanks for your help guys, I will install retropie and then the desktop environment.

Thanks I'm not sure if it is the controller though, I was testing everything on a pi 1 model B and it worked fine every time I rebooted. Granted I wasn't using the powered hub at the time.

I'll try eliminating the hub and report back. If it is just the controller that's fine once the same thing doesn't happen with the arcade encoder :D

http://pastebin.com/jfKLrumc

Pastebin of the STD out file

This is the output of tail -f /tmp/dumps/steam_stdout.txt
When attempting to launch lr-picodrive from inside emulation station that is launched from SteamOS.

@II12yanII

https://retropie.org.uk/forum/topic/3/read-this-first

https://github.com/retropie/retropie-setup/wiki/Playstation-1

https://github.com/retropie/retropie-setup/wiki/Playstation-1#why-arent-my-bin-files-showing-in-emulation-station

So I am going to say installing the SteamOS driver is probably a bad idea seems to have broken standard functionality. Specifically after disabling and removing the driver.
Having to rekick now to get it back to normal.

@mediamogul

That's a good idea in theory, but you're already running into major issues that could very well be isolated to the VM environment and never even be seen when using an actual Pi.

I think your right. Hopefully I will get a RPi3 Model B for Xmas.

Thanks.

I do it that way for my media server, which also runs Win7 and the files are gone, but having never used a RaspPi before I just wanted to double check. :D

If i stay with my original .cfg i can boot on date/hours and move left/right down/up but i cannot confirme with sélect. And just if i change mapping on my .cfg, when i launch it s black screen ans reboot main menu of reicast.why reboot if i modified the .cfg?

So I had some time to think about this while at work, and I think it might be easier to just use that NES to USB circuit (link). By using that circuit, I can combine both NES ports into a single USB plug. I saw some walkthrough examples where somebody had used that exact circuit in an NES, and the ports line up perfectly. I was also looking last night, and found a DB9 to USB adapter that might work well for Sega and Atari controllers. I've only heard of the Raphnet NES adapters from other builds, and don't know how well the Mayflash Adapter will work, and if it will work with ATARI as well.. I'd really like somebody to help me figure out if this is a good option, because I'd really like to have the option to install a way to use original controllers where possible.

Since I'm on the topic of controllers.. I have another major question. Does the system handle correctly the mappings for multiple controllers and types? So far, while waiting for all my hardware, I've been testing with just a Wireless Xbox 360 controller. I also have a Saitek P2500 controller that I was originally using before I got the Wireless Xbox 360 dongle. So does RetroPie/RetroArch still work if I have say.. 2 Xbox controllers? What if I have an Xbox Controller and the P2500? What if I don't have those, and just have 2 NES controllers? What if I'm really crazy and I'm using an NES controller and a Sega Master System controller (they're the same design more or less). Does the system handle multiple controllers, mix and match controllers, or even just 1 different controller per system? Since I'm still in the build phase, I don't have this issue NOW, but I'd like to know if this has come up and if there is a way through it.

Thanks guys! Also, I got my NES console in the mail today.. so I'm getting closer to build time!

@Lyle_JP

The ISO format doesn't make use of a cue sheet. Because of that and a few other format differences, they're really only useful for imaging unprotected, single track CDs and DVDs. You can convert between the two formats, but you'll always get data loss with anything more complicated than a single track disc.