Guru3D, recentemente, ha pubblicato un articolo sull'ultima revisione del benchmark DirectX12 “Ashes of Singularity”, arrivando a scrivere nelle conclusioni dei pensieri totalmente errati. Perché? Perché Hilbert Hagedoorn, l'autore dell'articolo, ha preso per veritieri i risultati del test FCAT, non domandandosi del perché di valori completamente diversi rispetto a quelli visti fino ad oggi, con una AMD in pesante vantaggio su NVIDIA.

 

 

A cercare di dirimere la questione è giunto il sempre preciso e puntuale Joel Hruska, su ExtremeTech: “There’s a report making the rounds from Guru3D that shows AMD’s FCAT results as compared with Nvidia. The resulting frame time plot makes AMD look terrible, but these results aren’t accurate. The output looks the way it does because there’s a mismatch between what FCAT expects and how AMD’s driver actually performs image compositing.  […] First, some basics. FCAT is a system NVIDIA pioneered that can be used to record, playback, and analyze the output that a game sends to the display. This captures a game at a different point than FRAPS does, and it offers fine-grained analysis of the entire captured session. Guru3D argues that FCAT’s results are intrinsically correct because “Where we measure with FCAT is definitive though, it’s what your eyes will see and observe.” Guru3D is wrong. FCAT records output data, but its analysis of that data is based on assumptions it makes about the output — assumptions that don’t reflect what users experience in this case. AMD’s driver follows Microsoft’s recommendations for DX12 and composites using the Desktop Windows Manager to increase smoothness and reduce tearing. FCAT, in contrast, assumes that the GPU is using DirectFlip. According to Oxide, the problem is that FCAT assumes so-called intermediate frames make it into the data stream and depends on these frames for its data analysis. If V-Sync is implemented differently than FCAT expects, the FCAT tools cannot properly analyze the final output. The application’s accuracy is only as reliable as its assumptions, after all”.

In parole povere, con gli ultimi driver AMD ha deciso di seguire le direttive di Microsoft per la creazione dei driver, attraverso il WDM (Windows Driver Model), non supportato dal test FCAT. La stessa casa del benchmark, Oxide, ha confermato quanto scritto da Joel: “According to Oxide, Microsoft is making a huge push in Windows 10 to make the operating system cooperative, with an emphasis on smooth image presentation (which is why the AMD driver composites using WDM instead of DirectFlip). DirectFlip also isn’t as power-efficient as WDM. All of these considerations, however, make it more difficult to profile applications”.

In risposta, il redattore di Guru3D ha scritto, in maniera sprezzante ed arrogante, quanto segue: “I find the answer (quella di Joel, ndr) to be more complicated as they explain. I am not a programmer hence (and gosh I do not wish to be one) I have to deal with findings and results on a more basic level”. Tradotto: “Non avendo le capacità tecniche per comprendere quanto faccio, mi limito a sparare cazzate come un FaviJ qualunque”.