Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Log/Build history of auto-updates done within RPCS3 #8484

Closed
I-Knight-I opened this issue Jun 23, 2020 · 1 comment · Fixed by #10972
Closed

[Feature Request] Log/Build history of auto-updates done within RPCS3 #8484

I-Knight-I opened this issue Jun 23, 2020 · 1 comment · Fixed by #10972
Assignees
Labels

Comments

@I-Knight-I
Copy link

Quick summary

A log or history containing the updates that have been applied from within the program itself. For each entry, a "from version" and "to version" too.

Details

When testing a regression, I came across an issue whereby I didn't have the exact builds I had been recently using to play games as I'd been updating from within the GUI. Typically, I'd download the .zip file and put it into a folder called "Version History" and just never really appreciated its usefulness until now.

Therefore, a simple log file that notes down updates would be seriously appreciated and could even help with future bug and regression reports.

1. Please describe, what part of RPCS3 would be affected by your feature:

  • UI

2. Please tell us, why your feature is important to RPCS3.

Please read above. It'll help with regression and bug testing. From both a helper point of view as well as an ordinary user submitting reports, the information could be vital.

3. Please attach screenshots of the feature implemented in other projects.

Best I can find right now that's similar is something like what Windows has.

4. Please provide your system configuration:

  • Windows 10 Home 1909
  • i9-9900K @ 5.0Ghz
  • MSI GTX 980Ti 6G Gaming
  • v446.14
@fefo-dev
Copy link

fefo-dev commented Mar 9, 2021

Seconding this request. A update-history.log would make debugging regressions much easier for infrequent updaters like myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants