•  Added On-Screen Display performance profiler. Power users may enable it to measure and visualize CPU and GPU performance overhead added by On-Screen Display rendering. Two performance profiling modes are available:
• Compact mode provides basic and the most important CPU prepare (On-Screen Display hypertext formatting, parsing and tessellation), CPU rendering and total CPU times, as well as GPU rendering time (currently supported for Direct3D9+ and OpenGL applications only)
• Full mode provides additional and more detailed per-stage CPU times.
• Improved built-in framerate limiter:
• Fractional framerate limit adjustment functionality is no longer power user oriented, now you may specify fractional limit directly from GUI
• Now you may click “Framerate limit” caption to switch framerate limiter to alternate “Frametime limit” mode. New mode allows you to specify the limit directly as a target frametime with 1 microsecond precision
• Added alternate framerate limiting mode, based on synchronization with display rasterizer position. Now you may synchronize the framerate to up to two independent scanline indices per refresh interval. Combining with power user configurable scanline wait timeout and graphics pipeline flushing options, those settings provide experienced users vendor agnostic ultra low input lag adaptive VSync, half VSync or double VSync functionality on any hardware
• Added power user oriented idle framerate limiting mode. Unlike traditional framerate limiting mode, idle framerate limiting mode is only affecting inactive 3D applications running in background. Idle framerate limit is specified as a target frametime with 1 microsecond precision. Idle framerate limiting mode helps to reduce power consumption when you minimize some heavy 3D applications and switch to other processes
• Various On-Screen Display optimizations and improvements:
• Added adjustable minimum refresh period for On-Screen Display renderer. The period is set to 10 milliseconds by default, so now the On-Screen Display is not allowed to be refreshed more frequently than 100 times per second. Such implementation allows keeping smooth animation when On-Screen Display contents are being updated on each frame (e.g. when displaying realtime frametime graph) without wasting too much CPU time on it
• Added alternate GPU copy based Vector2D On-Screen Display rendering mode implementation for Direct3D1x applications. New mode provides up to 5x Vector2D performance improvement on NVIDIA graphics cards, however it is disabled on AMD hardware due to slow implementation of CopySubresourceRegion in AMD display drivers
• Vector2D rendering mode is now forcibly disabled in Vulkan applications on AMD graphics cards due to insanely slow implementation of vkCmdClearAttachments in AMD display drivers
• Revamped geometry batching and vertex buffer usage strategy in pure Direct3D12 On-Screen Display renderer (currently used in Halo Wars 2 only)
• Added Vector2D rendering mode support to pure Direct3D12 On-Screen Display renderer
• Optimized On-Screen Display hypertext parsing and tessellation implementation
• Optimized state changes in OpenGL On-Screen Display rendering guru implementation
• Improved implementation of On-Screen Display rendering from separate OpenGL context (profile compatibility switch used in certain OpenGL applications, e.g. Pyre) on AMD graphics cards
• Optimized state changes in Direct3D1x On-Screen Display rendering implementation
• Solid rectangles and line primitives in Direct3D8 and Direct3D9 On-Screen Display rendering implementations are now rendered from vertex buffer instead of user memory
• Improved OpenGL framebuffer dimensions detection when framebuffer coordinate space is selected
• Increased static vertex buffer size for Vulkan and pure Direct3D12 renders to increase amount of primitives rendered in On-Screen Display in a single pass
• Improved desktop duplication based desktop video capture implementation ( Windows 8 and newer OS versions):
• Now desktop video recording sessions do not stop on display mode switch or on switch to exclusive fullscreen mode. Such approach allows you to start capturing video on desktop then launch some 3D application and create a video file containing both desktop and 3D application’s video streams
• Improved video capture API allows video capture frontend applications (e.g. MSI Afterburner) to force desktop or 3D application video capture modes in addition to default mixed desktop/3D application capture mode
• Now desktop capture is using multhithreaded active busy-wait loop frame capture instead of timer driven frame capture in order to improve frame timing precision and resulting video smoothness. The previous timer driven frame capture can be enabled via configuration file if necessary
• Decreased desktop duplication timeouts in order to improve RivaTuner Statistics Server GUI response time under certain conditions during desktop videocapture sessions in timer driven frame capture mode
• Improved SDK:
• Improved RTSSFrametimePipeSample sample. Now the sample demonstrates frametime pipe connection for applications running with both full administrative and limited user rights
• Improved NVENC plugin. Added NVIDIA 416.xx drivers family support. The plugin was recompiled with newer NVENC encoder API headers, because NVIDIA stopped supporting legacy v4 NVENC API in release 416 and newer series drivers. Due to this change NVENC plugin no longer supports pre-release 358 NVIDIA drivers 
• Fixed On-Screen Display rendering in wrong colors when Vector2D mode is selected and Direct3D1x applications use 10-bit framebuffer
• Fixed Vulkan fence synchronization issue, which could cause GPU-limited Vulkan applications to hang due to attempt to reuse busy command buffer
• Active busy-wait loop in the framerate limiter module is now forcibly interrupted during unloading the hooks library to minimize the risk of deadlocking 3D application when dynamically closing RivaTuner Statistics Server during 3D application runtime
• Improved CBT hooks uninstallation routine to minimize the risk of deadlocking 3D application when dynamically closing RivaTuner Statistics Server during 3D application runtime
• Improved validation in OpenGL On-Screen Display rendering routine to minimize the risk of crashing OpenGL applications
• Changed OpenGL cleanup routines to improve compatibility with OpenGL applications using multiple rendering contexts (e.g. GPU Caps Viewer)
• Improved synchronization in 32-bit API hook uninstallation routines
• Added timeout to API hooks injection in CBT hook handler. The timeout is aimed to reduce injection related CPU overhead on some systems, related to high mouse polling rate combined with keyboard/mouse hooks installed by third party applications
• Interoperability D3D10 page flips on some systems are now filtered by framerate calculation module in OpenGL/Vulkan applications
• Hook engine is now using alternate double jump x64 hook trampoline to improve compatibility with third party 64-bit On-Screen Display applications
• Added compatibility profile switch for hooking IDXGISwapChain::ResizeBuffers via VTable instead of hotpatching
• Added hook epilogs support to 32-bit VTable hook handler
• Fixed instance checking implementation in 64-bit RTSSHooksLoader and EncoderServer helper applications
• Added exclusion profile for Forza Horizon 4. Please take a note that On-Screen Display is currently not supported in this game due to its protective system limitations
• Forcible graphics and compute queues synchronization is now disabled by default for Vulkan applications presenting frames from compute queue (AMD Vulkan rendering codepaths in DOOM and Wolfenstein II : The New Colossus). Due to this change, On-Screen Display will be invisible in those games on such platforms by default. Experienced users, understanding and accepting that On-Screen Display rendering will cause performance penalty, may re-enable it with PresentFromCompute profile switch
• Added tri-state skinned buttons support in the skin engine
• Updated profiles list

