@windg

yes it work ty.

@retropieuser555 I got some errors running cmake. It's fine. I'll use cmitu's incomplete script.

@kounabi22 I'm not sure if this refers to all binaries or just the one referenced in the topic, but @BuZz said in lr-mame binary not updating?:

(...) I have also paused building binaries currently and will resume soon.

I don't know what the "regular" binary update schedule is like or anything but I see on the emulationstation-dev package (from the master branch) which receives regular updates on GitHub, the latest binary is from 21 Jul 2023, over a month ago. I feel like in the past these have been updated within days of the code change, but maybe that's not always the case? Or maybe they really did mean all binaries had paused, and "will resume soon" hasn't happened yet.

@JRay999

You're quite welcome! :D

@Dipkid ok, it worked I opened the controllers and realized that many buttons weren't on the same slots and one of my joysticks was upside down. Thanks for your help.

@sirhenrythe5th I think the objective is to track in real-time the 'insert coin' on some machine so as to, my wild guess, charge the usage of the games. The problem is that you need to capture the select button only when you're running the emulator, and when it actually equates to an insert coin event. It's an interesting and not so easy to solve problem (apart from modifying the emulators to do this tracking somehow)

@mitu said in about lr-flycast with new core:

@kounabi22 Sadly no, I've been testing various variants/versions so that it would work on both Pi3 and Pi4 but due to the lack of free time, I haven't found a solution. I'll have some more free time this summer, so I want to get back to updating the module and adding the standalone flycast instead of reicast.

Any luck to make it work on both pi?

Then it means the retroarch.cfg was not a problem, but can't think of a reason why running it from EmulationStation has this problem.

Running RetroPie from the desktop is not a supported configuration on the Pi. Use raspi-config from a terminal and configure your system to auto-boot to console as the pi user - https://www.raspberrypi.org/documentation/configuration/raspi-config.md

I change the settings see if you can download it now guys.

Sorry took so long but thanks it worked amazing you are the best.

I don't think the N64 emulator mapping are switched (each controller should have its own mapping), but rather that the most recent configured controller takes the place of P1 or they're just arranged alphabetically.

You can check this in the mupen64plus.cfg file and see the order in which they appear and their device index.

@aatheronb I'm assuming that you're talking about EmulationStation, RetroPie's frontend? If so, see this thread.

Video here

See this topic for an explanation. Because of the update, the auto-login doesn't work. So you just have to explicitly login and then type sudo raspi-config to configure auto-login again. Reboot after the configuration and your RetroPie should start again Emulationstation on boot.

I have this problem when I start the basic installation of RetroPie-setup 4.4.1 It will have to install glideN64 myself it's good?

I have some problems with English, so it's pretty complicated when I do google searches. thank you.

@sam Setting up RetroPie on a real RPi is easy if you follow the instructions (which you've presumably already looked at when you installed on Ubuntu), and the forums are full of extremely useful information (sometimes better than the documentation :P)

Have realistic expectations tho; while the vast majority of platforms are emulated pretty much flawlessly and PS1 emulation is mostly very good if you overclock your Pi a bit, N64 and Dreamcast are really at the very limit of what can be achieved on the Pi3.

If you're cool with that, and maybe asking a question or two here if/when you get stuck, then in my opinion there's no reason not to get an RPi3.

thanks, currently reinstalling
first time i have installed this so panniced a bit thought id done something wrong haha