Some games load, some don't (NES/FCEUmm Core)

hansolo77 · 17 Nov 2016, 01:20

Yes, I suppose I can.. It will take me a while, I just got home from work. :) Need to finish checking the rest of my email.

Darksavior · 17 Nov 2016, 01:25

@hansolo77 Spy vs spy and smb1 work fine for me. They are from the no-intro romset if it matters. Uninstall fceumm, reinstall, and see if that fixes anything.

hansolo77 · 17 Nov 2016, 01:37

Yeah I'm using a fresh No-Intro romset as well [2016-09-06]. It's possible my process of adding the ROMs to my storage drive did something to them. I ran them through clrmamepro with a Parent-Clone dat to make a clean set of 1-Game/1-Rom. Since some NES games require headers to play, running it through clrmamepro might have killed their headers.

@Darksavior can you confirm your hashes for those 2 games? Mine are:

Super Mario Brothers (World).zip
CRC32 - 54AB90D6
MD5 - E1969132CD9B11EAB2799F71FFD85B2D
SHA-1 - 675279585F004781277A49ED66E9F29271588F86

Spy vs Spy (USA).zip
CRC32 - 19A4894C
MD5 - 84F3EEF059083A3FB548648A536BEB8B
SHA-1 - CB207E661FF4785FED6BC6F343541AD02F3E9387

I use this tool (right click a file, go to properties, and it gives you the hashes on a new tab called "File Hashes") to generate hashes easily. It's free!

Darksavior · 17 Nov 2016, 02:48

@hansolo77
Nothing matches. You...ran nes roms in clrmamepro? I've never, in the near 20yrs of playing roms, ever needed console roms to be fixed. The no-intro set is fine as is.

hansolo77 · 17 Nov 2016, 03:11

These weren't fixed... I just didn't want to have multiple copies of the same game. So I used clrmamepro to filter out and rebuild a new set (move files from one folder to the other) that didn't need duplicated. I just remember that when I did that, it reported an error before I could do it, saying that I needed a header file to make it work, and the comment by @dankcushions said about headers made me think of it. I'm too tired to mess with this tonight, so I'll follow up tomorrow. All I know is, it works fine in QuickNES, and used to work in FCEUmm before we started figuring out what wasn't working with RetroAchievements.

Thanks for checking the hashes though. Maybe something did change, unless you're not using the same romset [2016-09-06].

bmn001 · 17 Nov 2016, 06:08

I'm having this exact problem with a different rom. My error occurs in the same spot: Line 925 of runcommand.sh.

This exact rom worked fine with 4.0.1. I just happened to try now that my system is at 4.1.1 and it's a no go.

In both cases, the version of lr-fceumm I'm using is the same: 1.3.6.

Here's more info from my side:

Pi Model: Pi 3 Model B
RetroPie Version Used: 4.1.1
Built From: Pre made SD image on RetroPie website at 4.0.1, then eventually upgraded using setup script to 4.1.1
USB Devices connected: none
Controller used: 8Bitdo NES 30 Pro
Error messages received: (see log)
Log found in /dev/shm/runcommand.log (if relevant): http://pastebin.com/JghBCrAx
Guide used: none
File: /home/pi/RetroPie/roms/nes/10-Yard Fight (USA, Europe).zip
Emulator: lr-fceumm 1.3.6
Attachment of config files: not sure which configs you need, but happy to provide them

bmn001 · 20 Nov 2016, 21:58

Well here's something interesting. When I unzip the rom it works fine. It's only when it's zipped that I get the "aborted / line 925" error.

@hansolo77 Try unzipping the rom and see if it works for you.

hansolo77 · 20 Nov 2016, 22:07

Interesting find. I will definitely give that a try if I continue to have problems. I'm actually trying to figure out what's wrong with my controller setup right now, so this nagging bit of issue has been sort of "put on the back burner" so to speak.

flop · 20 Nov 2016, 22:45

Well... I don´t know if spy vs spy is a famicom rom, but I suggest to you to get that disksys.rom BIOS too in addition to unzip the files

bmn001 · 21 Nov 2016, 22:22

Tried compiling lr-fceumm from source, ended up with the same version (1.3.6) and it unsurprisingly still did not work.

Does anyone have any ideas of why we might be seeing this behavior?

Based on our logs posted here it looks like runcommand is the culprit, but I'm not 100% sure.

