Steve started GamersNexus back when it was just a cool name, and now it's grown into an expansive website with an overwhelming amount of features. He recalls his first difficult decision with GN's direction: "I didn't know whether or not I wanted 'Gamers' to have a possessive apostrophe -- I mean, grammatically it should, but I didn't like it in the name. It was ugly. I also had people who were typing apostrophes into the address bar - sigh. It made sense to just leave it as 'Gamers.'"
First world problems, Steve. First world problems.
We’re still in China for our factory and lab tours, but we managed to coordinate with home base to get enough testing on the GTX 1660 done that a review became possible. Patrick ran the tests this time, then we just put the charts and script together from Dongguan, China.
This is a partner launch, so no NVIDIA direct sampling was done and, to our knowledge, no Founders Edition board will exist. Reference PCBs will exist, as always, but partners have control over most of the cooler design for this launch.
Our review will look at the EVGA GTX 1660 dual-fan model, which has an MSRP of $250 and lands $30 cheaper than the baseline GTX 1660 Ti pricing. The cheapest GTX 1660s will sell for about $220, but our $250 unit today has a higher power target allowance for overclocking and a better cooler. The higher power target is the most interesting, as overclocking performance can stretch upwards toward a GTX 1660 Ti at the $280 price-point.
We’ll get straight to the review today. Our focus will be on games, with some additional thermal and power tests toward the end. Again, as a reminder, we’re doing this remotely, so we don’t have as many non-gaming charts as normally, but we still have a complete review.
Our initial AMD Radeon VII liquid cooling mod was modified after the coverage went live. We ended up switching to a Thermaltake Floe 360 radiator (with different fans) due to uneven contact and manufacturing defects in the Alphacool GPX coldplate. Going with the Asetek cooler worked much better, dropping our thermals significantly and allowing increased overclocking and stock boosting headroom. The new drivers (19.2.3) also fixed most of the overclocking defects we originally found, making it possible to actually progress with this mod.
As an important foreword, note that overclocking with AMD’s drivers must be validated with performance at every step of the way. Configured frequencies are not the same as actual frequencies, so you might type “2030MHz” for core and get, for instance, 1950-2000MHz out. For this reason, and because frequency regularly misreports (e.g. “16000MHz”), it is critical that any overclock be validated with performance. Without validation, some “overclocks” can actually be bringing performance below stock while appearing to be boosted in frequency. This is very important for overclocking Radeon VII properly.
We recently revisited the AMD R9 290X from October of 2013, and now it’s time to look back at the GTX 780 Ti from November of 2013. The 780 Ti shipped for $700 MSRP and landed as NVIDIA’s flagship against AMD’s freshly-launched flagship. It was a different era: Memory capacity was limited to 3GB on the 780 Ti, memory frequency was a blazing 7Gbps, and core clock was 875MHz stock or 928MHz boost, using the old Boost 2.0 algorithm that kept a fixed clock in gaming. Overclocking was also more extensible, giving us a bigger upward punch than modern NVIDIA overclocking might permit. Our overclocks on the 780 Ti reference (with fan set to 93%) allowed it to exceed expected performance of the average partner model board, so we have a fairly full range of performance on the 780 Ti.
NVIDIA’s architecture has undergone significant changes since Kepler and the 780 Ti, one of which has been a change in CUDA core efficiency. When NVIDIA moved from Kepler to Maxwell, there was nearly a 40% efficiency gain when CUDA cores are processing input. A 1:1 Maxwell versus Kepler comparison, were such a thing possible, would position Maxwell as superior in efficiency and performance-per-watt, if not just outright performance. It is no surprise then that the 780 Ti’s 2880 CUDA cores, although high even by today’s standards (an RTX 2060 has 1920, but outperforms the 780 Ti), will underperform when compared to modern architectures. This is amplified by significant memory changes, capacity being the most notable, where the GTX 780 Ti’s standard configuration was limited to 3GB and ~7Gbps GDDR5.
Today, we’re reviewing the GTX 1660 Ti, whose name is going to trip us up for the entirety of its existence. The GTX 1660 Ti is NVIDIA’s mid-step between Pascal and Turing, keeping most of the Turing architectural changes to the SMs and memory subsystem, but dropping the official RTX support and RT cores in favor of a lower price. The EVGA GTX 1660 Ti XC that we’re reviewing today should have a list price of $280, sticking it between the $350 baseline of the RTX 2060 and the rough $200 price-point of modern 1060s, although sometimes that’s higher. For further reference, Vega 56 should now sell closer to $280, with the RX 590 still around the $260 range.
We won't be writing an article for this one, so just wanted to run a quick post on our new DLSS comparison in Battlefield V. This was easier to relegate to video format, seeing as it required more detailed visual comparisons than anything else. Some charts are present, but the goal is to compare DLSS on vs. off across two GPUs: The RTX 2080 Ti and the RTX 2060, each of which has different allowances for DLSS enablement.
The RTX 2060 can run DLSS at 1080p or 1440p, whereas the RTX 2080 Ti can only run DLSS at 4K, as an FPS which is too high will not allow for DLSS processing to complete before frame present (and so the 2080 Ti cannot step lower than 4K). Comparisons primarily try to find where the major upsides might be with DLSS, and they seem to mostly exist with very thin objects that have limited geometry in far distances, where DLSS can create a smoother image and eliminate some of the "marching ants" effect. On the flip-side, DLSS seems to introduce some blur to the image and doesn't outperform natively running at the lower resolution instead.
We moderate comments on a ~24~48 hour cycle. There will be some delay after submitting a comment.