Open MattHorn25 opened 6 days ago
I'll let answer @Novum that question because that is likely how it is designed.
Now, what is the point applying antialiasing on pixels when you intentionnally want to see big pixels using r_scale
?
I would suggest that bigger pixels need more antialiasing than smaller pixels to convey a similar amount of information - the smaller the pixels, the less AA is needed. That may be a matter of preference of course.
But this report is more about the fact that antialiasing should apply if enabled - there's nothing about the Scale setting that would suggest to a new user that it will interfere with antialiasing. Users who want big aliased pixels would intuitively select a high Scale and low/disabled AA to achieve this.
When enabled (ie when set to other than 1x) the Scale option in Graphics introduces aliasing regardless of what the AA setting is. However the amount of aliasing differs slightly depending on the AA setting. The Scale option seems to behave as though it's displaying every other, or every fourth etc pixel from the 'full' unscaled image, with that 'full' image being antialiased according to the AA setting - and the remaining pixels are discarded. Intuitively the user would expect that the AA setting applies to the Scaled pixels, not the raw source pixels.
To reproduce, select any high AA setting and any chunky Scale setting in the Graphics options and the aliasing should be very visible on any/all content.