RetroAchievements: hash generation failed

Open
#856 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
54/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
backend

Research direction

Start by tracing how the core exposes ROM files to RetroAchievements, using the log’s “Could not open file” result as the failure point. Compare the current core’s ROM loading path with the older working version or Mupen64Plus-Next, and check whether the ZIP-contained ROM path is handled. Done means RetroAchievements can identify a ROM and load its achievements.

Written by the indexing model from the issue text.

Description

RetroAchievements does not seem to work in this core, because the ROMs cannot be hashed and identified. Loading any ROM gives a "hash generation" error, and achievements do not load.

ParaLLEl N64 is supposed to be a supported core for RetroAchievements: https://docs.retroachievements.org/general/emulator-support-and-issues.html#nintendo-64. The old version of the core (before the Parallel Launcher merge) used to work, and the Mupen64Plus-Next core does work.

Here is a log (it comes from macOS, but the same issue was confirmed on Android):

retroarch.log

The relevant portion:

[INFO] [RCHEEVOS] Identifying game: /Users/USER/ROMs/n64/Super Mario 64 (USA).zip#Super Mario 64 (USA).z64
[INFO] [RCHEEVOS] Found 1 potential consoles for z64 file extension
[INFO] [RCHEEVOS] Trying console 2
[INFO] [RCHEEVOS] Could not open file
[INFO] [RCHEEVOS] Load failed (-25): hash generation failed
[INFO] [RCHEEVOS] Game load failed: hash generation failed
Dominant language
C
Stars
414
Forks
155
Avg merge
1d 8h
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libretro/parallel-n64

All issues in libretro/parallel-n64

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.