New features of RTSS - more flexible Reflex data sources, PresentMon V2 integration

This video demonstrates the following new features of RTSS : - Customizable Reflex data sources. Fixed set of Reflex latency/timespan data sources was available before, now you may use new reflexlatency/reflextimespan formulas inside your custom Reflex related data sources to calculate latencies between two arbitrary Reflex markers. I demonstrate it by changing yellow Reflex “Simulation“ timeband to “Simulation-to-Render-Submit“ timeband. Initially it is a latency between simulation_start [1] and simulation_end [2] markers, I change it to simulation_start [1] and rendersubmit_end [4] - New PresentMon V2 overlay layout. With PresentMon V2 Intel changed their frametime sampling approach from Present-to-Present to Start-to-Start. Modified PresentMon V2 overlay layout allows you to see both old Present-to-Present and new Start-to-Start frametimes and dynamically switch between them with “F“ key. That’s what I demonstrate a few times next. - When I press “F“ to switch between frametime sampling modes, you may observe two nearby orange spikes on the graph per each key press (please remember that PresentMon’s data is delayed by approximately 3 seconds, this delay is reflected as “Reporting lag“ in overlay). This orange graph is new PresentMon’s ClickToPhotonLatency metric. Those two nearby spikes are key press and release events for each key press. - Now I move mouse around to see mouse activity related “jigsaw“ on ClickToPhotonLatency. - Then I press and hold “D“ button so you can see one more “jigsaw“, which is reflecting automatic repeating key press event from keyboard - As you see, ClickToPhotonLatency is not static so it makes no sense to display absolute value for it. Instead of that, this overlay layout calculates and displays average value for it. I show that I do it with swavg(x,512) function, which is calculating average value for “S“liding “W“indow containing the last 512 ClickToPhotonLatency samples - And finally, I show you how do I implement overlay transformation with keyboard events to switch between Present-To-Present and Start-to-Start frametime sampling modes. I added IsPresentToPresent data source, which checks if “F“ key press counter is even/odd. Then I simply display frametime either as msBetweenPresents (PresentMon V1 present-to-present metric) or as CPUFrametime (PresentMon V2 start-to-start metric)