• Added On-Screen Display locking mechanism for third party On-Screen Display client applications. The mechanism is aimed to eliminate unwanted On-Screen Display flickering effect when some client application is performing risky two-stage On-Screen Display refresh while On-Screen Display is being actively refreshed by another client. Please take a note that third party On-Screen Display clients must be also updated in order to use this mechanism and get rid of flickering
• Added new text formatting tags support for displaying minimum, average, maximum, 1% low and 0.1% low framerates in benchmark mode. The tags are allowing On-Screen Display clients to display independent benchmark statistics simultaneously for multiple running 3D applications instead of displaying foreground 3D application statistics only
• Now it is possible to adjust frametime history graph size via RivaTuner Statistics Server properties. Please take a note that you may use positive values to specify the size in pixels or negative values to specify it in symbols
• Now it is possible to toggle benchmark mode state from RivaTuner Statistics Server properties. However, third party benchmark client applications like MSI Afterburner are still required to toggle benchmark mode state with hotkeys during 3D application runtime and to save benchmark results to a text file
• Now it is possible to toggle between averaged or instantaneous calculation modes for peak (i.e. minimum and maximum) framerates for benchmark mode via RivaTuner Statistics Server properties
• Fixed issue in context help system, which could cause the tooltip to flicker when it was displayed below mouse cursor
• Fixed screen capture feature in On-Screen Display preview window when RivaTuner Statistics Server is installed in UAC-protected folder
• Updated SDK:
• Now RTSSSharedMemorySample sample code is demonstrating the implementation of On-Screen Display locking and flickering filter
• Updated profiles list

• New unified geometry batching implementation for all supported 3D APIs provides more efficient On-Screen Display rendering and more easily extendable renderer architecture
• Due to new unified geometry batching implementation bar chart graphs are now being rendered in a single pass with On-Screen Display text
• Added new formatting tags for displaying embedded bars
• Fixed multithreaded audio encoder uninitialization issue, which could cause temporary prerecord files not to be deleted when prerecording video to a file
• Updated profiles list

Version 7.0.0 

