libretro / libretro/RetroArch

[Feature request] Improvement to gpu-screenshot or otherwise

Open
#10,537 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

So (at least at current) I dont use screenshots in the literal sense. I do use the screenshot of save state feature though.

I have kept gpu screenshot off for a few reasons.

  1. the screenshots look better to me as they dont include a picture of the notification popping up saying your saving a state and they dont capture corners of your overlay here or there

  2. they capture the original resolution which i find helpful as a quick reference to a machines reso 😛

  3. theyre substantially lighter weight of course

my issue is that it seems cores like beetle psx and dolphin are capturing the giant shaded overlaid 4k resolution state images regardless of the SS setting. Those are just the ones ive come across thus far. I presume it has something to do with them being hardware cores.

The feature request is for a means to circumvent the forced full resolution capture of hardware cores and/or to be able to disable the “non-game” stuff from appearing in a capture when gpu screenshot is enabled (less desirable to me relative to the first request but a good option to have, ive seen several requests about getting at least the notifications out of the captured images) I imagine the saving state notification can be coaxed out of the image by speeding up the point at which the SS is taken (or delaying it, but it would have to be substantially delayed for cores like dolphin that take a few seconds to complete the save state)

GPU screenshot ideally should function as a global toggle one way or the other. (if thats even possible, dont know without asking i suppose)

(same with gpu recording tbh, but something tells me thats a bigger fish)

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

Start by reproducing save-state screenshots with the gpu screenshot setting using Beetle PSX and Dolphin, comparing captures with and without the setting. Review how screenshot timing, resolution, notifications, and overlay content differ; done means the requested global behavior or a clearly scoped alternative is implemented and verified for these cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-graphics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.