RetroPie 4.3.17 Stretch images
-
@meleu
Joystick selection doesn't seem to work anymore on this image.Example for NES, with Dualshock3 selected for player 1 with "by name" method :
pi@retropie:~ $ cat /opt/retropie/configs/nes/joystick-selection.cfg input_player1_joypad_index = "Sony PLAYSTATION(R)3 Controller #1"pi@retropie:~ $ cat /opt/retropie/configs/nes/retroarch.cfg # Settings made here will only override settings in the global retroarch.cfg if placed above the #include line input_remapping_directory = "/opt/retropie/configs/nes/" input_player1_joypad_index = "0" # input_player2_joypad_index = "1" # input_player3_joypad_index = "2" # input_player4_joypad_index = "3" #include "/opt/retropie/configs/all/retroarch.cfg"pi@retropie:~ $ cat /dev/shm/runcommand.log --- start of joystick-selection log joystick selection by name is ON! joystick indexes for "nes" was configured joystick indexes for "all" was configured --- end of joystick-selection log Parameters: Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fceumm/fceumm_libretro.so --config /opt/retropie/configs/nes/retroarch.cfg "/home/pi/RetroPie/roms/nes/Dr. Mario (Europe).zip" --appendconfig /dev/shm/retroarch.cfgStill the controller for player 1 is the other one (Hori Fighting stick mini)...
Edit : tried with other systems : same behaviour
I also tried to configure 2 PS3 controllers as player 1 and 2, same. Player 1 stay with the Hori stick, Player 2 is mapped with the first PS3 controller.Edit again : After some tests I checked the jslist files :
pi@retropie:~ $ cat /tmp/jslist. jslist.2Nyz jslist.3XSC jslist.hfJr jslist.Tbq2 jslist.tmyw jslist.UUnk pi@retropie:~ $ cat /tmp/jslist.* 0:Sony PLAYSTATION(R)3 Controller #1 1:HORI CO.,LTD. Fighting Stick mini 4 #1 0:Sony PLAYSTATION(R)3 Controller #1 1:HORI CO.,LTD. Fighting Stick mini 4 #1 0:Sony PLAYSTATION(R)3 Controller #1 1:Sony PLAYSTATION(R)3 Controller #2 2:HORI CO.,LTD. Fighting Stick mini 4 #1 0:Sony PLAYSTATION(R)3 Controller #1 1:Sony PLAYSTATION(R)3 Controller #2 2:HORI CO.,LTD. Fighting Stick mini 4 #1 0:Sony PLAYSTATION(R)3 Controller #1 1:Sony PLAYSTATION(R)3 Controller #2 2:HORI CO.,LTD. Fighting Stick mini 4 #1 0:Sony PLAYSTATION(R)3 Controller #1 1:HORI CO.,LTD. Fighting Stick mini 4 #1The strange thing is The Hori Controller is USB connected (and never disconnected), so it should always be index 0 (what seems to be retroarch view)...
But his index in your script changes according to the PS3 controllers connected.@psyke83 Could it be that your sixaxis module somewhat forces the index of the PS3 controllers to the first ones, regardless of the already connected controllers ?
(That would explain the active led 1 on the controller, before upgrading when I connected a DS3, the led 2 was on, because of the arcade stick being the first) -
@sano said in RetroPie 4.3.11 Stretch images for testing:
Joystick selection doesn't seem to work anymore on this image.
:(
Thanks for the heads-up. Will try to check it when I find some free time.
-
Thanks a lot @meleu ;)
And try to enjoy your free time, this is not so critical :)I think I narrowed it down to the jslist executable.
Here are 2 results before and after powering on a DS3 :
pi@retropie:~ $ /opt/retropie/supplementary/joystick-selection/jslist 0:HORI CO.,LTD. Fighting Stick mini 4 pi@retropie:~ $ pi@retropie:~ $ /opt/retropie/supplementary/joystick-selection/jslist 0:Sony PLAYSTATION(R)3 Controller 1:HORI CO.,LTD. Fighting Stick mini 4Whatever, Retroarch still sees Hori as the 1st controller and DS3 as the 2nd, hence the issue...
If it can help, from the OS point of view, Hori is /dev/input/js0 and DS3 is /dev/input/js1 -
I'm not too familiar with the controller order stuff, but isn't the HORI controller a PS3-compatible controller? That means it'll use the hid-sony driver.
That's a relevant detail, because the old
ps3controllerdriver works differently. The sony_hid driver (with or without my module) would use the nameSony PLAYSTATION(R)3 Controller, butps3controller(assuming you use the DS3 via bluetooth) selects the namePLAYSTATION(R)3 Controller, and it's enumerated through a uinput virtual input device.If this is a sixaxis bug (or if not a bug, different behaviour from the driver), then it's off-topic regarding the stretch image and I would suggest continuing the discussion in my thread to keep this one on track.
FWIW, I have two official DS3 pads, and they seem to select the correct led corresponding to the controller number.
-
For information, I updated today, including OS packages, and the console autologin option reverted back to false, resulting in a console login prompt at boot.
I had to reconfigure it through raspi-config in order to boot to ES.
If someone could try to reproduce this... It could be an upstream bug. -
@sano I've seen this also. It is an upstream bug (unless they somehow wanted this by design, which I doubt).
-
@sano It's caused by the systemd package update - from the upgrade log
Setting up systemd (232-25+deb9u2) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Removed /etc/systemd/system/getty.target.wants/getty@tty1.service. Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service → /lib/systemd/system/getty@.service.I will report this upstream.
To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first
-
Issue opened here - https://bugs.launchpad.net/raspbian/+bug/1755811
-
4.3.14 stretch images are now available in the first post.
I will be testing them out on my Raspberry Pi 3 B+ when it arrives. But the packages are up to date, so they should work.
To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first
-
@buzz Nice, I was wondering if you saw my post about this.
Tagging interested people from other threads : @ganondork @pjft @tashman
Thanks for them, I didn't buy a Pi 3B+ (not yet). -
Looks like there may be a problem with the images - as I can't boot them here from a quick test. Possibly due to upstream Raspbian changes that are incompatible with the build script. Will update with more information soon.
[edit] Actually it could be my desktop/build system, as I updated it recently.
[edit] It was: They are missing the fat partition :-)
mkfs.vfat: command not foundHave fixed up the image builder dependencies. Currently building 4.3.15 images.
To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first
-
@buzz Got a 3B+ already. I'm not super-advanced, but happy to use my extra card with the new Pi to see if and how things work. Ping me when you have what you think is a working image and I'll grab it.
-
4.3.15 stretch images are now available in the first post. They should work on the Raspberry Pi 3 B+ but I have not yet tested. They boot on my Raspberry Pi 3 Model B.
The images are based on the latest Raspbian Stretch Lite.
-
I can confirm the 2/3/3+ image works correctly on the new Raspberry Pi 3 Model B+
To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first
-
@buzz you happen to have the wifi or the network with pi 3b + and 4.3.15?
-
@mikozzz Just tested LAN - for Wifi on the new Raspberry Pi 3 Model B+ you need to set the country (same as with Raspbian Stretch)
WiFi is disabled until wireless regulatory domain is set (Pi 3 B+ only)
- The domain can be done through 'Raspberry Pi Configuration' (rc_gui),
'raspi-config' or by setting 'country=' to an appropriate ISO 3166
alpha2 country code in /etc/wpa_supplicant/wpa_supplicant.conf.To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first
-
@buzz I can not find the network with the network too , i use winscp
-
@mikozzz that's not enough information for me to go on. Can you see the internet from the RPI ? Did you enable SSH ? How is your RPI connected?
To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first
-
@buzz ^^ not much slept sorry obviously
-
The .15 image boots up fine for me.
No, i can't see my wifi networks straight away (i have both 2.4 and 5.0).
Found the setting to set Wifi Country (Canada for me). Pi asked for reboot, which i did. Now i can see both 2.4 and 5.0 networks. That got me an IP so i assume all is well.
edit:
I also set Pi name and password before looking at the wifi stuff.
Wifi indeed works as it can find RPie Setup Script and a couple of themes.edit:
Based on a quick test with N64 Rogue Squadron, the music is still pretty scratchy and the game sluggish as usual. However, N64 Mario Kart seems better on both counts than I recall.
Finally, I can't seem to get my Mac Transmit app to connect. I can browse it in the Finder just fine, though I always found Transmit gets me to a higher (root?) starting point. I can still connect via Finder or Transmit with my old Pi fine. Yes I've enabled SSH. Transmit settings are identical for the two devices, except for the IP address, which I've set aside for each device in my router.
Oh well, enough for now :)
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.