@mbrett you can use "pure". Press "scroll lock" on your keyboard and it will disable "game focus". Keyboard should work fine then.

If you use a BT mini keyboard, you have to remap that command to another button. I used "page up" via the Retroarch menus.

Try it before you use Staging.

Somewhat solved.
I went back into Bluetooth and removed the XBox controller from the paired listing, and then added it back in the usual way, and this time got no error (maybe due to the XPadNeo being installed ?), and then did the Input configuration again, and now the Middle Button + X brings up the menu to quit the games etc, like the Pi3B+ did.

Its super weird as I re-did the Input configuration 3 times and that did not solve it, before I tried removing the controller completely and adding it in again.

There certainly seems to be some sort of issue here, but I am unsure what it is exactly.

Do you have an input override for this game ? If you open the RetroArch menu and go to Controls/Port 1, what kind of device type does it say it is ?

Please add some more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Update: After a pause to address some other stuff around the house I was finally able to rebuilt some of the internals of the Roadcase Cocktail Cabinet. The most recent work items included:

Remove USB Hub, replaced by. . . Mount Meanwell 5v PSU Reroute all USB connections (make longer USB cables) for arcade controls direct to Pi4. Rewire audio and LEDs directly to PSU (instead of USB hub) for power Rewire the mains AC to incorporate a split—Power the Pi transformer and a GPIO-triggered relay Mount and wire the relay in a project box to power the display and PSU (which in turn powers the audio and the LEDs. Remount audio amp, reroute speaker wires. Update my Python script to trigger the relay on another GPIO pin.

It was a lot, but I had to keep it all straight and do everything at once. Before this step, I had a USB hub tying the spinners and trackball controls to the Pi, but also providing power. This was not necessary with a small and cheap PSU. It cleared up some of the bulky power transformers and removed some hardware, but replaced it with other stuff. In the end, this is a bit more complex, but the controls are now plugged in directly to the Pi and I have a relay turning on and off the display.
94C5DDCA-26D6-4826-B968-C6FA03A836D9.jpeg 151A3145-DE7C-45FC-A677-3A48864E164B.jpeg

Sorry, we don't support 3rd party images. Use the image from retropie.org.uk/download and see if you still got the issue, then we can help you.

@winterelf 3rd party builds are not supported by this forum.

If this were a build direct from this forum, the above fix would have worked. The file extension list in the es_system.cfg is the only change you need to make to allow a file to be shown in the game list of each system. It will just show without meta data until it is scrapped. This is also how it shows any images or videos. Once ES reads that file extension in that list, it knows what to do.

So who knows why your build is not doing that. You'll have to ask the team that created it.

@hawkes_84 It comes with more experience in config files to recognise or guess the different comment characters as well as section titles in square brackets. 🤓

@quicksilver thanks. Looks like it's relatively recent and has got some attention, I guess that's promising in terms of it getting fixed soon.

@icer363 said in Skyscraper not showing videos?:

I have it enabled in the settings.

Do you enabled it in the Skyscraper settings or EmulationStation (or maybe both) ?
Note that after you scrape (with videos enabled), you need to run the gamelist generation step again in order for the videos to show up in EmulationStation.

@mitu You made my day. 😄

And of course adafruit put 4gb pi's up not an hour after I posted this. So of course I jumped on it. Now, an hour after that, they are out of stock of 4gb, but the 2gb is in stock.
Oh well, 4gb is overkill, but it's better than scalping prices off elsewhere.

@tango said in AdvMAME in 2021 - on Pi 3 and Pi 4:

@dankcushions said in AdvMAME in 2021 - on Pi 3 and Pi 4:

lr-fbneo has been part of retropie since 4.5 in 2019: https://github.com/RetroPie/RetroPie-Setup/releases/tag/4.5

It wasn't showing up in my emulators, either in EmulationStation. I'm trying to remember from what I've read. Is ~/RetroPie/roms/fba the directory for fbneo ROMs?

yes (and /arcade and /neogeo - see https://retropie.org.uk/docs/FinalBurn-Neo/ )

And am I right that the emulator won't show up on EmulationStation unless I have ROMs in the directory?

that’s right. however you’ll still see it as installed in retropie-setup’s package manager regardless.

i can't stress enough that apt is nothing to do with emulators in retropie :) emulators are installed and updated via the retropie-setup script, not apt. even if they are there somewhere, apt wouldn't install to the same place as retropie, leverage retropie's config scripts, or add the systems to emulationstation, etc.

Okay, that helps a LOT, since I've been bumbling around here, on and off, for a while, and never realized these packages were handled separately from apt.

How are they updated, then? Do I need to update them manually through the script or are they updated automatically?

https://retropie.org.uk/docs/Updating-RetroPie/

My thought would be that if I use a new image and copy the /home/pi/Retropie directory recursively to the new image, that should preserve all the settings, configuration changes, and high scores to the new system. Please let me know if I'm wrong on that.

it wouldn't. for example, (most) config files are stored in /opt/retropie/configs/* etc. You can probably find some info on copying configs across images elsewhere on the forum, or perhaps someone will reply. personally i don't like to copy configs across from older versions - defaults change, emulators change, etc. I think you can end up carrying sub-optimal settings through to later versions. I like to start fresh, or pick and choose specific config files I know to be safe, but that's just me...

With Debian, I can easily do automatic updates so I don't have to go into a system and do admin work. I used to do that when I ran a business where all my software was on a Debian server. I know some people don't like auto-updates, but I never had a problem with things failing or crashing and that way I only had to deal with doing it manually when doing a dist upgrade.

For an arcade system, I'd like to keep that as automated as possible. I have had very little free time in the past decade and I'd rather automate whatever I can.

So how would I handle that with RetroPie, EmulationStation, and the emulators?

the update link above describes how you update retropie, but before we were talking about what was described as a pre-fbneo image, which would indeed be a dist-upgrade (or 2), which is not a supported in-place upgrade.

@Thorr69 said in connect to tv and monitor:

Totally not what he asked about and why are you answering this really old thread?

Spam, really.

@markyb2021 it will work both ways, if it says bluetooth on it then you can connect with that, once you get past the first start up. or they have said

i always have a keyboard to use as my first controller for the first setup part. so i dont know if the 8bitdo can connect with bluetooth while its being used as a wired controller

@folly Sounds like great progress! Ingenious work with the PSP battery.

I bet PS2 is decent for emulation, they are powerful enough in retro terms. PSP seems more fun - I like the handheld retro aspect.

I've got an XBox One and a decent laptop as well, I like modern and retro. There is some messing around to get games to work sometimes on Windows - I had trouble with Jurrasic World Evolution this week, took me a day to get it working (it didn't like booting up in anything other than 60hz 1080p). I'm playing Halo Infinite now as well - it is so good for a free game (only the multiplayer is free though).

@DanTarl

Hi DanTarl - I created a forum account just to thank you for this tip.

I was frustrated by my zero delay encoder going in to disconnect/reconnect loop (led flashing) while using MAME on Ubuntu v22. Adding this to the Grub Linux boot parameters fixed the problem immediately.

The line now looks like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbhid.quirks=0x0079:0x0006:0x00000400"

Detailed instructions for editing Ubuntu boot parameters here.

Thanks again - solving this seemed like such a longshot!

Paul

@mitu yes, you are right