Tuesday, April 10th 2012
EVGA Precision X Updated to Version 3.0.2
EVGA has today rolled out a new version (3.0.2) of its Precision X GPU overclocking software. This latest release includes a new skin (EVGA Classified), support for hardware monitoring history logging, and is bundled with the new EVGA VoltageTuner utility.
Download Precision X
Full 3.0.2 changelog
- Added "Always on top" setting to the context menu of detached hardware monitor window. When this option is disabled, hardware monitoring window can be minimized to the taskbar when it is detached from the main window
- Added hardware monitoring history logging support. Now EVGA Precision is able to save history in native RivaTuner Hardware Monitoring Log file format. The log files captured with EVGA Precision can be viewed in any text editor like Notepad or in graphics form in RivaTuner's HML file viewer (RivaTuner must be installed for viewing log files in graphics form)
- Maximum framerate target increased to 120 FPS
- Maximum length of GPU name for GPU selection buttons has been increased to 10 symbols
- Added new "Force fan speed update on each period" option to the "Fan" tab. New option may improve compatibility of software automatic fan speed control mode with some bugged display drivers, overriding manually programmed fan speed under certain conditions
- Bundled EVGA EVTune utility has been replaced with brand new EVGA VoltageTuner utility
- Added bundled EVGA Bridge utility, allowing controlling EVGA Precision via Bluetooth from Android smartphones. The bridge utility is automatically started by EVGA Precision when "Enable external access to application via Bluetooth" is ticked in advanced settings
- Fixed issue in skin engine causing boost clock marker legend to be rendered improperly under certain conditions
- Added new "EVGA Classified" skin
Download Precision X
- Added "Always on top" setting to the context menu of detached hardware monitor window. When this option is disabled, hardware monitoring window can be minimized to the taskbar when it is detached from the main window
- Added hardware monitoring history logging support. Now EVGA Precision is able to save history in native RivaTuner Hardware Monitoring Log file format. The log files captured with EVGA Precision can be viewed in any text editor like Notepad or in graphics form in RivaTuner's HML file viewer (RivaTuner must be installed for viewing log files in graphics form)
- Maximum framerate target increased to 120 FPS
- Maximum length of GPU name for GPU selection buttons has been increased to 10 symbols
- Added new "Force fan speed update on each period" option to the "Fan" tab. New option may improve compatibility of software automatic fan speed control mode with some bugged display drivers, overriding manually programmed fan speed under certain conditions
- Bundled EVGA EVTune utility has been replaced with brand new EVGA VoltageTuner utility
- Added bundled EVGA Bridge utility, allowing controlling EVGA Precision via Bluetooth from Android smartphones. The bridge utility is automatically started by EVGA Precision when "Enable external access to application via Bluetooth" is ticked in advanced settings
- Fixed issue in skin engine causing boost clock marker legend to be rendered improperly under certain conditions
- Added new "EVGA Classified" skin
10 Comments on EVGA Precision X Updated to Version 3.0.2
(I know you haz... trollface)
T_T
This loads for me as the posted link just hung up with just the background showing. :banghead:
just a heads up.
and thank you Cristian_25H :cool:
www.evga.com/precision/
Flashing HD7870 DCUII, suddenly asus GPU tweak has voltage support.
I don't need this BS, i don't wanna jerk around 5-6 softwares that each has it's own set of controllers supported.
Wish unwinder could fix it soon.
Anyway its not the big issue, the issue as it mentioned is to deal with voltage control via software. As a reviewer (and unlike many reviewers) i owe it to my readers (till of course there's just no way and even then see the above what i done in order to get it to work).
Unfortunatly, I'm not a programmer like w1zz who can basically add it to his sorta unified control software.
So your whole dilemma is predicated on one single card not functioning?