NEO-GEO CD for Dummies

Nakynaw

@zerojay said in NEO-GEO CD for Dummies:

@Darksavior Mine are all CHD as well. lr-neocd seems to fail to recognize my BIOS files even with proper matching SHA-1's.

I found what was the cause of the same problem for me, i'll share with you in case it helps : my games were working very well with the NeoGeo Bios in the folder "fbneo" while the games were in CUE with SUB IMG and CCD.

When I compressed the game files in CHD, I also had the segmentation fault.

So I did exactly as @Darksavior : the BIOS files (000_lo.lo and neocd.bin) in a "neocd" folder that I created in the bios, and not in the "fbneo". Now, using the lr-neocd emulator it works well!

THX guys and good luck to the others.

Clyde

Just for the sake of completeness:

@Nakynaw said in NEO-GEO CD for Dummies:

Indeed, it returned "0" for an answer. But I do not get it. I do have ".cue" in neogeo rom folder...

No, you had them in subdirectories of the neogeo rom directory. My command line only works with files in the current directory. It could be expanded to "walk" through any subdirs, but since you fixed it another way by now, no need for that.

I tried this :

pi@retropie:~ $ chdman created -i "Metal Slug 2 (Wld).cue" -o "Metal Slug 2.chd"

But it said "command not found" and I had just installed mame-tools and rebooted.

It's createcd, not created. 🧐

I know, I am so far from knowledgeable in the Pi district. :/

Nobody was born with this knowledge. We all learn on the way.

zerojay

@Nakynaw said in NEO-GEO CD for Dummies:

@zerojay said in NEO-GEO CD for Dummies:

@Darksavior Mine are all CHD as well. lr-neocd seems to fail to recognize my BIOS files even with proper matching SHA-1's.

I found what was the cause of the same problem for me, i'll share with you in case it helps : my games were working very well with the NeoGeo Bios in the folder "fbneo" while the games were in CUE with SUB IMG and CCD.

When I compressed the game files in CHD, I also had the segmentation fault.

So I did exactly as @Darksavior : the BIOS files (000_lo.lo and neocd.bin) in a "neocd" folder that I created in the bios, and not in the "fbneo". Now, using the lr-neocd emulator it works well!

THX guys and good luck to the others.

Still no luck for me. I had those files already in a neocd folder in my bios directory along with some more, so I deleted the extras and tried again, but no luck. lr-neocd still says it cannot find the BIOS files (and it appears to be checking in BIOSDIR/neogeo which has them already) and the two fbneo emulators both segfault after the bios starts up.

Darksavior

@zerojay If you're positive it's not seeing the bios, and you've double checked the hashes, then you can try this:
Uninstall and then reinstall lr-neocd from source and open the rgui to check: "Settings","Directory","System/BIOS" and make sure it points to /home/pi/RetroPie/BIOS

zerojay

I ended up using the lr-mess core for this instead. Seems to be working well.

Crush

I found that your naming conventions are not in line with the other systems, also it wont be picked up by most themes because of this.
My es_systems entry is as follows:

 <system>
    <name>neogeocd</name>
    <fullname>Neo Geo CD</fullname>
    <path>/home/pi/RetroPie/roms/neogeocd</path>
    <extension>.cue .CUE .chd .CHD</extension>
    <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ neogeocd %ROM%</command>
    <platform>neogeocd</platform>
    <theme>neogeocd</theme>
  </system>

Hope this helps someone.

shavecat

Hey im trying to run it .with
lr-neocd
but its just going back to ES
any ideas ?

Darksavior

@shavecat Enable verbose logging and post the log.

shavecat

@Darksavior
runcommand.info


neocdz
lr-neocd
/media/usb0/roms/neogeocd/Metal Slug 2 (World).chd
/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/$

runcommand.log


Hello logfile - runcommand-onstart checking in here
Hello logfile - runcommand-onstart checking in here
Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/lib$
Hello logfile - runcommand-onend checking in here
Hello logfile - runcommand-onend checking in here

Darksavior

@shavecat You need to post the contents of runcommand.log with verbose logging enabled.

shavecat

@Darksavior
how do i do that ?

Darksavior

@shavecat https://retropie.org.uk/docs/Runcommand/

shavecat

@Darksavior
That is what i wrote already -0
"/dev/shm/runcommand.log"

Hello logfile - runcommand-onstart checking in here
Hello logfile - runcommand-onstart checking in here
Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/lib$
Hello logfile - runcommand-onend checking in here
Hello logfile - runcommand-onend checking in here

mitu

@shavecat said in NEO-GEO CD for Dummies:

That is what i wrote already -0

That's not a Verbose log. Enable verbose logging and then look into the log to see the error. Post it on pastebin.com.

shavecat

@mitu
"When launching Libretro cores (those prefixed by lr-) the Runcommand launch menu presents the option to Launch with verbose logging. This outputs more information to the log file found in /dev/shm/runcommand.log which is useful, and often necessary, when diagnosing problems. Once the game is exited, the log file can be downloaded via SFTP or viewed directly via the command line.

"
What im doing worng ???

I did got it runging with the fbeno-neocd
but its getting to the disc loding screen and quit
https://pastebin.com/URSMK3sW

mitu

@shavecat said in NEO-GEO CD for Dummies:

https://pastebin.com/URSMK3sW

Again, this is not a verbose log.

shavecat

@mitu
Hey again
so how do i do that ?
there is no explain ...

mitu

@shavecat said in NEO-GEO CD for Dummies:

so how do i do that ?

I think it's described pretty well in the docs - in the link posted by me or other posters. Just start the game by choosing the 'Launch with verbose logging' from the runcommand launch menu.

shavecat

@mitu
thanks u
for some reason didnt notice it
so im using the lr-neocd
and its loading but i just getting a black screen
https://pastebin.com/V64i6q1n

mitu

Either a bad .chd file or missing BIOS files - which should match what's described in https://github.com/libretro/neocd_libretro. Your SYSTEM folder is borked though, instead of pointing to the BIOS folder as it's configured in RetroPie, it points to the ROMs folder - you probably reset the RetroArch's configuration file or messed up the configuration when you created a separate system for NeoGeto CD.