01-12-2018, 10:57 PM -
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
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
Desktop: Ryzen 7 5800X, Radeon RX 6800 XT, 2x8G DDR4 3600MHz, Manjaro Linux
Laptop: Ryzen 9 5900HX, Radeon RX 6700M, 2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350, Radeon R9 280X, 2x4G DDR3 1600MHz, Manjaro Linux
Laptop: Ryzen 9 5900HX, Radeon RX 6700M, 2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350, Radeon R9 280X, 2x4G DDR3 1600MHz, Manjaro Linux