@alfredox123 that's good to know

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

https://retropie.org.uk/forum/topic/1640/xbox360-wireless-controllers-receiver-connectivity-issues/17

Please provide information when posting - https://retropie.org.uk/forum/topic/3/read-this-first

Did you read through https://github.com/retropie/retropie-setup/wiki/retroarch-configuration ?

Thanks for the info.
I knew jstest-gtk. I didn't know it is available via console, too.
I'm gonna test it with a USB gamepad first, to check if it's what I need (I suppose so). NES/SNES controllers test will take a while, since I need to prepare the interconnection board. Maybe I will do a quick test with jumpers.

Thanks everyone!

I found the solution for my setup. In short, the solution was to use the audio on my TV rather than my home theater system.

My Setup My setup is a small home theater, not a dedicated display for retro awesomeness... Raspberry Pi 3 HDMI output to TV TV volume all the way down Optical S/PDIF out to Bose speaker system

As it turns out, this is okay for some MAME games, not frogger or most anything that needs samples. It sounds like some of the audio durations are too short to come through the system. Perhaps it needs to un-mute the Bose amplifier and fade in, but by then it's too late to hear anything more than a slight pop.

Solution Raspberry Pi 3 HDMI output to TV Use TV volume (don't route audio through home theater, it can be plugged in but not used)

I put all of the config files back to default, I think..., and all of my mame and nes games seem to sound good with some quick testing.

All is well in retro land. I hope this helps someone else!

No problem. If you do make a clean install, check out the video to explain how to make RGUI changes stick.

@smoothmalik Please format your posts - I have fixed your post above. https://retropie.org.uk/forum/topic/3/read-this-first

change the aspect ratio (see configuration editor).

@Cole_48

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

https://github.com/retropie/retropie-setup/wiki/Managing-ROMs

No experience with the GameStick unfortunately, but in relation to this:

@Dopy25 said in Gamestick (bluetooth) controller:

I also attempted to connect a PS3 controller, but after plugging it in to charge and running the setup for it, the original controller does not light up at all, I am hoping this is unrelated.

You cannot currently use the PS3 controller drivers and the normal bluetooth stack at the same time, so that may be why the GameStick no longer connects after trying the PS3 controller.

@BuZz said in Retropie 3.8 Bluetooth Configure Issue:

you cant use ps3controllers and the built in bluetooth stack at the same time currently. Known limitation of the ps3 pairing software.

@Concat it is - and so the prebuilt binaries have been downgraded because of this.

@herb_fargus Thanks Herb! I've been in Raspberry Pi longer than RetroPie and in linux longer than both. :-}

Which version of MAME are you using?

@Loatman Glad you liked the guide. Hopefully we can resolve this issue with startx; I've run through the installation instructions at least four times, using three different recent versions of Raspbian Jessie on a Pi 3; it'd be good to work out what the issue is.

The clue may be in you saying you don't have an 'exit to command line' option.

It's a little confusing as you seem to have the system configured to boot directly to the console, which happens when you use the Raspberry Pi Configuration tool (Raspian desktop, Menu, Preferences) to select Boot to: CLI. Setting this option is also what adds 'exit to command line' to the Shutdown menu in Raspbian.

Did you set your system to boot to the command line in some other way?

Just to clarify, is the prompt where you type startx the main console - e.g. does you Pi boot, scrolling a few pages of status messages, and leave you with a full-screen command line?

When you run startx what happens? Do you get an error message?

Did you use the option to resize the filesystem (assuming you weren't using the latest Raspbian image, which seems to run this automatically now)?

You can check the amount of free disk space from the command line with:

df -k

Filesystem 1K-blocks Used Available Use% Mounted on /dev/root 61271084 36856840 21869428 63% / devtmpfs 437064 0 437064 0% /dev tmpfs 441400 67696 373704 16% /dev/shm tmpfs 441400 6268 435132 2% /run tmpfs 5120 4 5116 1% /run/lock tmpfs 441400 0 441400 0% /sys/fs/cgroup /dev/mmcblk0p1 61384 20960 40424 35% /boot tmpfs 88280 8 88272 1% /run/user/1000

My system has a 64GB SD Card. In the above example, the main partition dev/root is showing a total of 61271084 1k blocks; divide this by 1048576 to obtain 58.43GB total, of which 63% is used

Btw: apologies for the delay in responding, I didn't have 'watch' set on the thread.

@Joebo happy to help - glad you got it working

Just a (probably daft) thought: how unreachable is "unreachable"? Completely or just from where you're set up? All you have to do is temporarily get the pi on the network and use SSH to set up the wifi from the laptop. Think you can start RetroPie headlessly. You'd have to work out the IP address etc, but I think that would work.

Also, assuming the laptop has ethernet, you could directly connect it to the pi via a crossover cable - though tbh, getting your hands on a usb keyboard seems easier (and they always come in handy)

@Kristopherson05 you won't find help for that here: https://retropie.org.uk/forum/topic/2/forum-rules