2D Graphics Markk and Performance Test V11 Biuild 1017

[zenmota]

After Updating to Version 11 Build 1017 of Performance Test, my 2D Graphics Mark seems to be cut in half. It was around 1600 with V11 Build 1016, with V11 Build 1017 it is around 700. No changes were made to system hardware, driver updates or Windows Updates. Have attached 2 screenshots (one with build 1016 and one with build 1017). Also, system info.


Thanks

[David (PassMark)]

There was no changes made to the 2D benchmark test between these releases.

Is this reproduceable with build 1017 or was it a one off bad result?

What are the individual results for the suite of 2D tests?

[zenmota]

I get about the same results for the 2D Graphics Mark every time I run Build 1017 (about half what it was in Build 1016). I even uninstalled Build 1017 and installed Build 1016. When I run Build 1016 the 2D Mark is about double that of Build 1017. Uninstall Build 1016 and install Build 1017 and 2D Mark is about half that of Build 1016. Like I said, no changes in Hardware, Drivers, Windows Updates or Windows settings. Settings in Performance Test are default. Have attached screenshot of just 2D Mark in Build 1017.


Thanks

[zenmota]

Perhaps you could run Build 1016 on a system to see what you get on 2D Mark. Then run Build 1017 on the same system to see what you get. See if there is any difference. Not trying to tell what to do.

Thanks

[David (PassMark)]

OK, you are right. Something got busted.
Your Direct2D result is very low compared to what it should be for your hardware. All your other tests appear fine, above average in fact.

I also replicated a before / after bug on my machine with the latest patch release.



The benchmark test itself is fine (and the correct FPS data is displayed while the test is running) but when displaying the result, somehow we now have the decimal point in the wrong place!
Pretty strange and not deliberate.

We'll investigate and get it fixed tomorrow.

[zenmota]

Ok, Great. Thanks for looking into it. Didn't noticed the decimal point.

[OldMike65]

OK, you are right. Something got busted.
Your Direct2D result is very low compared to what it should be for your hardware. All your other tests appear fine, above average in fact.

I also replicated a before / after bug on my machine with the latest patch release.



The benchmark test itself is fine (and the correct FPS data is displayed while the test is running) but when displaying the result, somehow we now have the decimal point in the wrong place!
Pretty strange and not deliberate.

We'll investigate and get it fixed tomorrow.

Good news because I've got the exact same issue on version 1017 ....had to reinstall version 1015 ...which works fine. Glad you guys are fixing this issue. I am also a paid user ...Mike

[OldMike65]

OK, you are right. Something got busted.
Your Direct2D result is very low compared to what it should be for your hardware. All your other tests appear fine, above average in fact.

I also replicated a before / after bug on my machine with the latest patch release.



The benchmark test itself is fine (and the correct FPS data is displayed while the test is running) but when displaying the result, somehow we now have the decimal point in the wrong place!
Pretty strange and not deliberate.

We'll investigate and get it fixed tomorrow.

Thanks for fixing this issue ....because of the decimal point in the wrong place, it lowers the whole total score also ...by a lot

[David (PassMark)]

Should be fixed in release V11 Build 1018
https://www.passmark.com/products/pe...st/history.php

The problem was that the system information was not being collected correctly for the display. So it looked like the primary display had a resolution of 0 x 0 pixels. This then messed up the scaling of this 2D test.

We are going to flag all submitted results from build 1017 as invalid, given the test results are wrong.

[zenmota]

That seems to have fixed the problem. Thanks for the quick fix.

[OldMike65]

That seems to have fixed the problem. Thanks for the quick fix.

Same here the new version 1018 is working Great ....Thanks guys for the quick fix.