• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

S@Hers! Please read!

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
For stats & gaming benchmarks 🙂

BK
I went to download you proggy & I get this

We're sorry, but this page is currently unavailable for viewing.
If this site belongs to you, please read this help page for more information and assistance

[update]

Never mind I did 'save target as' & I got it 🙂
 
BK - no it won't be null and void, especially in light of the discussion pertaining to changing the Ars benchmark WU. The current benchmark unit is a high angle range one (6.718) and we've determined (at least with the 3.00 clients), that a number of seti calcs are not being performed on the VHARs like that one. Thus if you're trying to determine which runs a WU faster overall, say 98 or NT, you would get very different answers if you ran a VHAR vs a mid or VLAR. Since the VHARs and VLARs do not constitute the majority of WUs being distributed, then overall, your predictions based on OS alone would be faulty if you run a bench using only the VHAR.

Thus with the 3.03 coming out now, there seems to be a call to gather info again - particularly on the WU AR that we're looking at - 0.417, which seems to be the most common and one that seems to trigger most if not all of the seti calcs. There's also some discussion about possibly coming up with some computational factors to account for different OSes etc. in order to predict WU times...

So there is a use for your proggy! 🙂
 
Back
Top