Tuesday, January 17th 2012
EVGA Precision Updated to Version 2.1.2
EVGA has now made available a new update for its graphics card monitoring and overclocking tool known as Precision. This latest release is known as version 2.1.2 and it brings the following:
Updated EVGA Voltage Tuner:
- Fixed bug preventing EVTune from applying settings at Windows startupEVGA On-Screen Display server has been upgraded to version 4.3.1. New version gives you the following improvements:
- Added new profile setting "Enable compatibility with modified Direct3D runtime libraries" allowing EVGA On-Screen Display Server to detect runtime function offsets dynamically on each 3D application startup. This provides On-Screen Display functionality support in applications using modified Direct3D runtime libraries (e.g. FXAA injection Direct3D runtimes)
- Added new profile settings allowing you to limit the framerate during gaming. Limiting the framerate during gaming can help to reduce the power consumption as well as it can improve gaming experience due to removing unwanted microstutteing effect caused by framerate fluctuations
- Added Vector 3D On-Screen Display rendering mode support for OpenGL applications
- Added Raster 3D On-Screen Display rendering mode support for OpenGL applications using ARB shaders (e.g. ID Software's Rage)
Graph limits are now adjustable in the graph properties in "Monitoring" tab
Added unified vendor independent video memory usage monitoring layer for graphics cards, having no generic video memory monitoring interfaces implementation in display drivers. By default unified video memory usage monitoring path is enabled as a fallback path on NVIDIA graphics cards when generic NVAPI video memory usage monitoring is not available (e.g. on NVIDIA graphics cards unattached to Windows desktop, such as dedicated PhysX or other GPGPU graphics cards). Power users may redefine unified and generic video memory monitoring paths usage behaviors via the configuration file.
EVGA Precision 2.1.2 can be downloaded via this page.
Updated EVGA Voltage Tuner:
- Fixed bug preventing EVTune from applying settings at Windows startupEVGA On-Screen Display server has been upgraded to version 4.3.1. New version gives you the following improvements:
- Added new profile setting "Enable compatibility with modified Direct3D runtime libraries" allowing EVGA On-Screen Display Server to detect runtime function offsets dynamically on each 3D application startup. This provides On-Screen Display functionality support in applications using modified Direct3D runtime libraries (e.g. FXAA injection Direct3D runtimes)
- Added new profile settings allowing you to limit the framerate during gaming. Limiting the framerate during gaming can help to reduce the power consumption as well as it can improve gaming experience due to removing unwanted microstutteing effect caused by framerate fluctuations
- Added Vector 3D On-Screen Display rendering mode support for OpenGL applications
- Added Raster 3D On-Screen Display rendering mode support for OpenGL applications using ARB shaders (e.g. ID Software's Rage)
Graph limits are now adjustable in the graph properties in "Monitoring" tab
Added unified vendor independent video memory usage monitoring layer for graphics cards, having no generic video memory monitoring interfaces implementation in display drivers. By default unified video memory usage monitoring path is enabled as a fallback path on NVIDIA graphics cards when generic NVAPI video memory usage monitoring is not available (e.g. on NVIDIA graphics cards unattached to Windows desktop, such as dedicated PhysX or other GPGPU graphics cards). Power users may redefine unified and generic video memory monitoring paths usage behaviors via the configuration file.
EVGA Precision 2.1.2 can be downloaded via this page.
8 Comments on EVGA Precision Updated to Version 2.1.2
I checked it out, there is something wrong with the fan control setup.
While I have eVGA graphics cards (and motherboard), eVGA has never been (in my personal opinion) able to implement worthwhile software.
Back to Afterburner.
I suppose it is the 'slightly different' part that is the problem.
MSI makes it work, eVGA does not.
Just my opinion, however.