Any time mate. Thank god. Was just about to start updating my resume for a new field of work.

@trekdrop I followed this site to put a switch on my pi3 (using GPIO 03 rather than 18 to make it a start/stop switch)and it works fine. "https://www.element14.com/community/docs/DOC-78055/l/adding-a-shutdown-button-to-the-raspberry-pi-b"

@mo418

That's so bizarre. I loaded this page and it was empty and then the replies populated after I posted... Or I stroked out for a while. Why do I taste purple?

@edmaul69 it worked! Thanks!!!

@BuZz said in RetroPie for the Pie and Ubuntu - Same version?:

pix86

OHHH Got it. Learn something new everyday.

-BC

I worked on this a little bit more last night while watching the Rio Olympics and this is what I got so far...

nano /opt/retropie/configs/ports/quake/retroarch.cfg

input_libretro_device_p1 = 3 input_player1_a = "space" input_player1_b = "backslash" input_player1_y = "q" input_player1_x = input_player1_start = "escape" input_player1_select = "tab" input_player1_l = "a" input_player1_r = "d" input_player1_left = "left" input_player1_right = "right" input_player1_up = "w" input_player1_down = "s" input_player1_l2_btn = input_player1_r2_btn = input_player1_l3_btn = input_player1_r3_btn = # Hotkey button input_enable_hotkey_btn = "tab" # Exit emulator input_exit_emulator_btn = "x" input_exit_emulator = "del"

The hotkeys to exit the emulator do not work for me and also the Esc key doesn't show Quake's menu. Right now the only way to exit Quake is to SSH in and administer the killall retroarch command.

If anyone has any further customizations, please let me know.

@battlecat Awesome!

We must go deeper... a 3rd RPi to control the controller

This is the only way I found to do it, if you keep a backup copy of the SD image and work on another copy, you can't really break anything. It is actually quite straight forward as long as you follow the instructions. I started at this part
Resizing a partition within an image file

and stopped here
truncate -s $(((END+1)*512)) imagename.imgThe image was on my Windows shared folder i had mounted in my Ubuntu VM.

I used the info here to mount the Windows Share
https://wiki.ubuntu.com/MountWindowsSharesPermanently

I knew how to then copy the new image to SD and also had a copy of the original in case i stuffed up.

It's all a good learning experience

Thanks buzz. I will re-format the card (SanDisk Ultra 8Gb) Download the image again and try again. Cheers!

@jabberwock101 it was packaged when the build was broken. Occasionally happens.

@dankcushions that will be £50 :p

@backstander I'm running the newest version on my pi3. It doesn work and from what I've read it doesn't work for anyone.

I did see that, but for some odd reason, I interpreted that as meaning that those were just the default, and were overridden by my new bindings. It never even occurred to me that the select part of that would remain after I changed the bindings. Now I know better.

Thank you once again.

Im going to add this here because I ran in to another issue, this time with Retroarch (and because this thread comes up on google when searching)

While the controller worked for the ES menu and other port stuff I had previously configured with 360 controller mappings, the config generation script does not properly find and recognise the controller named "Afterglow Prismatic Wired Controller" and is not creating a config for it under /opt/retropie/configs/all/retroarch-joypads

so consequently, when launching an emulator (NES for example) resulted in the message in yellow saying Afterglow Prismatic Wired Controller not configured. Try as i might, it was not auto generating, and for some reason kept defaulting and regenerating configs for my LogitechF310 which wasn't even plugged in this time.

I had to get around this by manually copying an xbox360 mapping .cfg file I had previously, and replacing as follows.

[/opt/retropie/configs/all/retroarch-joypads/AfterglowPrismaticWiredController.cfg ]

input_device = "Afterglow Prismatic Wired Controller"
input_driver = "udev"
input_r_y_plus_axis = "+4"
input_l3_btn = "9"
input_r_x_minus_axis = "-3"
input_r_axis = "+5"
input_save_state_axis = "+5"
input_l2_btn = "4"
input_start_btn = "7"
input_exit_emulator_btn = "7"
input_l_y_minus_axis = "-1"
input_l_axis = "+2"
input_load_state_axis = "+2"
input_up_btn = "h0up"
input_r_y_minus_axis = "-4"
input_a_btn = "0"
input_b_btn = "1"
input_reset_btn = "1"
input_down_btn = "h0down"
input_r2_btn = "5"
input_l_x_plus_axis = "+0"
input_l_y_plus_axis = "+1"
input_r3_btn = "10"
input_right_btn = "h0right"
input_state_slot_increase_btn = "h0right"
input_x_btn = "2"
input_menu_toggle_btn = "2"
input_select_btn = "6"
input_enable_hotkey_btn = "6"
input_l_x_minus_axis = "-0"
input_y_btn = "3"
input_left_btn = "h0left"
input_state_slot_decrease_btn = "h0left"
input_r_x_plus_axis = "+3"

@Floob I'm sorry for not being clear on first place. I downloaded v3.8.1. I did not install it on top of Raspbian.

@BuZz I'll can try it once I get my hands on it again, although that sdcard have been functioning without any issue with the same very Pi for a while. I've been using a surplus power supply I had laying around, but I don't think it's a power supply issue. I'm not getting low voltage warnings, and I was able to drive the same piece of hardware with external HD's before without a glitch, using the same power supply.

One thing I did try, was to locate a hash for the file I downloaded to check it's integrity (since it's a huge file, and my ISP is having issues recently). I did not find it anywhere obvious, but I also was in a rush, so this may be my bad.