RPCS3 Forums

I've been reading the monthly blog posts for a while now, and there's something I thought of that would be a great improvement.

State the regressions. While newer builds may bring performance improvements to certain games, they may have negative effects on other games. For example, a build from last month ran Skate 3 at a minimum of 15 FPS. The latest build, however, runs Skate 3 at a maximum of 3 FPS.

This will not only show honesty (not hiding mistakes), but would also show users which games might not work as well as they used to.

Again, it's just an idea.

Problem is knowing the regressions.
If we know them beforehand, we fix them whenever possible before merging a pull request. Otherwise they're fixed afterwards as well.
If we know what made them regress, instead of writing about the regression we can fix the regression.

For example, no one has reported what pull request regressed Skate 3 performance, only a graphical regression.

Current reported regressions can be found at https://github.com/RPCS3/rpcs3/issues?q=...Regression