be quiet! Dark Rock PRO TR4 review
MSI GeForce RTX 2060 Gaming Z review
Palit GeForce RTX 2060 GamingPro OC review
Promo: MS Office 2016 Pro Plus Key For $31.5
Corsair IronClaw RGB mouse review
Corsair Harpoon RGB Wireless mouse review
Corsair M65 RGB ELITE game mouse review
GeForce RTX 2060 review (founder)
WD Black NVME SSD (1TB) Review
Seasonic Focus SGX-650 Power Supply review
Guru3D RTSS Rivatuner Statistics Server Download v7.2.0 Final
on: 10/30/2018 09:49 AM [ 27 comment(s) ]
Advertisement
Here you can download RTSS Rivatuner Statistics Server. Initially designed as a small helper application for RivaTuner graphics card utility, RivaTuner Statistics Server became de-facto framerate monitoring, On-Screen Display and high-performance videocapture service provider for other graphics card utilities.
We've moved RTSS 7.2.0 Beta towards an official final release. Build 19063 is available for official download here. There are no serious changes comparing to the previous beta, just internal pre-release code/documentation cleanups and minor improvement for scanline sync mode: it is no longer necessary to restart 3D application after enabling Scanline Sync x/2 mode, now it is applied in realtime. We always suggest that you download latest full beta package of MSI Afterburner which always includes a stable build of RTSS - Download here.
Note: Does your overlay not work anymore after the update? Please perform a full uninstall of RTSS and AfterBurner (with profiles removal) and perform a CLEAN install of it.
Features:
- The server provides framerate and frametime monitoring support to the client applications. Framerate and frametime statistics is being collected for DirectX and OpenGL applications. The statistics can be rendered in On-Screen Display or provided to client applications connected to the server.
- The server provides 3D acceleration usage statistics to the client applications. The clients can use the statistics to determine if any 3D applications are currently running and apply different hardware profiles depending on it.
- The server provides On-Screen Display support to the client applications. The clients can display any text info in the On-Screen
- Display in DirectX and OpenGL applications. The server can be also used as a standalone framerate monitoring solution and display own framerate statistics in the On-Screen Display.
- The server provides desktop and in-game screen capture support to the client applications. BMP, PNG and JPG screen capture formats are supported.
- The server provides high-performance realtime desktop and in-game video capture support to the client applications.
- Uncompressed, high-performance custom RTV1 and native MJPG video encoding, encoding with third-party external VFW compatible codecs (e.g. Lagarith or x264vfw) and hardware accelerated H.264 encoding via Intel QuickSync, NVIDIA NVENC and AMD VCE are supported in conjunction with wide range of additional video capture related options, multisource stereo and multichannel (for Window Vista and newer) audio capture with Push-To-Talk support. The functionality of expensive commercial video capture products is now available to everyone absolutely for free! There is no need to buy dedicated video capture software anymore!
- Framerate limiting support. Limiting the framerate during gaming can help to reduce the power consumption as well as it can improve gaming experience due to removing unwanted microstuttering effect caused by framerate fluctuations.
- User extendable architecture. You may express your creativity and design your own skins for RivaTuner Statistics Server, create localization for your native language, use the server to display any custom text in On-Screen Display directly from your own application and many, many more!
System requirements:
- Windows XP, Windows Vista, Windows 7, Windows 8 or Windows 10 (both x86 and x64 versions) with full administrative rights
- Any DirectX, Vulkan or OpenGL compatible graphics card
Version 7.2.0 :
- 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
Version 7.1.0
- 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
Version 7.0.2
- 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
2 pages 1 2
cryohellinc
Senior Member
Posts: 2166
Joined: 2014-10-20
Senior Member
Posts: 2166
Joined: 2014-10-20
#5601540 Posted on: 10/30/2018 10:39 AM
Thank you for this continuous effort.
Thank you for this continuous effort.
Unwinder
Moderator
Posts: 13728
Joined: 2000-09-05
Moderator
Posts: 13728
Joined: 2000-09-05
#5601541 Posted on: 10/30/2018 10:44 AM
Done it is when.
Final build of Afterburner package with this RTSS when will be released?
Done it is when.
DJLRADEON
Junior Member
Posts: 13
Joined: 2014-09-29
Junior Member
Posts: 13
Joined: 2014-09-29
#5601552 Posted on: 10/30/2018 11:28 AM
hoping it works with Forza Horizon 4
hoping it works with Forza Horizon 4
Unwinder
Moderator
Posts: 13728
Joined: 2000-09-05
Moderator
Posts: 13728
Joined: 2000-09-05
#5601553 Posted on: 10/30/2018 11:30 AM
I'm also hoping that users start reading release notes one day. Hehe. Nope, it doesn't work. And it is documented why.
hoping it works with Forza Horizon 4
I'm also hoping that users start reading release notes one day. Hehe. Nope, it doesn't work. And it is documented why.
YouLose 66
Junior Member
Posts: 1
Joined: 2018-10-30
Junior Member
Posts: 1
Joined: 2018-10-30
#5601575 Posted on: 10/30/2018 12:30 PM
hoping it works with Forza Horizon 4
Right Way, i hope it to, sad that Forza just crash.
hoping it works with Forza Horizon 4
Right Way, i hope it to, sad that Forza just crash.
Unwinder
Moderator
Posts: 13728
Joined: 2000-09-05
Moderator
Posts: 13728
Joined: 2000-09-05
#5601596 Posted on: 10/30/2018 01:03 PM
Right Way, i hope it to, sad that Forza just crash.
Answered one post above.
Right Way, i hope it to, sad that Forza just crash.
Answered one post above.
coolhwhip
Junior Member
Posts: 1
Joined: 2018-10-31
Junior Member
Posts: 1
Joined: 2018-10-31
#5601918 Posted on: 10/31/2018 06:07 AM
Trying to install latest version and keep getting "RivaTuner Statistics Server is currently active, install process will be aborted" message. Tried to uninstall current RivaTuner v7.1.0 and get the same message. What am I doing wrong?
Trying to install latest version and keep getting "RivaTuner Statistics Server is currently active, install process will be aborted" message. Tried to uninstall current RivaTuner v7.1.0 and get the same message. What am I doing wrong?
Unwinder
Moderator
Posts: 13728
Joined: 2000-09-05
Moderator
Posts: 13728
Joined: 2000-09-05
#5601919 Posted on: 10/31/2018 06:13 AM
The message is telling you what are you doing wrong. You cannot install or uninstall RTSS while it is running.
The message is telling you what are you doing wrong. You cannot install or uninstall RTSS while it is running.
Lucasx32
Junior Member
Posts: 1
Joined: 2018-10-31
Junior Member
Posts: 1
Joined: 2018-10-31
#5602134 Posted on: 10/31/2018 07:38 PM
Nice work guys! How can I enable the performance profiler to see GPU and CPU times?
Nice work guys! How can I enable the performance profiler to see GPU and CPU times?
Fox2232
Senior Member
Posts: 8133
Joined: 2012-07-20
Senior Member
Posts: 8133
Joined: 2012-07-20
#5602176 Posted on: 10/31/2018 09:45 PM
@Unwinder : I think that you should have mentioned as 1st thing about CPU/GPU Profiler that it is there to show CPU/GPU time per frame used by RTSS. I understand why you made that feature. But on 1st look one would expect it to be statistic for entire frame time, not just RTSS cost.
So, at 1st I was like: Wow, that must have been a lot of hard work. Then I enable it and see tiny numbers which hinted either error in measurement, bad decimal point or that it is measuring something else than I thought. I understood it only after reading release notes again with those numbers in mind.
Either way, thanks!
@Unwinder : I think that you should have mentioned as 1st thing about CPU/GPU Profiler that it is there to show CPU/GPU time per frame used by RTSS. I understand why you made that feature. But on 1st look one would expect it to be statistic for entire frame time, not just RTSS cost.
So, at 1st I was like: Wow, that must have been a lot of hard work. Then I enable it and see tiny numbers which hinted either error in measurement, bad decimal point or that it is measuring something else than I thought. I understood it only after reading release notes again with those numbers in mind.
Either way, thanks!
ambros
Junior Member
Posts: 1
Joined: 2018-11-02
Junior Member
Posts: 1
Joined: 2018-11-02
#5602806 Posted on: 11/02/2018 09:44 PM
ne fonctionne pas avec "fallout 76" et " overwatch"
rtss bloque ouverte des jeux
obliger de désactiver rtss pour jouer
ne fonctionne pas avec "fallout 76" et " overwatch"
rtss bloque ouverte des jeux
obliger de désactiver rtss pour jouer
Unwinder
Moderator
Posts: 13728
Joined: 2000-09-05
Moderator
Posts: 13728
Joined: 2000-09-05
#5609457 Posted on: 11/21/2018 03:01 PM
endless crashes in BF5 also in Tom Clancy's The Division dx12 also in other games! bought an analog much better from Russian developers of FPS Monitoring!
My nerves are more expensive to me, it's better to pay a penny, but it's much more comfortable and beautiful\
My nerves are more expensive for me as well so you'll continue spam with advertisement in some different place. RTSS is also Russian product BTW, which doesn't prevent it from being free. And such honest kind of ads just smells bad. So bye.
endless crashes in BF5 also in Tom Clancy's The Division dx12 also in other games! bought an analog much better from Russian developers of FPS Monitoring!
My nerves are more expensive to me, it's better to pay a penny, but it's much more comfortable and beautiful\
My nerves are more expensive for me as well so you'll continue spam with advertisement in some different place. RTSS is also Russian product BTW, which doesn't prevent it from being free. And such honest kind of ads just smells bad. So bye.
EvilGhost666
Junior Member
Posts: 3
Joined: 2018-12-01
Junior Member
Posts: 3
Joined: 2018-12-01
#5612377 Posted on: 12/01/2018 01:04 PM
What are you did with RTSS????? Today if i close RTSS - is start automatly AGAIN!
I trying to play X4 (new game), but can't with RTSS, because black screen, if i close RTSS - all is fine, but i need to close MSI Afterburner for close RTSS >_<
WHY YOU DID IT?
X4 just kick RTSS and can't give me a chance for play.
A lot of games didn't work with RTSS and this is another...
What are you did with RTSS????? Today if i close RTSS - is start automatly AGAIN!
I trying to play X4 (new game), but can't with RTSS, because black screen, if i close RTSS - all is fine, but i need to close MSI Afterburner for close RTSS >_<
WHY YOU DID IT?
X4 just kick RTSS and can't give me a chance for play.
A lot of games didn't work with RTSS and this is another...
Unwinder
Moderator
Posts: 13728
Joined: 2000-09-05
Moderator
Posts: 13728
Joined: 2000-09-05
#5612391 Posted on: 12/01/2018 01:44 PM
Registering here to create a hate post written in bold is counterproductive, educating yourself and RTFM'ing is much more effective way. No, RTSS is not starting itself, never started and never will. Client applications like MSI AB always do that if _you_ enable some functionality that require RTSS. It was so since day one, it is documented in both readme and context help. So RTFM please and no need to continue posting using such tone.
And why I'm not surprised that IP is Russian too
Registering here to create a hate post written in bold is counterproductive, educating yourself and RTFM'ing is much more effective way. No, RTSS is not starting itself, never started and never will. Client applications like MSI AB always do that if _you_ enable some functionality that require RTSS. It was so since day one, it is documented in both readme and context help. So RTFM please and no need to continue posting using such tone.
And why I'm not surprised that IP is Russian too
ultraex2003
Senior Member
Posts: 117
Joined: 2012-07-26
Senior Member
Posts: 117
Joined: 2012-07-26
#5612393 Posted on: 12/01/2018 01:53 PM
What are you did with RTSS????? Today if i close RTSS - is start automatly AGAIN!
I trying to play X4 (new game), but can't with RTSS, because black screen, if i close RTSS - all is fine, but i need to close MSI Afterburner for close RTSS >_<
WHY YOU DID IT?
X4 just kick RTSS and can't give me a chance for play.
A lot of games didn't work with RTSS and this is another...
bro !!! are you mean the game x4 Foundation for me run very well with msi ab+rtss 7.2.0 i have win 7 os
What are you did with RTSS????? Today if i close RTSS - is start automatly AGAIN!
I trying to play X4 (new game), but can't with RTSS, because black screen, if i close RTSS - all is fine, but i need to close MSI Afterburner for close RTSS >_<
WHY YOU DID IT?
X4 just kick RTSS and can't give me a chance for play.
A lot of games didn't work with RTSS and this is another...
bro !!! are you mean the game x4 Foundation for me run very well with msi ab+rtss 7.2.0 i have win 7 os
-Tj-
Senior Member
Posts: 15895
Joined: 2012-05-18
Senior Member
Posts: 15895
Joined: 2012-05-18
#5612397 Posted on: 12/01/2018 02:01 PM
^Same here on windows 10 Rs5,
X4 runs fine without a issue, played it yesterday.
^Same here on windows 10 Rs5,
X4 runs fine without a issue, played it yesterday.
Unwinder
Moderator
Posts: 13728
Joined: 2000-09-05
Moderator
Posts: 13728
Joined: 2000-09-05
#5612407 Posted on: 12/01/2018 02:47 PM
^Same here on windows 10 Rs5,
X4 runs fine without a issue, played it yesterday.
Yep, and in addition to that I just needed to buy X4. Buy just to confirm the next fake bugreport. Two games purchased per day just to see that someone is mistaking is too much, heh.
^Same here on windows 10 Rs5,
X4 runs fine without a issue, played it yesterday.
Yep, and in addition to that I just needed to buy X4. Buy just to confirm the next fake bugreport. Two games purchased per day just to see that someone is mistaking is too much, heh.
EvilGhost666
Junior Member
Posts: 3
Joined: 2018-12-01
Junior Member
Posts: 3
Joined: 2018-12-01
#5612433 Posted on: 12/01/2018 04:50 PM
Strange Guys, just i can play X4, but only if RTSS closed With RTSS last update - blackscreen
Win 10, this is first game with problem for last 5-6 years.
Maybe i can change config file of X4? For fps limite? ^^
And guys, how to close RTSS without close MSI Afterburner?
Only today i see problem: if i close RTSS - RTSS open again automatic
Strange
Guys, just i can play X4, but only if RTSS closed With RTSS last update - blackscreen Win 10, this is first game with problem for last 5-6 years.
Maybe i can change config file of X4? For fps limite? ^^
And guys, how to close RTSS without close MSI Afterburner?
Only today i see problem: if i close RTSS - RTSS open again automatic
Unwinder
Moderator
Posts: 13728
Joined: 2000-09-05
Moderator
Posts: 13728
Joined: 2000-09-05
#5612447 Posted on: 12/01/2018 06:11 PM
I fail to understand that, why do you need to post "A lot of games didn't work with RTSS and this is another..." when it magically becomes "this is first game with problem for last 5-6 years. "??? That's not the best trick to attract developer's attention. Did you at least try to read what I posted? MSI AB spawns RTSS as soon as _you_ enable any functionality that requires RTSS service. It incudes, screen capture, framerate monitoring, OSD etc. Context help for _each_ of such features explicitly documents that RTSS will be loaded if you enable it. You can see full list of active RTSS-based client features in MSI AB info window. RTSS won't be closed until you have at least one RTSS-dependent option active in MSI AB. And no, you don't need to kill RTSS to exclude any application from being hooked, that's why profiles system and exclusion list exists.
I fail to understand that, why do you need to post "A lot of games didn't work with RTSS and this is another..." when it magically becomes "this is first game with problem for last 5-6 years. "??? That's not the best trick to attract developer's attention. Did you at least try to read what I posted? MSI AB spawns RTSS as soon as _you_ enable any functionality that requires RTSS service. It incudes, screen capture, framerate monitoring, OSD etc. Context help for _each_ of such features explicitly documents that RTSS will be loaded if you enable it. You can see full list of active RTSS-based client features in MSI AB info window. RTSS won't be closed until you have at least one RTSS-dependent option active in MSI AB. And no, you don't need to kill RTSS to exclude any application from being hooked, that's why profiles system and exclusion list exists.
safron
Junior Member
Posts: 2
Joined: 2018-12-02
Junior Member
Posts: 2
Joined: 2018-12-02
#5612575 Posted on: 12/02/2018 10:20 AM
does not work for X4: Foundations
does not work for X4: Foundations
Astyanax
Senior Member
Posts: 883
Joined: 2018-03-21
Senior Member
Posts: 883
Joined: 2018-03-21
#5612596 Posted on: 12/02/2018 12:26 PM
The black screen with RTSS is a Kepler driver bug, atleast thats the conclusion I came to talking to Unwinder previously about it.
Has anyone got a GTX 750 to rule out first gen maxwell? otherwise i'm following this up as a Kepler specific problem.
The black screen with RTSS is a Kepler driver bug, atleast thats the conclusion I came to talking to Unwinder previously about it.
Has anyone got a GTX 750 to rule out first gen maxwell? otherwise i'm following this up as a Kepler specific problem.
Unwinder
Moderator
Posts: 13728
Joined: 2000-09-05
Moderator
Posts: 13728
Joined: 2000-09-05
#5612668 Posted on: 12/02/2018 05:09 PM
The black screen with RTSS is a Kepler driver bug, atleast thats the conclusion I came to talking to Unwinder previously about it.
Has anyone got a GTX 750 to rule out first gen maxwell? otherwise i'm following this up as a Kepler specific problem.
Finally got old rusty Kepler based graphics card to reproduce it (GTX 650 Ti Boost). It is indeed looking like a bug in 4xx.xx drivers family on Kepler GPUs, the previous versions of drivers (e.g. 388.13) behave properly on this GPU family too. Vulkan 4xx.xx drivers on Kepler cause entire framebuffer content to be cleared by render pass when color attachment load operation is set to VK_ATTACHMENT_LOAD_OP_LOAD (i.e. valid previous framebuffer content is requested by application) and initial framebuffer layout for render pass is set to VK_IMAGE_LAYOUT_UNDEFINED.
Good thing: seeing this behavior it is really easy to add workaround for it from application side by adding one more memory barrier and changing initial layout for render pass. That's what I did in beta 3, it should work on Keplers now:
http://msi-afterburner.guru3d.com/RTSSSetup721Beta3.rar
The black screen with RTSS is a Kepler driver bug, atleast thats the conclusion I came to talking to Unwinder previously about it.
Has anyone got a GTX 750 to rule out first gen maxwell? otherwise i'm following this up as a Kepler specific problem.
Finally got old rusty Kepler based graphics card to reproduce it (GTX 650 Ti Boost). It is indeed looking like a bug in 4xx.xx drivers family on Kepler GPUs, the previous versions of drivers (e.g. 388.13) behave properly on this GPU family too. Vulkan 4xx.xx drivers on Kepler cause entire framebuffer content to be cleared by render pass when color attachment load operation is set to VK_ATTACHMENT_LOAD_OP_LOAD (i.e. valid previous framebuffer content is requested by application) and initial framebuffer layout for render pass is set to VK_IMAGE_LAYOUT_UNDEFINED.
Good thing: seeing this behavior it is really easy to add workaround for it from application side by adding one more memory barrier and changing initial layout for render pass. That's what I did in beta 3, it should work on Keplers now:
http://msi-afterburner.guru3d.com/RTSSSetup721Beta3.rar
Astyanax
Senior Member
Posts: 883
Joined: 2018-03-21
Senior Member
Posts: 883
Joined: 2018-03-21
#5612678 Posted on: 12/02/2018 05:33 PM
Nice, i'll forward this onto Manuel so the driver side can get fixed too.
Nice, i'll forward this onto Manuel so the driver side can get fixed too.
safron
Junior Member
Posts: 2
Joined: 2018-12-02
Junior Member
Posts: 2
Joined: 2018-12-02
#5612705 Posted on: 12/02/2018 06:54 PM
Thanks
It works.
Thanks
It works.2 pages 1 2
Post New Comment
Click here to post a comment for this file on the message forum.
Guru3D.com © 2019
Senior Member
Posts: 211
Joined: 2014-05-07
We just released a final build of RTSS (Rivatuner Statistics Server) build 7.2.0. RTSS is an integral part of tweaking tools like MSI AfterBurner and responsible for the overlay, video recording and s...
Download: Guru3D RTSS Rivatuner Statistics Server 7.2.0
Final build of Afterburner package with this RTSS when will be released?