[bobbyt]

I want to say both gave me a black screen, but I’m not 100% positive…

I know I always got the black screen, and I usually used F4, but I thought I used the menu option a couple of times…

I’m currently in a downgraded state so I can’t verify for sure….

[bobbyt]

If you are looking to bind it to the controller, I think it might need to be more like this:

input_player1_rewind_btn = “3”

The reason I say this is inside of the custom emulator files custom buttons need the player1/player2/player3/player4 prefixes, so I’m guessing it would hold true to this as well…

[bobbyt]

By default it maps only to A B & Z, as the default Genesis/Megadrive controller had only 3 buttons.

The 6 button controller was released at a later date (I had a Genesis as a kid and I remember upgrading all my controllers around the time Mortal Kombat came out for the home systems).

If you go into the RetroArch config menu (by hitting F1 on your keyboard by default), you can toggle the emulator from 3 button to 6 button mode under one of the menu options…

Once you do this the custom mapping will need to tied to the following buttons:

input_player1_a_btn = “#”
input_player1_b_btn = “#”
input_player1_y_btn = “#”
input_player1_x_btn = “#”
input_player1_r_btn = “#”
input_player1_l_btn = “#”

Note that there isn’t a 1 to 1 mapping of A B C X Y Z on these, but if you play around with them for a while eventually you should be able to figure out which button corresponds to what in 6 button mode…

[bobbyt]

I did a straight FAT format… The format size of the card doesn’t really matter, as it stars with a FAT format, which after imaging becomes a small FAT partition (/boot/) and a larger Linus partition.

Once you boot up with the card you can expand the image to occupy all unused disk space…

To be honest when I did it I never thought twice about the limitations of the FAT format. I just erased the card, imaged it and expanded the main partition once I booted up with it…

[bobbyt]

I think the issue has to do with the starting format for the XML files under:

