goody_fyre11Suggestion for Monthly Blog Posts
Started by goody_fyre11

1 posts in this topic

29 posts 18 threads Joined: Sep 2017
01-11-2018, 03:55 AM -
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.

3,706 posts 96 threads Joined: Aug 2017
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
    Desktop: Ryzen 7 2700X,   Radeon RX 6800 XT, 2x8G DDR4 3200MHz, Manjaro Linux
     Laptop: Intel i7 6700HQ, Intel HD 530,      2x8G DDR4 2133MHz, Manjaro Linux
Old Desktop: AMD FX-8350,     Radeon R9 280X,    2x4G DDR3 1600MHz, Windows 7

Forum Jump:

Users browsing this thread: 1 Guest(s)