@caver01 Thanks so much. I will try that again. I think that it what I am running Arkanoid and Tempest on.

Jason

Yesterday, I figured out that to use the arrow keys, I have to hold down the control key. So, at least I can use the arrow keys. But, it's not the best solution.

Any help on the joystick issue would be appreciated.

Thank you.

Well, I've solved it myself.
I put it here in case someone serves.

What it does when starting the emulator N64 is to restart the GPIO of the Raspberry Pi and the pins that are configured as output PWM are put to full power.

What I have done to solve it is to insert the following command:

Gpio -g mode 18 pwm

I put it inside the infinite loop that checks the temperature.

I hope that it would be useful to someone.

I had the following error that occurs if you configure a PS3 controller before attempting to configure an 8bitdo gamepad:

Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in msg_reply_handler reply_handler(*message.get_args_list(**get_args_opts)) File "/home/osmc/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 118, in pair_reply dev_connect(dev_path) File "/home/osmc/RetroPie-Setup/scriptmodules/supplementary/bluetooth/bluez-simple-agent", line 38, in dev_connect dev.Connect() File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in call return self._proxy_method(*args, **keywords) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in call **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.bluez.Error.NotAvailable: Operation currently not available

The solution is to remove the PS3 controller driver via the retropie_setup.sh script ([Manage packages] -> [driver]->[ps3controller]->[uninstall/remove]).

Afterward, manually remove all packages/dependencies related to it. Basically any package mentioned in the PS3 controller setup guide:

https://github.com/retropie/retropie-setup/wiki/Setting-up-a-PS3-controller

sudo apt-get --purge remove sixad
sudo apt-get --purge remove sixpair
sudo apt-get --purge remove bluetooth
sudo apt-get --purge remove blueman
sudo apt-get --purge remove bluez-hcidump
sudo apt-get --purge remove checkinstall
sudo apt-get --purge remove libusb-dev
sudo apt-get --purge remove libbluetooth-dev
sudo apt-get --purge remove joystick
sudo apt-get --purge remove pkg-config
sudo apt-get --purge remove python-gobject
sudo apt-get --purge remove bluez-utils
sudo apt-get --purge remove pi-bluetooth

Then,

sudo apt-get install pi-bluetooth

Then follow the normal 8bitdo setup guide:
https://github.com/retropie/retropie-setup/wiki/Setting-up-an-8bitdo-Bluetooth-controller

@columboscoat
You're still quite knowledgeable and helpful though.

Sorry for the trouble man.

@Goose You didn't word anything "wrong" You just haven't supplied any, or at least, very much relevant info. This is a technical forum for users of the software, not the "psychic hotline". Try again.

@mediamogul Ah! Thanks everyone for that info. I was also hoping to increase the buttons you have to press to RESET the game (instead of hotkey+b), but I guess that's not possible yet.

I'm having a similar issue. Thought I'd post here rather than start a new topic, hope that's OK.

My problem is the game starts up and runs fine as long as I leave it in demo mode. The demo loop runs the video and sound just fine. But when I start a game I see Dirk run across the bridge and then the screen goes black. I can hear the game running but can't see anything. By pressing random controls sometimes I'll get the death scene or if I'm lucky, a level I can actually play before it all goes dark again. I've deleted the .dat and parsed many times with the same result.

I'm hoping someone can help me sort this out, thanks. Here's my ls output:

pi@retropie:~ $ ls -Rla /home/pi/RetroPie/roms/daphne/
/home/pi/RetroPie/roms/daphne/:
total 16
drwxr-xr-x 4 pi pi 4096 Jan 19 14:37 .
drwxr-xr-x 63 pi pi 4096 Jan 18 19:15 ..
drwxr-xr-x 2 pi pi 4096 Jan 19 21:09 lair.daphne
drwxr-xr-x 2 pi pi 4096 Jan 19 19:58 roms

/home/pi/RetroPie/roms/daphne/lair.daphne:
total 103684
drwxr-xr-x 2 pi pi 4096 Jan 19 21:09 .
drwxr-xr-x 4 pi pi 4096 Jan 19 14:37 ..
-rw-r--r-- 1 pi pi 16316 Jan 19 21:10 lair.dat
-rw-r--r-- 1 pi pi 893769849 Jan 19 14:42 lair.m2v
-rw-r--r-- 1 pi pi 27496826 Jan 19 14:17 lair.ogg
-rw-r--r-- 1 pi pi 19 Jan 19 20:10 lair.txt

/home/pi/RetroPie/roms/daphne/roms:
total 28
drwxr-xr-x 2 pi pi 4096 Jan 19 19:58 .
drwxr-xr-x 4 pi pi 4096 Jan 19 14:37 ..
-rw-r--r-- 1 pi pi 17906 Jan 19 19:49 lair.zip
pi@retropie:~ $

Try on CLI
amixer cset numid=3 1
that forces headphone output
amxier
Loads ALSA-mixer tool
/etc/init.d/alsa-utils restart
Restarts mixer

@Carbooja no. see http://commonmark.org/help/ (Three backticks for code blocks)

Ah ok thank you. So basicly i neet to change the command to

subprocess.call("modprobe --first-time -r db9_gpio_rpi", shell=True)

and import the subprocess?!

@herb_fargus

do you live in tualatin?

lol unfortunately no, it's only my first PC PIII(Tualatin) name, that i take as nickname.

Does emulationstation work just from the terminal by typing in emulationstation?

yes it works, but now i have another problem, my sixaxis dont mapping correct, can it be a problem of internal bluetooth in my laptop, i need to use external dongle ? Whith my usb controler it work fine.

@dankcushions said in MAME2003, Rgui vs Tab:

when you press tab, where are those control configurations stored?

https://github.com/RetroPie/RetroPie-Setup/wiki/lr-mame2003#mame-menu

They appear to be tied to the retropad mapping so how do they work with the Rgui bindings?

basically all libretro emulators only see the retropad abstraction. so regardless of what controller you use, the emulator will only see 'Retropad A button', 'Retropad B button', etc. if you rebind something using the TAB key, what you are saying is 'Button 1' in mame is changed from 'Retropad A button' to 'Retropad B button', etc.

Perfect, thanks! I missed this in the Wiki.

@benlefou87 Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@benlefou87 Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Ok I fixed this! :)

So for anyone that has this problem in the future this is what I have done:

Update the Retropie script in the retropie config menu Set the screen resolution & shader I wanted to use in the config menu Update from source the kid friendly emulation station add on (I tried uninstalling it first but that bricked the image) Test everything is working, Which for me it now appears to be :)

Rbaker, Thanks for your input.
The kiosk mode I refer to is a experimental emulation station that allows the retro menu and a few other things to be locked out to make them child friendly.
I will also look at getting a bigger PSU.
Thanks.

@MacEns Try going into /boot/config.txt and remove the hash symbol at the start of config_hdmi_boost=4. This will increase the HDMI signal. Or swap out the cable. If it is displaying on and off and your TV is giving you that warning I would say that is your issue. This value can also be changed up or down.

@Murderlol Ah, cool. Glad you got it sorted. Thanks for replying. It just helps others who search the forum with similar issues.

I can't access it but still I know that You can override it by just copy pasting text on the cell with data validation :/
Still just disabling any editing option will work fine. I don't trust any of those sheets but for me they are a list of compatible roms.