21 replies to this topic

[Werne]

I found there is no diference between the 128 and 192 setting but the "254" setting will make your hardisks louder and an improvement in "access time" is given .

The program controls the HDD head movements. Reason for 192 not making a difference (along with a description of what does what):

Get/set Automatic Acoustic Management (AAM) setting. Most modern harddisk drives have the ability to speed down the head movements to reduce their noise output.  The possible values are between 0 and 254. 128 is the most quiet (and therefore slowest) setting and 254 the fastest (and loudest). Some drives have only two levels (quiet / fast), while others may  have  different  levels  between  128  and 254.  At the moment, most drives only support 3 options, off, quiet, and fast.  These have been assigned the values 0, 128, and 254 at present, respectively, but integer space has been incorporated for future expansion, should this change.

From hdparm man-page.

[spz2]

All the things i mentioned in my first post give an increase in playability i can attest for all through my own testing and i can assure you i am very meticulous in such matters . You can trust me or better yet test all the things i say in games though that may take some time , or don't trust me if you feel like it , it's all up to you mr "author". I feel like a bee that's gathered too much honey and must share .Putting common manners aside for a second i can brag about  being a PC performance myth buster haha . Use d3d overrider as it uses its own built-in V-sync mechanism with only 4 mb of ram usage and it is very very well optimized , Nvidia Inspector.exe uses the Nvidia forceware V-sync's  which are not as good , in some cases they can be complete crap, especially wuth the beta drivers. It doesn't have adaptive Vsync and it doesn't need it , because what does adaptive V-sync do ? it stops V-Sync when frames drop bellow a certain point ( relative to monitors refresh rate ) that's all it does . Why does it do that  ? Because unlike D3DOverrider V-sync with 0.000 framedop , nada! zero !  the forceware version of V-sync eats a lot of frames when it's on, though it may stop its self when after a certain point, for example in "1/2adaptive" = 60hz/2 = 30 fps, which is a fairly low fps score and you will lose the benefit of V-sync smootheness when you need it the most. And in full adaptive V-sync it would be useless because by definition it will stop when it drops bellow 60fps( from a 60 hz monitor sync) which is inevitable considering V-sync caps most games at 60 fps . And as counter intuitive as it may freakin sound THAT'S WHEN YOU NEED IT THE MOST at LOW FPS! I found that only V-sync and tripple buffering can save a game from becoming a complete slideshow in situations of 10-15 fps areas for example.  The whole Adaptive V-sync idea is a fail , it was a fail before it even got on the drawing board , i mean just use common sense Nvidia , like i do , it ain't hard. Sorry for the late reply .

Edited by spz2, 16 October 2013 - 10:19 PM.