@Arrafart Those are great controllers by the way. I have the old set (US and Japanese) with the corresponding color patterns on the buttons, before Nintendo forced 8-bitdo to change them :-(. I actually set RetroPie up with them easily. I wanted to try the Xbox 360 controller out. I also use the WiiU Pro Controllers as well.

@mitu said in retropie with raspberry pi5 + vga666 for crt tv:

RetroPie support for the Pi5 is still pending, so some things might not work.

but if i launch retropie i get a black screen

There's no 'retropie' application, what exactly are you launching ? Are you using the RaspiOS Lite and starting EmulationStation from the command line ?

yes i launch EmulationStation

@mitu
I ended up having to do a full re-install of Mint Mate 22 for other reasons. This is my third install in the past 2 weeks and I hope I do not need to do so again.

Let it be known that even after a fresh full-reinstall of Mint Mate 22, the same lack of joypad recognition continues. I have to access the setup through terminal via the sudo command in order to make it work. Otherwise, accessing the setup through the Retropie OS itself does not enable joypad function in Mint Mate 22. I did not have this issue with Mint Mate 20.

@mitu said in Error updating to the latest version of Retroarch:

You can delete the cores folder and it the .info files will be re-downloaded on future updates.

Awesome. Thank you!

@jds140 said in Switching USB flash drives.:

Or even copy the file structure from one drive to the other?

Yes, that should work. The USBmount script just looks for the directory name retropie-mount and mounts it if it's found.

@mitu Yes retropie-extras. Ok i will.

I'm not aware of any issues with 22.04. There may have been, at the time it was launched, 2 years ago, but there shouldn't be today. Again, 18.04 is not supported upstream and support for it from various emulators is dwindling.

@mitu
Fixed, using MC I could see everything, just my folder structures were wrong and so nothing was showing up, quick rearrangement and it's all good.

Thank you for your help.

@frankeanu said in No prompt to set up my controller:

@Addison Sorry, I just wanted to provide the info of what I was using. There was no personal reference link; it was the URL copied directly from the Amazon product listing. It's now removed.

A correct Amazon link would appear as something like this.

https://www.amazon.com/dp/XXXXXXXXXX/

Yours had extra which meant a referral was also included.

It's okay though.

Just be a little more careful.

It's easy to get suddenly banned here. :P

@BuZz Hi, thanks for this hint :-) . I did not know that. So it is much better :-) By the way, the modified script is far from perfect. I have only tested so. For the final version is still missing a recognition. But unfortunately I have no idea how to integrate this reasonably. ( function get_platform() )

Greetings

I had the same idea, I am trying to run RetroPie on my Raspberry Pi with Debian 11 (I can't install RetroPie on Bullseye) on a Docker container, and I am using my iPad as a screen through Remote Desktop, and a Bluetooth controller (8Bitdo Zero 2), and I can use Emulationstation (my gamepad works fine there) but when I launch any game my controller doesn't work (I don't have a wired controller so I don't know if that's the problem). I've tried to change the retroarch controller configuration and changing it to "sdl2" only works one button... I don't know why. If you don't have any issues maybe I could try your Dockerfile because it might be my setup?

@Ashpool said in rgui - load/save state option missing:

May I ask(/wonder) why update_packages_gui_setup() calls updatescript_setup(), but basic_install_setup() ain't doing that?

Not sure I fully understand.
Basic setup is meant for a new installation, which assumes you are doing a manual installation. This means you just cloned the RetroPie repository, so there's no need to update again the script.

@Darksavior AWESOME DUDe thankyou

Pushing needs an remote repository.

pi@retropie:~/RetroPie-Setup $ git remote -v # output cmitu git@github.com:cmitu/RetroPie-Setup.git (fetch) cmitu git@github.com:cmitu/RetroPie-Setup.git (push) origin https://github.com/retropie/RetroPie-Setup (fetch) origin https://github.com/retropie/RetroPie-Setup (push)

If you haven't added your own repository as a remote, add it first (make sure you set-up SSH keys authentication for the repository, Github doesn't allow pushing over HTTPS anymore with user/pass). Then, when you create a branch and want to push it to your repository, just

git push --set-upstream mine test

where mine is the name of your fork's remote repository.

pi@retropie:~/RetroPie-Setup $ git push --set-upstream cmitu amiberry-5.2 Enumerating objects: 45, done. Counting objects: 100% (43/43), done. Delta compression using up to 4 threads Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 871 bytes | 37.00 KiB/s, done. Total 5 (delta 4), reused 0 (delta 0), pack-reused 0 remote: Resolving deltas: 100% (4/4), completed with 4 local objects. remote: remote: Create a pull request for 'amiberry-5.2' on GitHub by visiting: remote: https://github.com/cmitu/RetroPie-Setup/pull/new/amiberry-5.2 remote: To github.com:cmitu/RetroPie-Setup.git * [new branch] amiberry-5.2 -> amiberry-5.2 Branch 'amiberry-5.2' set up to track remote branch 'amiberry-5.2' from 'cmitu'.

@BuZz
Yes it is.
Thank you very much.

@genge094 said in keep getting stuck on one part of running retropie set-up script on raspbian:

@sleve_mcdichael thanks! I was able to get it to download on the full desktop OS but it boots into a black screen. I guess I would have to start a new topic for that one though.

Can you describe what you exactly did ?

@sirhenrythe5th Yes. I even used the official Raspberry Pi program. I think I figured out the problem though. Thanks for the reply!

Hi,
What internal resolution for flycast are you running? I'm using 800x600 and output at 1080p, core resolution (no integer scaling) have no issues running dreamcast games at all, apart from WINCE (windows CE) games as I'm using the recently reverted flycast core, these are not currently supported. Check you are using alsathread for audio and turn of shaders, as most shaders are too demanding (I do use 2x presale bilinear/zfast on all games without issue). Oh and check you are using recent BIOS files as well.

Here's parts of my config:

reicast_alpha_sorting = "per-triangle (normal)"
reicast_anisotropic_filtering = "4"
reicast_boot_to_bios = "disabled"
reicast_broadcast = "Default"
reicast_cable_type = "TV (Composite)"
reicast_custom_textures = "disabled"
reicast_delay_frame_swapping = "disabled"
reicast_div_matching = "auto"
reicast_dump_textures = "disabled"
reicast_enable_dsp = "enabled"
reicast_enable_naomi_15khz_dipswitch = "disabled"
reicast_enable_rttb = "disabled"
reicast_fog = "enabled"
reicast_force_wince = "disabled"
reicast_frame_skipping = "disabled"
reicast_framerate = "fullspeed"
reicast_gdrom_fast_loading = "disabled"
reicast_hle_bios = "disabled"
reicast_internal_resolution = "800x600"
reicast_language = "Default"
reicast_mipmapping = "enabled"
reicast_pvr2_filtering = "disabled"
reicast_region = "Default"
reicast_render_to_texture_upscaling = "1x"
reicast_synchronous_rendering = "enabled"
reicast_system = "auto"
reicast_texupscale = "disabled"
reicast_texupscale_max_filtered_texture_size = "256"
reicast_threaded_rendering = "enabled"