/home/pi/.emulationstation/gamelists/*/gamelist.xml

By default I think they contain:

<?xml version="1.0"?>
<gameList/>

Which messes with the scrapers. If you manually replace the contents of the files with:

<?xml version="1.0"?>
<gameList>
</gameList>

I then run the scraper, I believe it will work…

[bobbyt]

I’ve determined conclusively that running:

sudo apt-get update
sudo apt-get upgrade

Is what started this problem. I have downgraded and saw the problem go away, upon upgrading again the problem returned.

What I can tell is it appears to be tied to RetroArch emulators. BEFORE upgrading I would notice the command line after exiting an emulator, before ES reloads.

I also notice the command line right after launching an emulator from ES (right before the emulator starts working).

AFTER upgrading, I still see the command line after an emulator is launched, but the moment I exit an emulator the screen goes blank before kicking back to ES…

It appears that the screen is being blacked out after exiting an emulator. That black-out persists after exiting EmulationStation…

For the mite being I’ve restored a backup made pre apt-get upgrade and am working fine… This essentially appears to be a bug in RetroArch under the newest firmware for RPI, and as such should be fixed…

[bobbyt]

I had a slightly different issue, but to fix it I disconnected my XBox controller and connected an alternate USB controller. When I booted back into EmulationStation it recognized the old controller was gone and asked me to setup the new one.

I then reconnected the XBox controller and rebooted and ES re-asked me to configure the XBox controller…

[bobbyt]

I realize this isn’t all that helpful but, I recently upgraded to a 64GB Micro SDHC class 10 card after filling my 32GB card and had no issues…

[bobbyt]

I believe one problem you may run into is that lightguns don’t generally work on non CRT displays (i.e. flat screens).

The Linux drivers might not inherenly be comparable with PI, and (as you mantioned) the emulator might not support them…

My best guess would be no, but the posability exists that they might.

Unless someone has tried it top to bottom, you probably won’t get a clear answer either way…

[bobbyt]

[quote=82547]Could you attach your nes config file? Mine isn’t working and I want the same solution.
Thanks[/quote]

If your controls don’t work at all then you need to run through the controller configuration in ./retroarch_setup.sh first.

This will map the controls for ALL retroarch based emulators (including NES).

If you have done this and you want to CHANGE the controls in NES, this is where the following information comes into play…

I don’t have access right now, but he config lines are almost identical to what is in the default retro arch controller config (that is generated by retroarch_setup).

only difference is the config values must include _player#

for example, if your default control config has:

input_a_btn = 7
input_b_btn = 8

If you wanted to swap these in NES you would add the following to the emulator specific config:

input_player1_a_btn = 8
input_player1_b_btn = 7

input_player2_a_btn = 8
input_player2_b_btn = 7

Obviously you want to make sure you base your numbers off the retroarch controller config generated by retroarch_setup.sh…

[bobbyt]

Alright, this may be a general issue between the keyboard and RetroArch.

Hiting space bar has no effect. Holding 1 has no effect.

In short the only keys that work appear to be the arrow keys, return and escape…

No idea why retroarch can no longer detect the majority of keyboard keys…

[bobbyt]

I placed al my bios files into
home/pi/RetroPi/BIOS

Then created symbolic links when they needed to be in other locations.

I’m a bit OCD so I wanted to avoid multiple copies or copies outside of the BIOS folder…

[bobbyt]

I was under the impression that one couldn’t just add any dos game and get it working…

I’d like to get Descent up & running if it’s possible…

[bobbyt]

Unfortunately I believe I’ve ruled out a software based problem…

I’ve restored an older backup of my card to try and fix the issue. The problem is, doing that has had NO effect on the issue.

With the restore I have ruled out the following as causes:

The keyboard: 2 separate brands, one wireless one wired both have the same issue. Using the keyboard on my primary computer confirms the F Keys are working normally.

The Software: Restoring to a backup from 2 weeks ago, long before this problem started, didn’t fix the issue.

The issue started after a couple of specific steps. I first accidentally hit one of the keys on the keyboard while in an emulator, which triggered ‘mute’. I tried to undo this by successively hitting each of the F Keys. I then exited out of the emulator & re-ran the same game/emulator combination. From that moment on none of the F Keys have worked…

I’m now also noticing hitting the F Keys while in the command line outputs the following:

F1: A
F2: B
F3: C
F4: D
F5: E
F6 – F12: ~ (tilde)

I’ve seen these same outputs being listed by others having F Key issues.

Unless the letter outputs happens by default (which I can’t verify), it may be the key indication that the problem is occurring…

[bobbyt]

[quote=82361]Could you create your own custom bash script that did something like:

if [ -f […]/snes/$1.cfg ];
then
/opt/retropie/[…] –config [….]/all/retroarch.cfg –appendconfig [….]/snes/retroarch.cfg –appendconfig [….]/snes/$1.cfg $1
else
/opt/retropie/[…] –config [….]/all/retroarch.cfg –appendconfig [….]/snes/retroarch.cfg $1
fi

Then replace the entire command with /home/pi/myscript.sh %ROM%
[/quote]

This wouldn’t fix everything…

The problem is that there are still 2 occurrences of –appendconfig in the top call, so one of those will have no effect…

This would fix only ROM calls that don’t have a custom cfg…

I came up with a separate alternative, but I’m holding off on using it…

If I replace the first:
–config [….]/all/retroarch.cfg
With:
–config [….]/snes/retroarch.cfg

AND copy the contents of the all/retroarch.cfg & combine it with the snes/retroarch.cfg it works around the issue…

I’m not real happy with this setup so I’ve held off on doing it…

[bobbyt]

I got around to testing it sooner than I thought…

It actually worked but I ran into a separate snag…

I had to use –appendconfig a 2nd time to ensure all 3 configs got loaded:

–config [….]/all/retroarch.cfg
–appendconfig [….]/snes/retroarch.cfg
–appendconfig [….]/snes/GAMENAME.smc.cfg

The problem is the first -appendconfig parameters are fully replaced by the second. Since I do have configs in that file, they are overridden…

The only work around would be to create a custom config for EVERY ROM which I’m trying to avoid doing… My goal is to only create a couple custom configs and have the rest default to the default…

Every step forward I seem to make I have to take another step back… It’s a bit frustrating…

[bobbyt]

I got an idea a few hours ago that command represents the linux command line. I’m wondering if I could combine a variable deceleration set it to %ROM% and then use that variable in the command…

might just be wishful thinking but I will give it a try one of these days…

[bobbyt]

Isn’t that the default split?

[bobbyt]

If I’m not mistaken it will effect more than just the current Rom. I’m hoping to get something setup with no overhead…

Im just surprised that I can only use the variable once…

[bobbyt]

Ports run old dos games. Doom will run, as will Duke Nukem, all be it I cannot get duke nukem out of demo mode.

[bobbyt]

I’ve seen this same issue, so I’ve reduced the number of emulaters I’m using. One xample is that gameboy games wil work if renamed to gbc and joined with gameboy color games…

My understanding is that it’s a memory issue due to limitations of the Raspberry Pi…

[bobbyt]

On a side note…

I’m using wireless Xbox 360 controllers.

The one downfall I do see is there is a slight delay with wireless,

It’s made some games a bit harder than I remember them, but I do prefer the wireless…

[bobbyt]

Its my guess that it might rely upon DirectX..

Perhaps there methodology might lead to improvements in lower end shaders…

I’m most impressed with what the space invaders became. The new look seems perfect…

[bobbyt]

I’m bumping this because I have the same issue.

Having owned a C64 I remember carts would override the C64 desktop, but that’s not happening here.

The linked page appears to address disk and cassette based games but not carts…

[bobbyt]

Ideally if you can mount it, it should work. It’s just a matter of putting them into the correct folder:

/home/pe/Retro-Pie/BIOS/

That said, I find it a bit easier to FTP into the Raspberry Pi and upload it that way…

[bobbyt]

I appreciate it but like a moron I searched after I posted and got the info I needed…

I finally put the Arcade 84 video I’ve been hanging on to to use…

http://www.cinemarcade.com/arcade84.html

[bobbyt]

Can someone point me in the direction on how to set this up from scratch?

I didn’t even know his could be done.

[bobbyt]

I stumbled across the following thread on another forum which is about hiding the loading command prompts. I haven’t tried this myself…

http://www.raspberrypi.org/forums/viewtopic.php?f=78&t=88408

[bobbyt]

Work perfectly, thanks!\

[bobbyt]

I honestly didn’t experiment with retropie_setup xbox controller configs as I assumed it would just install the default drivers,,,

[bobbyt]

I had a separate post to be able to display an arcade attract loop as a screensaver, ideally the video optioon would bridge this as One would just need to generate a video of an attract loop…

So video is definitely a better idea…

[bobbyt]

I second this. Descent was one of my favorate games back in the day…

[bobbyt]

As of now it can be done by disabling the built in drivers, and installing alternate drivers.

The process I went through to get them working, however, was quite a nightmare… In addition you must remember to manually wake every controller before powering on the PI, or they won’t work properly.

So it would be great if the built in drivers could support the LEDs out of the box…

[bobbyt]

[quote=81861]If what I read elsewhere is correct, this is actually a memory issue.
The problem is more Rome and systems, the more memory needed by emulationstation (as it effectively hods everything in memory).
Also, if what I read is correct, updating to the newest version should help, as it’s taken the background images and compressed them better…
I ran into the same problem at one point, but ended up fixing it by pulling the N64 rooms (since theyre not playable anyway). I actually tried to find the blurry background images at one point to compress them myself but never found them…
[/quote]

It appears the info may be (at least partially) wrong.

I tried adding a single rom for a new system and my white background for SNES came back. I then managed to track down the folder with the background images (/etc/emulationstation/themes) and proceeded to compress all of them to about 1/3 their original size…

After restarting my PI the blank white screen came back… So the size of the background images doesn’t seem to have an effect on this problem…

[bobbyt]

I managed to get around the issue bu setting my system up to use an alternate mirror for apt-get…

[Author]

Posts