@jamrom2 said in No artifacting in lr-atari800 anymore: New build updated to 4.8.5 script:

@mitu ok, that works. I just save a config for each game. Thanks a mil!

So now the 5200. Why am I getting a pop-up when I start a game that reads "Atari800: 800 cart not found in DB".

I have the system selected as 5200 Super System in the Core Settings. The machine is listed as "Atari 5200 (16 kb) in the Atari800 emulator menu as well. These are the same roms I've been using for every build since my Pi2 days. Never seen this error message before. Thanks in advance.

Nevermind... Rom issue. Apparently it doesn't like .bin files anymore. I switched to all .a52 and all is working!

@lebonhomme said in IPEGA PG-SW002 Dual joystick on Retropie:

Is it a driver problem?

Most likely yes, you bought a gamepad that only supports a Nintendo Switch, so a separate driver is needed on Linux (which is what RetroPie is built on). If the hid_nintendo driver is not working with it, then it's probably not compatible.

Do you have a Nintendo Switch ? Any reason to choose this controller for RetroPie instead of a PC compatible controller ?

I have too Logitech F710 and i have saw this issue with Gran Turismo 2 and lr-pcsx-rearmed. During the race, sometimes, the controls are freezing, for example, i can't brake or turn the car. To fix this i have increase the psx cpu speed from 57 to 67 for this game. I didn't notice it with other emulators because i use the controller only with the games that support vibration.

I have saw the same issue with the same game and controller with other gaming distro and is more noticeable there.

With Logitech F310, that is not wireless, i don't have this issue.

Hi @mitu ,

Yes, that worked! Thank you so much! I remember I renamed this file, I didn't realise those lines were needed.

Thanks a lot!

@ModernPie Your config.txt have gpu_mem=64512. Maybe i am wrong, i believe this setting it is not necessary for a RPi4. Except that, 65MB for gpu memory is very low value .

@mitu My apologies for not reading through that read first post. Nevertheless the problem was exactly what you said. I made sure that everything on the back of those little controller boards was plugged in exactly the same on both sides now the only problem is the joystick orientation has to be flipped around because it is reading backwards should be good. Thank you for your help I appreciate it.

I already fixed it myself - LOL!

@rogeriol said in Fullscreen is always on when starting an arcade game:

If I leave the resolution adjust to best fit the tv, 4k is selected and I believe this could tax the rendering on performance in RetroArch.

https://retropie.org.uk/docs/Pi4/#4k-video-display

@rogeriol said in Fullscreen is always on when starting an arcade game:

I changed resolution on raspi config to 1280 720 to be easier on the rendering

pi4 is very capable of doing 1080p so i would use that, using the method in the previous link.

@ase1981 said in PS3 connected by USB on RPI4 running most recent Retropie:

However I am confused about the "plug and play" sync when using USB. Once it is synced, will I be able to disconnect the USB wire and still use the controller?

For a simply USB connection, the controller doesn't need to be 'synced', you can just press the PS button and it will start working, i.e. you can configure it and it will be available for the emulators included.

I don't want to be tethered to the RPi.

Using USB, it won't be 'tethered' exclusively to the Pi, that happens only when you pair it via Bluetooth.

I see there are bluetooth syncing options available, but it looks complicated and I would rather avoid that if possible.

It's really not complicated and I think you should give it a try.

Also is it possible to have more than 1 ps3 controller synced and running at the same time for 2 player games?

Yes.

@mitu

I've already done that, a number of times.

There's something more complicated going on here.

I attempted a completely fresh install to track my progress better step-by-step.

It's here: https://retropie.org.uk/forum/topic/34489/continued-sound-issues-some-kind-of-bug

There seems to be:

A bug somewhere in the RetroPie audio script since 4.8 (whatever update coincided with the ".asoundrc is no longer being used" message).

Why would raspi-config generate .asoundrc when we should be using /etc/alsa/conf.d/99-retropie.conf? Why multiple config files for the same thing?

Something kind of bug or interaction with omx player.

I think most of those who are posting with lvl0 volume mixer issues who aren't helped by your guide are stumbling because they have omx player enabled.

It looks very nice and I hope it will be possible to have this in RetroPie. Without being a developer, I think it is unlikely that we will see the latest version of this emulator in RetroPie, because of the minimal requirements set by the developer.

You can't change the name of the controllers, at least not the ones that show up in the selection script. They come from the OS and cannot be controlled from userspace. The input_device_display_name option is useful just inside RetroArch (shows just a friendly name for the device), so that won't help in the selection script.

So yesterday I had a weird error. I thought why don't I put the nvme mount with option exec into /etc/fstab. I did that and after that it would only boot into emergency and I couldn't recover anything. I tried adding the shell to cmdline.txt but nothing helped. So I decided to completly redo my retropie setup. After redoing everything, I tried again to build kodi with all the options and it just worked fine.
No errors nothing, it just went up to 100%. I installed it with sudo make install and it works.
:D As stupid as this seems it probably was some bad configuration which still existed from my first tries.
I want to thank you for your help, after I remounted my drive I thought what a godsent it would have took me atleast weeks to come up with this if ever. :D
So this thread can be closed now.

@Lolonois
This did work, thanks :)
I don't know what I did, but I made a fresh RetroPie flash again, then run the install twice and it worked

@louis1987

I don't have any lag with a Pro 2 without a dongle. (Edit: I also use two simultaneously)

First things first: Update your firmware. Use the 8BitDo application from their website.

Next: make sure background is selected under Bluetooth options to keep it initialized.

Which selection (SADX) do you have underneath your controller? Is it configured properly?

Here is a cfg with D input that should work well.

And here is the cfg I use with X-input.

Make sure it is showing the pop-up that the configuration has been added when you start a game. Sometimes I've noticed lag when the controller was working, but was autoconfigured in some way by RetroArch rather than using the cfg file.

If you are still noticing serious lag it may also be due to your case. Drill some holes in it. (not joking. had one of those shmansy metal cases and couldn't get Bluetooth working right with the controller basically on top of it. Then bought an NESPi case that had an SSD slot and the unshielded SATA connector really screwed with the Bluetooth / wifi- an RPI4 a dinky 3d printed plastic case with a good heatsink / fan is your friend)

Get all the basic thresholds and everything working right in the cfg to your liking as close to perfect as you can before you start adding layers of hardware and configuration complexity. Adding complexity to your system configuration outside of retroarch etc. will also likely be lost / not salvaged if you attempt a reinstall.

More hardware, more changes = more headaches down the line.

Keep it simple, focus on basics.

Good luck.

@dmmarti Ok then. Thanks! I'll use the mouse for MYST :)

Normally you'd compile it manually and add it as a separate emulator, but the current version doesn't compile on current RetroPie (Pi3/Pi4). You may wait until the new version of RetroPie (based on the Raspi OS bullseye) is released and the standalone flycast will be installable.
I've started working on a RetroPie module to integrate it, but due to some rendering bugs and the aforementioned incompatibility, I didn't add it to RetroPie proper yet.

@mitu you, my friend, are a genius (and this is really a stupid bug)
Yes, the hostname was Inwin as that particular system lives in an Inwin mini-ITX case. Changing the hostname of the system fixed it!