• Added initial Microsoft UWP applications support. Now RivaTuner Statistics Server provides full On-Screen Display, framerate/frametime statistics collection and framerate limiting support for sandboxed Windows 10 store applications. Screencapture and videocapture are currently not supported in UWP environment
• New default Metro interface styled skin designed by 00pontiac
• Default skin composition mode is now set to layered mode with color key and light transparency
• Improved default On-Screen Display rendering configuration provides better default On-Screen Display appearance on modern mainstream PC display resolution. Now raster 3D rendering mode with Unispace font and shadow rendering are enabled and zooming ratio is set to 3 by default
• Framerate is now displayed as integer value, however you may return back to floating point framerate representation with configuration file switch if necessary
• Hook engine is now using alternate shorter x64 hook trampoline to provide compatibility with Windows 10 Creators Update Direct3D9 runtimes. The previous trampoline can be enabled via the configuration file if necessary
• Hook libraries are now digitally signed by MSI to simplify and speed up the process of new versions’ whitelisting by third party anticheat systems. Thanks to MSI, EAC and BattleEye for making it possible!
• Fixed bug in Vulkan On-Screen Display cleanup code causing The Talos Principle to crash to desktop on changing video settings
• Improved On-Screen Display rendering quality in Direct3D1x applications using sRGB framebuffers
• Fixed bug is skin engine causing part of the profiles window to be rendered in solid black color when using layered skin composition mode with alpha channel
• Fixed crash on startup under Windows Vista with no platform update installed
• On-Screen Display is no longer being rendered improperly when switching between vector and raster On-Screen Display rendering modes during Direct3D1x application runtime
• FCAT overlay support is no longer limited to vector On-Screen Display rendering modes in Direct3D1x applications, now it is also supported for Direct3D1x applications when raster 3D On-Screen Display rendering mode is enabled
• On-Screen Display shadow in now rendered in proper RGB colors instead of BGR in On-Screen Display preview window
• New On-Screen Display shadow rendering for raster 3D mode provides improved shadow rendering quality for some combinations of fonts and low On-Screen Display zooming ratios. The previous mode can be also enabled via profile if necessary
• Now “Delete profile” button is unlocked when “Hide pre-created profiles” option is enabled and template based profile is selected
• Now you may hold <Ctrl> when pressing “!dd profile” button to create a profile for currently active 3D applications, or hold <Shift> to create a profile with disabled application detection (i.e. exclusion) for currently active 3D applications
• Added On-Screen Display transparency support. New On-Screen Display color picker window allows you to adjust color opacity level to make On-Screen Display to appear semi-transparent if necessary. Please take a note that transparency if fully supported for raster 3D On-Screen Display rendering mode. Some symbols of polygonal vector 3D font can be rendered with artifacts when transparency is selected and vector 2D mode doesn’t support transparency at all
• Added On-Screen Display background color fill mode. New “On-Screen Display fill” option allows you fill underlying On-Screen Display area with solid or transparent color. Fill color and transparency level can be customized in “On-Screen Display palette” colors list
• Updated SDK:
• Improved shared memory layout. Now each running 3D application entry contains x64/UWP application architecture usage flags in addition to previously available 3D API usage flags
• Added text formatting tags support for On-Screen Display text. Now the client applications using RivaTuner Statistics Server to render a text in On-Screen Display (e.g. AIDA, HwInfo or MSI Afterburner itself) can apply custom text colors, alignment, size and position to some parts of displayed text. Format tags are fully supported for raster 3D On-Screen Display rendering mode only, some tags are ignored for vector On-Screen display rendering modes
• Improved On-Screen Display text macro translator. To provide more flexibility and customization %FRAMERATE% macro is now deprecated and replaced with new tags allowing printing application specific framerate, frametime and 3D API independently
• Updated RTSSSharedMemorySample sample code. Now the sample demonstrates text format tags usage and shows you how to apply custom On-Screen Display color, subscript style and custom alignment to a text rendered in On-Screen Display from a client application. The sample also demonstrates framerate display via both %FRAMERATE% macro and new tags
• Improved On-Screen Display preview window:
• Now you may detach and set custom position and size of preview window by double clicking preview window area. Increased size of preview window can be useful if you prefer to adjust On-Screen Display position visually via dragging it inside the preview
• Now you may right click preview window area and select “Capture screenshot” command from the context menu to automatically capture screenshot from currently running 3D application and use it as On-Screen Display preview background, or use“Load” command to open and load some previously captured screenshot. This feature can be useful if you prefer to adjust On-Screen Display position visually via dragging it inside the preview. Original On-Screen Display preview window background can be restored with “Clear” command from the context menu
• Improved dynamic Direct3D12 presentation command queue detection algorithm
• Added On-Screen Display support for Direct3D11 applications using alternate frames presentation technique (e.g. Halo Wars Definitive Edition)
• Added power user oriented profile compatibility setting, allowing enabling alternate VTable based hooking for Direct3D1x applications concurrently presenting frames from multiple threads (e. g. Forza Horizon 3 or Halo Wars 2)
• Added power user oriented profile compatibility setting, allowing enabling pure Direct3D12 On-Screen Display renderer for some Direct3D12 applications conflicting with D3D11on12 interop layer (e.g. Halo Wars 2)
• Added power user oriented profile compatibility setting for OpenGL applications rendering from forward compatible 3.x+ context with disabled deprecated immediate OpenGL mode functionality. The switch allows the server to fall back to rendering path using a separate legacy OpenGL context
• Added On-Screen Display profile for Wolfenstein : The New Order 
• Added On-Screen Display profile for Citra Nintendo 3DS emulator 
• Added On-Screen Display profile for CEMU Wii U emulator
• Revamped internal benchmarking engine 
• Updated profiles list