@Clyde I think Linus did a video about it to end the debate once and for all. In the end, it didn't matter because temps were the same.

@cedric5555 I tried the game in mame2003plus. Audio is not perfect but it's there. If you shoot while the intro music to level 1 is played, the music is cut until the main level 1 music starts, then it seems to be fine. With fb-neo, overall all the volume was a bit lower. when the intro music is played and you shoot, the music is not interrupted and you can't hear your shooting until the main level music starts.

I don't know which one's right, but fb-neo might be the better one. I'm using a pi4 so it might be too slow on a pi3.

New cores are not automatically added to RetroPie, someone has to add it - either one of the developers or by submitting a PR (pull request, request to change) to the Github repository of the project.

Hm, it might be something with the new RetroArch version and bezels. I don't have bezels in my installation, but I frequently use shaders, so I don't think the shaders have any influence.

Let's see if we can reproduce it.

@mitu said in Custom Collections Not Showing Games/Roms:

If your collection ROMs are not part of an existing system, they won't show up. So if you created a roms/cps1 folder and put the ROMs there, then created a collection with the filenames of those ROMs, that won't work.
EmulationStation needs to know that roms/cps1 is a system, you probably had - in your previous build - cps configured as such.

If that's not your exact setup, then you should post the configuration files for EmulationStation's system list and the custom collection you've created. And it would be nice if you added the info asked in https://retropie.org.uk/forum/topic/3/read-this-first, just to know what version of EmulationStation/RetroPie we're talking here.

@mitu Thank you for your reply and I apologize for missing the other information. As soon as you mentioned the es_systems.cfg file was the moment I realized "yup, that's not there". All is good with this build now. Arg I knew it was going to be something silly.

i feel stupid, thanks alot

EDIT: wow performance is absolute garbage, how can this be, i looked in some forums, and everybody is like "oh you need dual core" dude i have a quad core 3.4 Ghz i7? Is it the settings or is it ubuntu itself?

Something I can do?

As @Thorr69 said, right now the PI4 model is not fully supported by RetroPie. If you flashed a Pi2/3 image, it won't work on the Pi4.

You can manually install RetroPie on the PI4 following the Manual installation guide. Support for this new model is ongoing and if you're just starting with RetroPie (or Linux), then is best to wait until an official release that supports the Pi4 will be announced.

Found an issue with source code. Pull request are pending.
https://github.com/libretro/libretro-atari800/pull/38

Ok thanks

Wow! I am literally blind how did I not see that when I looked in the config before...

Thanks so much! This works perfectly!

@PhoenixFlood said in Bezel Project gone from menu:

How can I get it back?

Probably by re-installing it - https://github.com/thebezelproject/BezelProject.

@pieguy123 said in Flycast and Reicast not emulating Capcom Vs SNK 2 correctly for character select screen:

I’m running the Japanese version.

I'm running the JP version (http://redump.org/disc/43772/) is there an US version ?

Update:

Updated the RetroPie-Setup script and all OS packages and restarted the Pi. This got the Bluetooth to connect (unreliably, it still fails to register about 1/4 of the button pushes I make). Frame rates are still very poor but I think that might just be the state of RetroPie on Pi 4 at the moment.

@muldjord I will give this a go to see if I can find out what is going on.
Either that or I will manually edit the files with the correct revision names from my previous scrapes.

Appreciate the help @muldjord and @mitu

Thanks

Jimi

There isn't one - basically if you pair it to a device, it will stay paired to that particular device. If you want to move it/connect it to a different device (PC/Pi/PS4), you'll have to do the pairing again.

So apparently I'm an idiot. Following the guide over at Reddit, I missed one thing. I had the mini-hdmi cable plugged into the second port and not to the port closest to the power supply. Looks like everything is working now.

@RGCTech As I said, support for the Pi4 is ongoing and some bits might not work or function as they were on the previous PI models.

Try leaving aside the resolution change, since it's not currently not added to runcommand on the PI4. Use the native display resolution - which you can set it manually to 1080p if it's not automatically detected by using raspi-config from the RetroPie menu.