4.0-rc2 images are available for testing.

glennlake

@BuZz Update. I went into the raspi-config file and set up my location(as i'm in the colonies:-)) and nothing changed there. I think that is controlled by raspian but it's good to know it still works.

glennlake

@BuZz I just installed kodi from retropie and it works like a charm! I am able to control it using my logitech f310. So far, so good.

BuZz

There is a new firmware/kernel out - Please can people sudo apt-get update; sudo apt-get dist-upgrade on the new image also and give the new kernel a test.

herb_fargus

@BuZz I'll give that a go as well. To anyone else there are some users reporting inconsistencies with multiple xbox360 controllers if anyone else can help verify that issue that would be good so we can get a fix upstream if it really is a kernel or firmware based issue

orbitall2k

There is no longer supported to VideoPac Odyssey 2 ?

glennlake

@BuZz OK... I've upgraded the kernel and firmware and no glitches yet. Is there a list of things you would like us to try? I'm not that big gamer and I don't do much, but I would be willing to test different configurations. I just thought of something. Could you make up a list similar to the list for reporting trouble on this forum? Maybe a testing report to fill out? Forgive me if you have something like this on the wiki as it just came to me.

BuZz

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

There is no longer supported to VideoPac Odyssey 2 ?

It's available from optional packages

BuZz

@glennlake I don't think we do have a checklist or anything. People all have different uses, so hopefully if people just do what they normally do, any issues will be noticed.

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

orbitall2k

@BuZz Thanks!

orbitall2k

I'm using PIFBA to run the neo-geo games, but when I enter the game does not work any command, or on the keyboard and not the PS3 controller. Already I edited the file /opt/retropie/emulators/pifba/fba2x.cfg several times, deleted and created based on the template and nothing,

I managed to work, Downloading PIFBA from GitHub, extracted only the fba2x.cfg file e copy to dicretory of pifba, and works

wget https://github.com/digitalLumberjack/pifba/releases/download/0.3/pifba-0.3.zip
sudo unzip pifba-0.3.zip fba2x.cfg
cp fba2x.cfg /opt/retropie/emulators/pifba/

Not sure if it's a bug because it does not test earlier, anyway I thought it best mencinar here in the forum. I'm sorry if it's not correct, =)

lilbud

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

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.