neogeocd lr-neocd problem

KrinaSam

Previously i used the lr-fbneo-neocd emulator and cue discs and everything was fine. Want to save some disk space i decided to use lr-neocd and chd disc. I read this topic link text
put the bios in the correct directory, but the games don't start. I have a black screen and back to the emulationstation. Verbosse logging has this effect:

cat: /home/pi/.attract/romlists/.txt: No such file or directory
Parameters: 
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-neocd/libneocd_libretro.so --config /opt/retropie/configs/neogeocd/retroarch.cfg "/home/pi/RetroPie/roms/neogeocd/2020 Super Baseball (World).chd" --verbose --appendconfig /dev/shm/retroarch.cfg
[INFO] RetroArch 1.9.7 (Git 8373ac6)
[INFO] === Build =======================================
[INFO] Capabilities:  NEON VFPv3 VFPv4
[INFO] Built: Sep  8 2021
[INFO] Version: 1.9.7
[INFO] Git: 8373ac6
[INFO] =================================================
[INFO] [Input]: Found input driver: "x".
[ERROR] [Core]: Frontend is built for dynamic libretro cores, but path is not set. Cannot continue.
[ERROR] Fatal error received in: "init_libretro_symbols()"
[INFO] [Core]: Content ran for a total of: 00 hours, 00 minutes, 00 seconds.
[INFO] [Core]: Unloading core symbols..

My bios folder /home/pi/RetroPie/BIOS/neocd/
000-lo.lo, NEOCD.BIN, ng-lo.rom, uni-bioscd.rom

barbudreadmon

@krinasam said in neogeocd lr-neocd problem:

Fatal error received in: "init_libretro_symbols()"

Basically, it means the core isn't installed

KrinaSam

@barbudreadmon I was installing the core from retropie-setup.

root@retropie:/opt/retropie/libretrocores/lr-neocd# ls
LICENSE.md  neocd_libretro.so  README.md  retropie.pkg

Darksavior

@krinasam Did you alter your emulators.cfg? Look at what your setup is trying to execute: libneocd_libretro.so. It's supposed to be neocd_libretro.so

mitu

@krinasam said in neogeocd lr-neocd problem:

I was installing the core from retropie-setup.

You may be installing it from the current RetroPie-Setup script, but the runcommand is not the one installed by RetroPie-Setup

/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-neocd/libneocd_libretro.so

the above line, as @Darksavior hinted, is not installed by RetroPie-Setup.

Is this an official RetroPie image or a 3rd party image ?

KrinaSam

@darksavior said in neogeocd lr-neocd problem:

@krinasam Did you alter your emulators.cfg? Look at what your setup is trying to execute: libneocd_libretro.so. It's supposed to be neocd_libretro.so

@mitu said in neogeocd lr-neocd problem:

@krinasam said in neogeocd lr-neocd problem:

I was installing the core from retropie-setup.

You may be installing it from the current RetroPie-Setup script, but the runcommand is not the one installed by RetroPie-Setup
/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-neocd/libneocd_libretro.so 
the above line, as @Darksavior hinted, is not installed by RetroPie-Setup.

Is this an official RetroPie image or a 3rd party image ?

Thanks gentlemen. I have a bug in emulators.cfg. I haven't seen this before. I changed it to neocd_libretro.so and it works now. Installer creates lines in emulators.cfg but in neogeo directory, not in neogeocd directory. Thank you for your help.

mitu

@krinasam said in neogeocd lr-neocd problem:

Installer creates lines in emulators.cfg but in neogeo directory, not in neogeocd directory. Thank you for your help.

There's no neogeocd directory in RetroPie, are you using a 3rd party image ?

KrinaSam

@mitu Yes. it is a Wolfanoz 1TB img

sirhenrythe5th

@mods: could the name of the 3rd-party-image be deleted from the previous post?
There should be no indirect commercial for these &$§#*-in-da-house-images here.

dankcushions

@krinasam I'm sorry, but we don't support third party images: https://retropie.org.uk/forum/topic/3/read-this-first

please install official retropie via https://retropie.org.uk/docs/First-Installation/ before seeking support here.

@sirhenrythe5th IMO threads like this are a good demonstration of the risks of third party images ;)

sirhenrythe5th

@dankcushions ok, i see.
IMO it would be enough to exchange the title of this image to "a 3rd party-image".
Does it really matter if is called Wolfanoz of Foxymouse Mega-Image to realize that those %$#!-images can bring trouble?
Edit: i dont want to argue with you!!!! Its just that i hate these prebuilds :/