4.0-rc2 images are available for testing.

BuZz

Because it wants a newer version.

meleu

@BuZz Maybe a clearer message would avoid this question.
Thanks for all the good work.

pattaboy

installed a fresh image and updated via retropie setup. Just wanted to play some PSX and the L2/R2 buttons won't work. I'm sure it is a bug.

I'm using a dualshock 3 controller and installed the PS3 drivers from the retropie setup.

tekn0

I noticed an issue with ps4 dualshock 4 controllers not assigning the right trigger or right shoulder buttons in 4.0 beta 2. The emulation station config controller input wizard seems to just jump over the right triggers half the time when trying to config. Also if config was successful retroarch cores do not use the triggers. Can anyone else confirm?

Edit: Used the button skip function to skip the trigger and shoulder buttons. Then went back up after the OK screen and held A to set them.

Was the Emulationstation Bug.

me

the lxde desktop doesn't work not even after i manually edit desktop.sh in ports to say:

#!/bin/bash
startx

than it says
x: user not authorized to run X server,aborting

when i put sudo infront of startx it works
and when i exit emulationstation and use startx it also works
before i made the change it was like this

#!/bin/bash
"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 PORT lxde

but then it jumps back to emulationstation

also when installing descent i get descent2 only no descent1
on a fresh 4.0-beta2 + pi-3 + oficial 7" touchscreen

herb_fargus

@me said in 4.0-beta2 images are available for testing.:

x: user not authorized to run X server,aborting

dpkg-reconfigure x11-common set to anyone

Riverstorm

@BuZz said in 4.0-beta2 images are available for testing.:

I am interested if the new kernel update makes any difference to those with trouble with 2x 360 controllers and xboxdrv.

I am probably missing it but where do you load the driver XBOX 360 controllers with 4.0-beta 2? Before I would do:

Option 3 (Setup / Configuration (to be used post install)
Option 829 (Xbox / Xbox 360 gamepad driver)
Option 3 (Set number of controllers to enable (currently 2)
Option 1 (Enable xboxdrv)
Reboot for changes to take effect

I was going to do some testing with 4 controllers and MAME.

BuZz

the package / menu numbers are dynamic - so they can always change.

it's under packages / drivers

Riverstorm

@BuZz said in 4.0-beta2 images are available for testing.:

the package / menu numbers are dynamic - so they can always change.

it's under packages / drivers

Thanks Buzz, I was able to get it loaded but there's some wonky things happening.

I'm using XBOX 360's model 1403 with the official Microsoft wireless receiver. I do have 4 wired if you think they would yield different results but in previous builds the wireless has been rock solid.

I had to load from binary a second time and reboot (maybe it was just the reboot but hard to say), then I was able to get controllers 1 and 2 connected but 3 and 4 refused (4-quadrant green ring flashing).

I did a reboot and nothing connected. Maybe to impatient but it's longer than normal from 3.7.

I did a 3rd reboot and just let it sit a few minutes. It seems slower to connect up than previously. At that point I had 3 controllers connected on the proper quadrants with the 4th controller flashing.

I tried several minutes but no luck on controller 4. I shutdown controllers 1, 2, 3 and just tried 4 but still no luck. I then turned back on controller 1, 2, and 3 and all 3 just flashed but never connected.

It's like if you do get them connected and disconnect you can't reconnect again without a reboot. With 3.7 I could connect and disconnect at any time no problem and it would pick an open controller quadrant no problem. Also you could reboot and the controllers would flash but as soon as ES was up they would connect. This doesn't seem to be the case now.

Also a side note after installing from binary and exiting to the main setup menu I tried to reboot but it dropped me back to RetroPie ES Menu. I went back in immediately and tried to reboot again and it worked. It seems if you wander menus (well in this case) and try to reboot it was a no go but if you go in and reboot immediately it works.

BuZz

There are known issues with xboxdrv and the latest kernel (and existing forum threads)

Regarding the reboot - did you update retropie-setup first? A fair amount has changed since beta2 - please update all packages (and retropie-setup - it will prompt when updating).

Riverstorm

@BuZz said in 4.0-beta2 images are available for testing.:

There are known issues with xboxdrv and the latest kernel (and existing forum threads)

Regarding the reboot - did you update retropie-setup first? A fair amount has changed since beta2 - please update all packages (and retropie-setup - it will prompt when updating).

Ok, I did not update before rebooting. I am running an update now on all installed packages. It prompted to update the script first which I answered yes. I said no to the underlying OS packages, is that ok? Will update you once it's complete.

BuZz

you should update everything including os packages for testing please.

Riverstorm

@BuZz said in 4.0-beta2 images are available for testing.:

you should update everything including os packages for testing please.

Ok did a reboot between updates. Updating everything now. I did a double-take as the menu is on the left now. I saw the disclaimer on selling SD cards. That's a true shame but a nice testament to the true awesomeness of RetroPie! ;)

BuZz

The menu shouldn't be on the left - probably due to an issue with control chars and console - try launching it again (sometimes when updating, some of the output seems to mess with the console etc)

[edit] oh do you mean the carbon ES theme ?

Riverstorm

@BuZz said in 4.0-beta2 images are available for testing.:

do you mean the carbon ES theme ?

Yes. It looks quite nice really! :)

Riverstorm

@BuZz said in 4.0-beta2 images are available for testing.:

you should update everything including os packages for testing please.

I updated everything and did a reboot. It's still very eradicate. It seems a hit or miss on if the controller will connect or just flash (green circle).

I had two flashing controllers and did a reboot one connected as controller one and the second continued to flash.

I did a reboot and left all the controllers off. After it fully booted up I powered on two controllers about 3 seconds apart and both connected as controller one (upper left quadrant glowing green on both). The other 2 wouldn't connect at all. So I shut off the two working ones and tried reconnecting them again but neither would connect a second time.

If you get disconnected after you're connected the only thing to do is reboot it seems. You can't always get connected though. I can't find a pattern in why sometimes they connect and other times not. It's very sporadic still.

I have 4 controllers all 1403 (two older from the Modern Warfare 2 era) and two newer. It's a hit or miss on which will connect and which won't. There seems no rhyme or reason.

EDIT: I have to head out for the evening but if there's a next step or any logs I can send you just let me know and I'll get them sent first thing tomorrow.

BuZz

you could try the latest xpad driver instead of the xboxdrv - https://github.com/RetroPie/RetroPie-Setup/issues/1277#issuecomment-233139295

Riverstorm

@BuZz said in 4.0-beta2 images are available for testing.:

you could try the latest xpad driver instead of the xboxdrv - https://github.com/RetroPie/RetroPie-Setup/issues/1277#issuecomment-233139295

Ok will try that. Also something new when exiting the ES menu with F4. I have two errors, both the same:

[ERROR] USBController::on_write_data(): USB write failure: 12: LIBUSB_TRANSFER_ERROR
[ERROR] USBController::on_write_data(): USB write failure: 12: LIBUSB_TRANSFER_ERROR

I have two things plugged in to the USB ports a keyboard and the Microsoft wireless receiver.

BuZz

This is related to the issue. It's a compatibility problem with the current kernel. I've not looked into it yet, but it's likely something that needs fixing in the upstream kernel or in xboxdrv

BuZz

@Riverstorm Please can you try this for me in case it's related to a change in the fork of xboxdrv we are using. Please first update retropie-setup then install the raspbian xboxdrv

sudo apt-get install xboxdrv

then edit /etc/rc.local and change the xboxdrv line from /opt/retropie/supplementary/xboxdrv/bin/xboxdrv to /usr/bin/xboxdrv