I think preferring a lower-than-native resolution over DLSS as a blanket statement is a bit of a wild take, but there can definitely be problems like artifacts, especially in certain games. I’m playing RDR2 at the moment and the TAA (which is forced to High with DLSS) is poorly implemented and causes flickers which is definitely annoying, as an example. I played Alan Wake 2 on an older laptop that barely ran it and I definitely noticed artifacting from DLSS there, though in fairness I was demanding a lot from that machine by forcing it to play AW2.
Frame time will of course be impacted so if you’re playing something really fast and twitchy you should stay away from DLSS probably. It’s also less bad if you don’t enable Frame Generation. Finally, both DLSS and Frame Generation input lag seems to scale with your baseline FPS. Using it to try to reach 60+ FPS will usually mean some input lag, using it when you’re already at ~60 FPS to get 80-100 or whatever means less noticeable input lag.
I think preferring a lower-than-native resolution over DLSS as a blanket statement is a bit of a wild take, but there can definitely be problems like artifacts, especially in certain games. I’m playing RDR2 at the moment and the TAA (which is forced to High with DLSS) is poorly implemented and causes flickers which is definitely annoying, as an example. I played Alan Wake 2 on an older laptop that barely ran it and I definitely noticed artifacting from DLSS there, though in fairness I was demanding a lot from that machine by forcing it to play AW2.
Frame time will of course be impacted so if you’re playing something really fast and twitchy you should stay away from DLSS probably. It’s also less bad if you don’t enable Frame Generation. Finally, both DLSS and Frame Generation input lag seems to scale with your baseline FPS. Using it to try to reach 60+ FPS will usually mean some input lag, using it when you’re already at ~60 FPS to get 80-100 or whatever means less noticeable input lag.