libretro / libretro/RetroArch

Achievement Screenshot does not include the badge

Open
#11,364 11 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cheevos feature request
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

I was wondering if we could make the screenshot of the achievement at the same time that the badge appears in order to use as evidence for manual unlocks when the Server is down.

The feature in this way would be much more useful, and perhaps it could include some other information to help the people judging the veracity of the screenshot if the screenshot belongs to a certain user like the Username, framerate or something of those sorts.

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

Today I played and activated the feature during downtime in order to ensure an easy screenshot of the cheevo, and it turned out that all the pictures do not include the badge and therefore are useless to show that I clear which cheevo.

Expected behavior

To have a screenshot of each achievement with the badge in order to submit as evidence.

Actual behavior

A screenshot is taken just before the badge triggers defeating the evidence purpose.

Steps to reproduce the bug
  1. Activate the Screenshot when unlocking an achievement feature
  2. Get an Achievement
Bisect Results
Version/Commit

You can find this information under Information/System Information

  • RetroArch: [version/commit]
Environment information
  • OS: Android, but all the systems have the same result according to mates in Discord
  • Compiler: [In case you are running local builds]

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no source file, test, or entry point. Start by tracing the achievement-unlock screenshot flow described in the reproduction steps, then verify that the captured image includes the achievement badge and sufficient identifying information to serve as evidence.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.