Add a UWP exclusion to MSI Afterburner's OSD

   Information

First of all, thanks to Unwinder for assisting me with this tutorial.

Dude and I noticed recently that since Unwinder(the developer of Afterburner) added support for UWP games and apps, it tends to show up, unwanted, on some apps.
I noticed he hasn't added profiles in RTSS(Riva Tuner Statistics Server)for every Windows 10 app***(see note at bottom of the tutorial), and why should he? He has given us the ability to do it ourselves(and much, much more).

To see what I mean, here is an example with the Camera app:



In one of his posts, he gave a brief explanation on how to do it, but it took me a while to figure out how to do it and what to copy and paste(in the tutorial below), and I thought I might as well post how to do it, to help my fellow Afterburner fans.

CONTENTS:

• Option One: The Easiest Way
• Option Two: The Easy Way
• Option Three: The long Way

 Preparation for Adding an OSD Exclusion

When you find a UWP app that shows the OSD, when it shouldn't, open RTSS by going into Afterburner's properties(gear icon)> On-Screen Display tab> and click the "More" button at the bottom:





You will see this:

Option One

The Easiest Way

   Information

This creates an "exclusion" and you won't need to manually disable OSD or application detection level for new profiles

1. When you open a UWP app, and the Afterburner(RTSS) OSD is displayed, open up RTSS as shown above.
2. Hold the <Shift> on your keyboard, and click the "Add" button(green button on the bottom left of RTSS).An "Add exclusion" window will be displayed.
3. Select only the app you want excluded.
4. Click OK
   

Close RTSS and restart your UWP app.
The OSD should be gone

Option Two

The Easy Way

   Information

This creates a profile, and you can turn off OSD this way or use the profile quick adjustments for UWP games and apps

1. When you open a UWP app, and the Afterburner(RTSS) OSD is displayed, open up RTSS as shown above.
   
2. While holding your keyboard's <CTRL>(control) key, click the Add button.
   
3. An "Add profile" window will open up.
   
4. Make sure only the UWP app is selected.
   
5. Then click OK.

After you have added the profile,
turn off the "On-Screen Display support" button.


Close RTSS and restart your UWP app.
The OSD should now be gone:)

Option Three

The Long Way

While the UWP app is still open, click the "I"(information) icon on Afterburner:


It will open the Information window.
Scroll down to the bottom where it say's On-Screen Display Server.
Where it say's Active 3D process,
find the UWP app, highlight ONLY the executable(not the whole line description),
then right-click and copy it:


Now go to the opened RTSS window, and click Add(bottom left), and paste the .exe into the System32 "open selection window" that opens:



Then where it say's "Application detection level" click "None" which will turn off the OSD in your UWP app:


Restart your UWP app and the OSD should be gone:


It's actually that "easy", and now you don't have to either be nerved, or turn of OSD to use your UWP apps.
And if you play UWP games, you might want the OSD there for some games(not sure about Candy Crush though)

   Tip

In my screenshot, you can see some of the app executables I have found.
Here is a list you can just copy(click each one 3 times fast to select it) & paste them into RTSS Add, so you will not have to open each app to find the executables.
If anyone finds any more, let me know, so I can add them to the list, please:

Code:

3DViewer.exe
Builder3D.exe
Maps.exe
Print3D.exe
WindowsCamera.exe

   Note

Unwinder has added the first 5 apps as exclusions in Afterburner's finale version(4.4.0), so if you are running it, you do not need to add them again(they can be found by going into RTSS>setup and deselect "Hide pre-created profiles")

Additional Link: Latest MSI Afterburner Betas & Updates ​

Great job Cliff

Dude said:

Great job Cliff

Thanks Doug, just let me know if you can do it, following the tutorial, when you've had a chance to try.

It took me a while(an hour or so, but for me that's an eternity) to figure it out, and I generally pick up stuff like this pretty quick, but Unwinder' s thread is not there for tutorials, so he generally just quickly brushes over new changes, and lets the users find out how to use the neat stuff.
Which makes sense, as he only does this on weekends it seems.

It works Cliff, I just removed maps and confirmed.

Dude said:

It works Cliff, I just removed maps and confirmed.

Great, hopefully it'll help others too:)

That with the OSD showing up where it shouldn't was really bugging me, so today i did some serious scanning through the RTSS beta thread at the GURU of 3D Afterburner forums just to find his post:

Sandboxed UWP process is still wrapped into regular EXE. If you click <I> button in MSI AB while some hooked UWP game is running, it will show the name of UWP executable in "Active 3D process" line. You can use this name for application-specific profile creation.
BTW, due to RTSS shared memory layout improvements (listed in the first posting) MSI AB 4.3.1 will also display "x64" and "UWP" flags next to each listed 3D process.

RTSS 6.7.0 beta 1 | Page 2 | guru3D Forums

And from there it was trial and error.

Then I thought if I had a hard time, I can imagine what it will be like for others, so I made the tutorial.

Archie123 said:

Nice post trying now :) . It seems i cant give you any rep because i have to "spread some around first"? anyway nice tutorial fella

Thanks Archie123:)(Darren)

Unwinder said:

>*Adding an OSD Exclusion

There is much more simple way to add profiles and exclusions in RTSS 7.0.0. When desired UWP (or Win32) application is running you may hold <Ctrl> when clicking <Add profile> button in RTSS to add a profile for currently active 3D application or hold <Shift> to add an exclusion for currently active 3D application (i.e. add a profile and automatically set application detection level to <None> for it).

Ahhh, I get it, and then a selection box pops up:)
I'll add it as an option above when I get a chance.

Welcome to 10 Forums @Unwinder, I love all the changes and additions you have added to Afterburner in the last year(specially Modern Web OSD).

Thanks for all your hard work.

We are always excited about new versions here.

The OSD is important to me, because when I run benchmarks I can see what causes instability, then adjust accordingly, to get the highest, but most stabile OC possible.