Jump to content
HWBOT Community Forums

jpmboy

Members
 View Profile  See their activity

  • Posts

    525

  • Joined

  • Last visited

 Content Type 

Posts posted by jpmboy

    CPU and gpu

    in HWBOT Competitions

    Posted

    unfortunately HEDT core counts higher than 10 have not been officially released before the start of this round... so by default it's limited to what was available in retail on Aug 1st. Otherwise, there should not be a core count limit (using HEDT cpus, I think server-class cpus have always been excluded)

    ROG OCS Team Edition: Team can be created for the occasion

    in HWBOT Competitions

    Posted

    <blockquote><span style="font-weight:bold;">websmile said: </span>Yes, it is but it is the way Asus wants to promote new blood, I think it could be worse :)</blockquote><br/>

    <br/>

    Interesting to see that these days "new blood" is worth more than people who have worked hard over the years. Sad reality eh..<br/>

    <br/>

    I hope ASUS does a survey after sometime to see how much of this new blood is "real". :rolleyes:

     

    Recidivism rate? ;-) It's low, but non-Zero.

    Lol - I wouldn't go near bracketed 1/4 mile if I were you then... you have to sit there while the guy in a Pinto gets a 6 sec head start against your 650bhp C4T! But is does bring in more racers in the long term.

    ROG OCS Team Edition: Team can be created for the occasion

    in HWBOT Competitions

    Posted

    Result is final - there will be no adjustments made anymore, I will make a few notes at the end though

    1. LOD was <span style="font-weight:bold;">never!</span> allowed for time spy - we had a clarification at rules at 24.11.2016 to add this explicitly as well as file editing prohibition, but even before this, only results with valid links were accepted (was already part of the first rules draw), this means LOD or Tesselation were never allowed for time spy.

    2. It is futile to send results or report them because of temps at stage 3 because there was no obligation for temperature monitoring. Some people did for information purposes, idle temps or load during run, if they are below 25 or show only temps after run it doen´t matter.

    3. LOD settings are detected by FM reliable with the driver settings that are scanned, I did ask for a check at FM for such results and they could show me the detailed LOD setting used at driver level. If you install a new driver but don´t change settings at nvinspector, open and change a single setting and hit apply, your old still dialed in settings for LOD will be applied as well, maybe this is helpful for some guys who wonder how it can happen that LOD is detected...

     

    Thanks to Asus for making this competition happen and thanks to all participants, not all was easy to handle with Ryzen for example and the big amount of submissions, but the concept worked mostly :)

     

    Love the final caveat in your otherwise direct and to the point post "... but the concept worked mostly".

    I can't imagine the number of complaints you mods handle. Thanks! And it was a very well thought out bracketed competition. :)

    nvidiaInspector LOD +3 Max? Bypass.

    in General overclocking

    Posted

    Hello.

     

    Any one here know how to bypass the +3 LOD max on nvidiaInspector :) ?

    Did it back in the days, but forgot how.

     

    tried Version 1.9.7.6 / 1.9.7.1

     

    Thanks.

    on any version of NVI you can enter the functional max for LOD by typing in the hex value directly into the dropdown field without selecting any of the presets.

     

    0x000000F0 or 0x00000190

×
×
  • Create New...