4.0-rc2 images are available for testing.

BuZz

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

Every time I try to connect SFC 30, I get a bluez error, no matter which mode i use.

Please open a new topic for help with this - I don't think it can be related to any 4.0 changes (the pairing code is the same)

BuZz

@orbitall2k please can you provide me with a copy of your non working config, and your working config - in case the input configuration script is doing something wrong. thanks.

techiedj

Just updated my rpi3 3.7 to 4.0beta2 and things are kinda broken. Updated setup script, ran top install option, then updated rasbian/kernel/all installed modules. Reboot and my controller won't pair. Tried to f4 out of emulationstation to command prompt to manually pair and froze waiting on prompt. Reboot again and setup keyboard and I can see all my systems still in emulationstation. Go to retropie menu - Bluetooth and froze again on black screen waiting on menu to show up. :(

BuZz

@techiedj please open a new ticket - read the link in my signature first so you can provide as much information as possible.

Nothing has changed with the pairing code btw - but it could be kernel related possibly.

Also try from a fresh image to rule out something with your older install.

orbitall2k

@BuZz After I posted, I was playing again and noticed the error had returned. I did the same procedure and did not work as I had posted. After several other tests, I found the real reason. For the controlerl function using the PIFBA it is necessary that the control is connected by cable when the PIFA is open, otherwise
even the keyboard works. After that you can play for bluetooth unplugging the cable. I did not find most other information on this problem anywhere else, so do not know if it was a bug, it would be interesting that other people could also make tests, even with other controls, as I am using 2 controllers of PS3, one DualShock 3 and other Sixaxis.

pattaboy

Since I updated to the beta I have lost the original splash screen of retropie. probably a known issue but already happened on 3 devices that I have.

Btw I like the manage emulator function where you can delete certain emulators that you dont use. however I think it would be better to call them 'Systems' and then you can delete the system together with the emulator it uses.

pattaboy

Als some rom folders related to their systems can't be deleted. permissions might have changed during the update.

mame-libretro
arcade

these are the folders

BuZz

@pattaboy if updating you will need to reconfigure the splashscreen as the repository layout changed.

Regarding removal - not everything relates to system. Also some systems have multiple emulators. We can't change this at this stage I'm afraid. I'm happy with the current naming.

If you do remove all emulators for a "system" - eg removing all snes emulators, it will remove the entry from es_systems.cfg so it won't show up in Emulation Station.

Will check the folder permissions.

BuZz

the mame-libretro/arcade folders had a mame2003 subfolder with the wrong permissions due to some recent changes - this is now fixed. Updating lr-mame2003 will fix it.

pattaboy

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

Will check the folder permissions.

Yeah I get it now! thanks.
Happy to help!

meleu

@BuZz
[This issue isn't about a 4.0-beta2 fresh install, but I think it fits on this thread.]

I was using the RetroPie Setup 4.0-dev on my raspi1. And I was using a RetroPie module I made and it has a getDepends libsdl2-dev. Everything is fine, this package is already installed. But after an "Update RetroPie-Setup script" (now the version is 4.0-beta2), I received this message when using my module:

...
Did not find needed package(s): libsdl2-dev. I am trying to install them now.
...

I'm sure the libsdl2-dev is installed:

[prompt]$ dpkg-query -W --showformat='${Package} ${Status} ${Version}\n' libsdl2-dev
libsdl2-dev hold ok installed 2.0.4+3rpi

Why the RetroPie-Setup isn't detecting this package?

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.