BuZz · 21 Nov 2016, 22:24

@bmn001 I doubt it is the fault of runcommand. If you unzip /home/pi/RetroPie/roms/nes/10-Yard Fight (USA, Europe).zip and from a commandline type file /home/pi/RetroPie/roms/nes/unpacked file name what do you get ?

The no-intro nes rom set doesn't have headers does it ? Headerless nes roms will not work.

hansolo77 · 21 Nov 2016, 23:42

I just thought I'd post an update. I didn't do anything, but now SMB1 works. I mean, I started from scratch with a brand new SD image of RetroPie, updated the kernel (for my raphnet adapter), updated from source RetroArch and lr-fceumm. I'm still troubleshooting my controller issue, but just for a test I went ahead and tried to load SMB1, and it loaded up fine. The ROM is still zipped, and I'm using a No-Intro set. I also have the ROMs stored on a permanently attached hard drive. Those files have not changed in the switchover to a new install. So I think what caused the original issue must have been something we ALL had done at one point. I wonder if this was a problem with maybe RetroArch, that was fixed since the last time it was updated? I have the latest source installed from yesterday (although they update the GIT all the time, with multiple pushes throughout the day). So maybe something is fixed? If not RetroArch, maybe the updated source to FCEUmm had a fix? All I know is that I didn't do anything to the ROM drive or the files, they're all still zipped and it worked.

bmn001 · 22 Nov 2016, 18:01

@BuZz Well keep in mind this same zipped rom worked with 4.0.1 with the same version of lr-fceumm.

I've unzipped the ROM, and the file command gives me this:

10-Yard Fight (USA, Europe).nes: iNES ROM dump, 2x16k PRG, 1x8k CHR, [Horiz.]

BuZz · 22 Nov 2016, 18:10

@bmn001 that should work at least. Maybe try updated retroarch and lr-fceumm (from binary first - i use the last retroarch/lr-fceumm binaries on my system and I have not noticed any issues with nes).

bmn001 · 22 Nov 2016, 19:48

Just tried updating both of those. First from binary, then from source. Same behavior in every scenario.
To rule out SD corruption or other file systemweirdness I'm in the process of downloading the latest SD image and will give that a go.

bmn001 · 22 Nov 2016, 21:50

Well it's definitely not SD corruption.

I downloaded 4.1 and put it on the SD. Rom worked. Updated w/setup script to 4.1.3, and...the rom still worked!

So then I tried putting backup image of 4.0.1 that I'd saved from a few months ago on the SD. The rom worked. I then updated w/setup script to 4.1.3. Rom did NOT work.

So somewhere in the update process from 4.0.1 to 4.1.3 , something breaks. I have no idea what or how to track it down, but if worse comes to worse I guess I could always just start over from scratch with 4.1.

hansolo77 · 22 Nov 2016, 22:46

Good find. I don't know what version I'm using. But as I said, using the latest SD image on the site, and updating RetroArch and the Core from source seemed to keep my system running those "bad" roms. Maybe it IS something to do with the 4.1.3 update. Was there something else going on that might have broke, like RunCommand, or EmulationStation?

bmn001 · 23 Nov 2016, 17:53

Well I gave up on trying to make this work. In the end, the only thing I could do was install the latest image (4.1) upgrade to 4.1.3 using the setup script, and reinstall roms, re-scrape data, re-config raspi system settings, re-add controllers...basically completely start over.

I've got things working now, but it was a ton of work and I'll have to think long and hard about ever upgrading RetroPie again.

bmn001 · 24 Nov 2016, 16:25

Ok, after getting everything set up all over again, the problem has returned. I'm pulling my hair out in frustration and I'm more determined than ever to find the cause.

This affects several roms on my system, and the problem only shows up when the roms are zipped.

The verbose logs continue to show the runcommand "line 925/aborted" error.

If I launch into the emulator with a working zipped rom, I'm then able to load a non-working zipped rom inside of the libretro GUI, and it works there! It's only when attempting to launch from emulationstation that I have problems.

Could this libretro bug be to blame? https://github.com/libretro/RetroArch/issues/3783
How can I check if "cache_directory" is set to a valid dir?

BuZz · 24 Nov 2016, 16:27

check your configs/all/retroarch.cfg - note that runcommand creates the /tmp/retroarch directory when it launches and removes it afterwards.