Thankfully, we caught that early and have fixed everything. And as a reminder, that data was valid and accurate – it just wasn't put in the right place. The error was in chart generation, where nVidia and AMD cards were put on the same charts using different settings, creating an unintentional misrepresentation of our data. We also had our custom Python script (which works perfectly) for interpreting PresentMon, a new tool to FPS capture, and that threw enough production changes into the mix that we had to unpublish the content and correct it.Īll of our tests, though, were good. The error was a mix of several variables, primarily having three different folks working on the benchmarks, and working with a game that has about 40 graphics settings. We had a clerical error in our original Gears of War 4 GPU benchmark, but that's been fully rectified with this content.
0 Comments
Leave a Reply. |