@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!

@mitu ah perfect that worked too, thank you very much!

@mitu Thx. Never thought of that. Exiting one will just start the other and each will shutdown/save properly. Nice :)

Upgrading the OS is not supported by Raspbian nor RetroPie. You probably have found some instructions on how to upgrade using apt and updating its configuration files in /etc/apt, but it's not a recommended process, especially for a beginner.

If you wish to use an up-to-date/current version, use the image from http://retropie.org.uk/download. We don't support 3rd party image, as outlined in https://retropie.org.uk/forum/topic/3/read-this-first.

@sleve_mcdichael thanks for the report, it should be ok now :)

Got it, someone from the official ppsspp-forum had the final hint.
I share this here for everyone running in the same issue (which should happen if you updated recently):

"RE: graphical issues since last update
Turn off the vertex cache setting.

It used to be accidentally disabled in code, but we re-enabled it recently. It seems to be malfunctioning on some devices now, though. It was accidentally broken for several stable versions."

@binarymessiah said in Low volume on videos with OMX+PCM:

Yeah not using OMX leaves me with no sound in the video snaps

That means the vlc built-in video player doesn't have the right audio settings. I remember now a while back a similar topic with the audio output from the Picade, the issue was that the I2S card doesn't have a volume control exposed to ALSA, so the volume slider has little effect.

Does alsamixer show any volume control for your card ? I assume that the configuration for the Picade has disabled the on-board audio, otherwise in-game sound wouldn't have worked.

@lister-of-smeg said in Buggy settings menu:

"I really dont have time to read that all, sorry."

I'll also add https://retropie.org.uk/forum/topic/29316/how-can-you-play-with-this-input-lag to his best-of.

@jimmyfromthebay

There is nothing wrong with the lr-atari800 build Did you put the right BIOS roms where they need to be? Are you running good ROMs. Make sure to check what's in the ROM files and not that they are double zipped...some downloads have that issue

Also..did you follow this?

once you have the correct BIOS files in place and the emulator(s) working. I highly suggest taking some time to go through this build setup for lr-atari800/5200.

Without it, your systems will work, but look nothing like they should, especially the a800 side.

https://retropie.org.uk/forum/topic/22392/lr-atari800-5200-artifacting-basic-and-other-guidance

@mitu said in problem with error log /dev/tty1: Permission denied:

@kounabi22 said in problem with error log /dev/tty1: Permission denied:

i fix it by change the theme to carbon.

That's just a workaround, you probably have too little memory allocated to the GPU - either in config.txt or in EmulationStation (or both).

As for the audio settings, you should probably have change:

Audio card should be set to 'Default' Audio device should be set to 'HDMI' OMX Player Audio device should be fine as it is, or you can set it to Alsa.

i try audio card default but i get no sound with audio device "hdmi" only "master" option works.
omx player alsa is fine.