MSI AB / RTSS development news thread

Hello everyone, I currently have an issue with sync scanline, I use it for a few days now and I tried different settings. I play mostly CS: GO on a XL2420T lightboost 10% with 1149 lines.
Here are my settings (found on the internet) for the game to know that I play in 1280 * 960
Limit = 121
LimitDenominator = 1
LimitTime = 0
SyncDisplay = 0
SyncFlush = 1
SyncHotkeys = 1
SyncScanline0 = -180
SyncScanline1 = 0
SyncTimeout = 2
SyncPeriods = 0

These settings give me regular image tearing. What values should I change to have a smooth game with sync timeout = 2? Thanks for enlightening me, have a nice day

 

Awesome Any sneak peek?

 

Looks amazing

 

I agree, it looks great as it is

 

Ooh, that's very neat! Thank you!

 

Curious about one thing, would it affect the CPU when minimized in the systray? Or this is just a thing for when the app is not hidden?

 

Thanks for the explanation. Got home and tested it, and the CPU usage with the window active is very, very small, typically below 1% on a 8700K that idles around 800MHz.

 

Working great and really like @Drerex skin work, been a fan of his for years.

 

just played RAGE 2 and noticed RTSS osd doesn't work , any tips ?!

 

API wise the game uses Vulkan though that's about the only advice I can give directly but I'd try the compatibility settings for that first, maybe also try windowed and borderless modes and restarting the game once or twice to see if that hooks.
From that to trying the 2D and 3D OSD compatibility options (NVIDIA GPU so AMD's little performance problem with 2D shouldn't be a issue here.) other than possibly being one of the first projects on VLK 1.1 instead of 1.0 SDK it should be workable with some tweaking and ensuring no other hooks are applied such as Steam (Rename the overlay .dll for 64-bit to get it out entirely as a test.), GeForce Experience and such.

You can use these overlays too but to begin with I'd minimize it to where it's RTSS and only RTSS ensure that works and then start adding in Steam, GFE and what else.
Minimize possible compatibility issues and build from that.

EDIT: I'd throw out the Steam overlay first if nothing else in RTSS or the window modes do it (Don't merely disable it in the client, it hides it but still injects. Thus rename the .DLL to get it out entirely.) and if that helps and then maybe try a delayed injection to see how that goes. (The overlay is used for various things so it's not merely screen captures or recording or achievement notifications so you probably don't want it entirely removed if that can be resolved.)

EDIT: And probably only hooking VLK and having the hooks for D3D off as well from RTSS so there's no problems with D3D being initialized and then here's VLK but it tries going through D3D so that's why you would disable those hooks when you know what API the game is using for the RTSS profile for RAGE2 here.


Explanation being a bit of a mess but minimizing potential conflicts and problems by hooking the API it's using but none of the others and if needed also try reducing or removing other hooks from for example overlays such as the Steam client itself, drivers and what else there might be and then there's a plethora of different RTSS settings and compatibility options for tuning it to hopefully be compatible while keeping everything active and loaded without any crashes or problems.

Nothing really new, just a bit of trial and error and testing to what works and going from that.


EDIT: And with a lot of compatibility options yeah it can take a while to work out the proper way to set it all up there's just a ton of variables and conditions and seeing what works and when it breaks and getting it all in order.

It might even have hooked properly but it's just not showing the OSD but related functionality could still work.