@retropieuser555 hello! I am using the standalone (not the lr)

@mitu
Thank you!
I don't know why it was Glcore. I changed it to Gl as you suggested and the shaders are now enabled!
Thanks so much for the help!

@nharrer
Did you make any progress with this issue?

I'm facing exactly the same problem now.

@skyde72 please provide details of your setup as requested.

@deep_low_matte said in Remove Incomplete Instalation on Ubuntu:

I then deleted the folders in the home directory but the space was not reclaimed

Which folders did you delete ?

RetroPie installs everything under /opt/retropie, you can check its size and maybe delete it if you wish.

An update......some success.

It seems I had two problems:

The precompiled binary does not work form me on the pi400 I was using rom files from amiga forever and didn't realise they were encrypted

I will update if I get any more issues

G

@barbudreadmon Damn man, you are my hero. It works perfectly now, thanks.

@dankcushions Huh, I don't recall modifying any of those settings. I'll try a fresh install and see if that fixes things!

There don't seem to be any other references to fbturbo or Allwinner in the remaining configuration.

Then I don't understand from where the fbturbo configuration is referenced.

Can you check if the file still exists after you remove the xserver-xorg-video-fbturb package ? If so, remove it and see if - after rebooting - you still get the error.

@fnkngrv said in 8Bitdo SN30 Pro+ USING USB ADAPTERS - Multiple Controllers:

The controllers are showing in the system as Xbox-360 controllers.
....
I have attempted to use zerojay's controller ID script at least for the LR cores however it doesn't seem to help.

Which script are you referring to ? If it uses joystick names to re-order the joysticks, then having the same name might confuse the script and the order may not be correct.

@thorr69 Great find! Now i can use verbose logging.

[INFO] RetroArch 1.8.8 (Git 9552f87)
[INFO] Redirecting save file to "/home/pi/RetroPie/roms/neocd/Fatal Fury 2.srm".
[INFO] Redirecting save state to "/home/pi/RetroPie/roms/neocd/Fatal Fury 2.state".
[INFO] === Build =======================================
[INFO] Capabilities: NEON VFPv3 VFPv4
[INFO] Built: Nov 2 2020
[INFO] Version: 1.8.8
[INFO] Git: 9552f87
[INFO] =================================================
[INFO] Loading dynamic libretro core from: "/opt/retropie/libretrocores/lr-neocd/neocd_libretro.so"
[INFO] [Overrides] no core-specific overrides found at /home/pi/.config/retroarch/config/NeoCD/NeoCD.cfg.
[INFO] [Overrides] no content-dir-specific overrides found at /home/pi/.config/retroarch/config/NeoCD/neocd.cfg.
[INFO] [Overrides] no game-specific overrides found at /home/pi/.config/retroarch/config/NeoCD/Fatal Fury 2.cfg.
[INFO] [Remaps]: remap directory: /opt/retropie/configs/neogeo/
[INFO] Redirecting save file to "/home/pi/RetroPie/roms/neocd/Fatal Fury 2.srm".
[INFO] Redirecting save state to "/home/pi/RetroPie/roms/neocd/Fatal Fury 2.state".
[INFO] [Environ]: GET_LOG_INTERFACE.
[INFO] [Environ]: SYSTEM_DIRECTORY: "/home/pi/RetroPie/BIOS".
[INFO] Core requested VFS version >= v1, providing v3
[libretro INFO] Using front end provided VFS routines
[INFO] [Environ]: SET_VARIABLES.
[INFO] Content loading skipped. Implementation will load it on its own.
[INFO] [Environ]: SET_INPUT_DESCRIPTORS:
[INFO] [Environ]: SET_PIXEL_FORMAT: RGB565.
[libretro ERROR] Invalid CUE sheet: Index 0 is not allowed with pregap.
[libretro ERROR] Could not open CUE file: /home/pi/RetroPie/roms/neocd/Fatal Fury 2.cue
[ERROR] Failed to load content
[INFO] Content ran for a total of: 00 hours, 00 minutes, 00 seconds.
[INFO] Unloading game..
[INFO] Unloading core..
[libretro INFO] NeoCD deinitializing
[INFO] Unloading core symbols..
[INFO] [Core Options]: Saved core options file to "/opt/retropie/configs/all/retroarch-core-options.cfg"

My cue file is correct, i open it on FBNeo....any ideas?

EDIT: I´ve removed PREGAP 00:02:00 line from .cue and it works in neocd and fbneo.

Is this make any difference for neocd emulation?

@dynamight picodrive has always been the default megadrive emulator for pi 1/0. pi1/0 versions of retropie don't really have any emulators/software related to other pi models installed by default. that's why there's different image downloads.

emulators can increase in accuracy and requirements, but the ancient versions used for pi1/0 shouldn't.

@teethree89

2 old projects of mine, perhaps something to peek in :

https://github.com/FollyMaddy/retropieXstation

and

I always use this in the desktop environment, running games directly from the explorer :
https://github.com/FollyMaddy/RetroRun

@dankcushions Thanks a lot for the replies and for this last tip. I've learned a lot with this thread (core options are always saved if modified in-game, I should not mess with them xD, a way to revert them back to defaults...).
Br,
Dimas.

@xys7er

Not sure. the only way to know that is to plug in one side of your control panel at a time... or remove the LEDs from the buttons and see what happens. Plug them back in one at a time.

Did you check each switch for continuity? Maybe one of the micro switches is bad giving feedback to the Pi?

I don't know what power source you are using for the Pi as you didn't mention it, but usually 3.5 amp is the sold standards. That should be enough to drive the LED's as well.

@mitu I used Eatcher also for cloning, I wanted to try out all the possibilities.
source disk:primary.jpg

destination disk:destination disk.jpg

as you said partuuid are different . I changed partuuid into cmdline and fstab and it works. the drive starts up with no problem.
Thank you for your help!!! You are the master!!!

@deguzler said in NES Roms not loading:

[libretro WARN] Not an iNES file!
[libretro INFO] FCEU_MakeFName: /home/pi/RetroPie/BIOS/disksys.rom
[libretro WARN] FDS BIOS ROM image missing!
[libretro WARN] An error occurred while loading the file.

It doesn't detect your rom file as a nes file, so it thinks it might be a fds file, for which you are missing the bios (it's not a fds game anyway, 10 yard fight was not released on fds). Your rom is probably corrupt, but if you are confident it's not then you can always try it with another nes emulator (nestopia or mesen are probably way better choices on a pi4 anyway since they are more accurate and pi4 should be able to handle them).

@a1eg said in Joystick not working for Commodore emulator VICE in some games:

@pscotto1234 THANK YOU
That did the trick!

You saved me perhaps a weeks time. I would have been playing around with this, reinstalling the RetroPie image, starting from scratch, trying this that and everything. Then maybe if I was lucky I would have come up with the answer.

Thank you for saving my time and giving me the answer!
I wonder why some games are for Joystick 1 and some for Joystick 2.

I found a lot of help in this forum. I'm very happy when I can help someone else ;)
Enjoy!