- Joined
- Feb 8, 2012
- Messages
- 3,013 (0.68/day)
- Location
- Zagreb, Croatia
System Name | Windows 10 64-bit Core i7 6700 |
---|---|
Processor | Intel Core i7 6700 |
Motherboard | Asus Z170M-PLUS |
Cooling | Corsair AIO |
Memory | 2 x 8 GB Kingston DDR4 2666 |
Video Card(s) | Gigabyte NVIDIA GeForce GTX 1060 6GB |
Storage | Western Digital Caviar Blue 1 TB, Seagate Baracuda 1 TB |
Display(s) | Dell P2414H |
Case | Corsair Carbide Air 540 |
Audio Device(s) | Realtek HD Audio |
Power Supply | Corsair TX v2 650W |
Mouse | Steelseries Sensei |
Keyboard | CM Storm Quickfire Pro, Cherry MX Reds |
Software | MS Windows 10 Pro 64-bit |
Apparently, frame times logged by FRAPS differ from what you get using hardware capture.
It seems that FRAPS data, while showing micro stuttering issues with CrossFire, was actually doing AMD a favor.
The truth seems even worse:
FRAPS frame times:
Using hardware capture:
The article is at http://www.pcper.com/reviews/Graphics-Cards/Frame-Rating-Part-3-First-Results-New-GPU-Performance-Tools
Does anyone has any more info on this? Why would FRAPS data differ so much for CrossFire?
It seems that FRAPS data, while showing micro stuttering issues with CrossFire, was actually doing AMD a favor.
The truth seems even worse:
FRAPS frame times:
Using hardware capture:
The article is at http://www.pcper.com/reviews/Graphics-Cards/Frame-Rating-Part-3-First-Results-New-GPU-Performance-Tools
Does anyone has any more info on this? Why would FRAPS data differ so much for CrossFire?