MSI AB / RTSS development news thread

You can add any application to exclusions list via add profile for this application and setting application detection level to "none". With 7.0.0 the process of adding exclusion can be simplified by holding <Shift> and clicking <Add profile> in RTSS while desired 3D application is running. In this case RTSS will detect all currently running 3D applications and allow you to select and add some (or all) of them to exclusions list.

 

UWP applications are still wrapped into regular EXEs, for Paint 3D it is "PaintStudio.View.exe" located in "Program files\WindowsApps".

 

I absolutely love such kind of smart posts from search haters and forum newbies. Instead of such suggestions, why don't you stay in the forum for a while and simply start answering the questions yourself daily instead of claiming that author is lazy? But that won't happen.

I also cannot expect much from a guy who come to free software forum, clone exactly the same question right after posting with solution then try to talk this way instead of apologizing. Please leave this thread and forum.

 

Not a problem, it is really easy to save you from that widely known fact, from my laziness and hostility.
I have a better solution: I did an exception with this beta and tried to return development to open development/beta testing model. That seem to be failed so we're returning back to private beta forum, no more public frequent betas for everyone, all development will be in private forum like it was before. 3 last posters may be proud of yourself, you make the forum cleaner.

 

One more attempt to leave betas in public domain. The thread is open again, but it will be moderated more strictly now, everything that I find offtopic and derailing the development will be silently removed from this thread without any useless dialogs with user. So those don’t use search and like to post to the thread without reading the previous posts are warned.

RTSS 7.0.0 beta 20 is online:

http://office.guru3d.com/afterburner/RTSSSetup700Beta20.rar

- More flexible raster font size adjustment. Now base raster font size (i.e. size for 1x zooming ratio) can be adjusted directly in font selection dialog.
- Added frametime history graph overlay. The overlay can be enabled in RTSS properties in FCAT settings group (“Enable frametime history overlay” option). Frametime history graph dimensions (512x100 pixels, 50ms max, 0ms min) are currently hardcoded in global profile template so power users can alter them there. The graph is currently attached to the bottom of OSD text.
- Fixed Vulkan sampler cleanup, which caused Vulkan OSD text to look pixilated in modern OSD layout when 3D application dynamically recreated Vulkan device.
- Added explicit multi-GPU support to pure D3D12 renderer (currently used in Halo Wars 2 only). So now D3D12 overlay in HW2 should work on SLI/CF systems as well.
- Framerate limit in GUI has been increased to 300 FPS.
- Screenshot/video encoding libraries (SaveMedia.dll/SaveMedia64.dll) and video encoder plugins are now also digitally signed.
- Added more exclusions to built-in profiles list (Paint 3D / 3D View, Unigine Superposition launcher ).

New frametime history overlay usage is demonstrated in this video:

 

Yes, I checked it but I cannot reproduce it here. It is correctly displayed as 60 with VSync on here. However, the game is indeed internally limited by 120FPS without VSync. So the question is: are you sure that VSync is working?

 

After reading some discussions in BlurBusters forums I'm rather surprised to see that a lot of users seem to misunderstand the basic principles of framerate averaging, OSD refresh period adjustment, different frametime display modes etc.
So I decided to add a some options to GUI (context help included) to let you to play with them and see how they affect displayed framerate and frametimes. New GUI options include the following:


o Added new “Framerate averaging interval” option to “General” tab. You may use this option to adjust framerate calculation and to see immediate framerate instead of smoothed if necessary
o Added new “Refresh period” option to “General” tab. You may use this option to adjust the refresh period for framerate and frametime counters and update them on each frame if necessary
o Added new “Display integer framerate” option to “General” tab. You may use this option to switch between integer and floating point framerate representation format
o Added new “Display maximum frametime” option to “General” tab. You may use this option to switch between immediate current frametime value or maximum frametime value during each refresh period. Maximum frametime value can be used for framerate stutters detection


Also now frametime is displayed next to framerate if you enable "Show own statistics" in RTSS, display frametime histoty graph and use RTSS as standalone framerate monitor application.

Grab RTSS 7.0.0 beta 21 here:

http://office.guru3d.com/afterburner/RTSSSetup700Beta21.rar

 

Correct, new options are related to framerate/frametime display only. They do not affect framerate limiting at all.

 

Comparing frametimes at 3D-application level (i.e. measuring them with FRAPS, RTSS or anything else) and display hardware level is not the best idea as well, that's like comparing apples to oranges, they are fundamentally different and won't match. That's exactly why NVIDIA introduced FCAT approach. I'd recommend that user to research what is FCAT, why it was introduced by NVIDIA, why frametimes are different in graphics pipeline input and output, what are runt and dropped frames and they are indivisible at 3D application level but exist in the end of pipeline.