MSI AfterBurner Overclock Application Discussion forum This forum is intended for MSI customers for questions on the AfterBurner Overclock Utility based off Rivatuner. In this section the users help each other out with answers as well as support staff from MSI.

- RTSS must be started before an UWP 3D application to provide automatic injection and On-Screen Display rendering. However, you can optionally define “Show On-Screen Display” hotkey in RTSS client applications (i.e. MSI Afterburner) and manually inject any running UWP application via pressing this hotkey even if you start RTSS during UWP application runtime.
- Currently the following UWP titles are supported officially: Gears of War 4, Gears of War Ultimate Edition, Forza Horizon 3 (please read notes below), Forza Motorsport 6: Apex (please read notes below), Minecraft Windows 10 Edition, ReCore, Ori and the Blind Forrest Definitive Edition. Other UWP titles were not tested at all, but may also work.
- Currently Forza series games may hang on startup if OSD is displayed during loading the game. To prevent that, RTSS includes application specific profiles for both Forza Horizon 3 and Forza Motorsport 6: Apex applications and disables automatic injection and OSD rendering for it. However, you may safely manually display the OSD in Forza series games via pressing “Show On-Screen Display” hotkey, but it is strongly recommended to do so after Forza Horizon 3 or Forza Motorsport 6: Apex finish loading into the main menu.

Halo Wars DE: doesn't work at all, no OSD, no fps/frametime data in AB.

Halo Wars 2: https://abload.de/img/2017-02-2020_00_10-grn8op3.jpg
Some issues on startup, possibly the same as in Forza games - the game crashes at campaign start once all the videos have played if the OSD is (or was at some point between game's launch and campaign start) enabled. If you wait till all videos have played and the actual level have loaded and you have control - then OSD turns on just fine. No idea if the game crashes anywhere further after playing some video though.

Will check GearsUE and UWP version of Quantum Break in a couple of hours.

Halo Wars DE: doesn't work at all, no OSD, no fps/frametime data in AB.

Halo Wars 2: https://abload.de/img/2017-02-2020_00_10-grn8op3.jpg
Some issues on startup, possibly the same as in Forza games - the game crashes at campaign start once all the videos have played if the OSD is (or was at some point between game's launch and campaign start) enabled. If you wait till all videos have played and the actual level have loaded and you have control - then OSD turns on just fine. No idea if the game crashes anywhere further after playing some video though.

Heh, it looks like this evil UWP development gonna cost me additional $50 to purchase Halo Wars 2 Ultimate Edition. I'll buy it and peek inside.
If HW2 crash on startup issue is indeed having the same roots as Forza, then it can be temporarily bypassed with similar application profile, simply create new profile template for it and copy forza_x64_release_final.exe.cfg/ForzaMotorsportApex.exe.cfg (both can be found in ProfileTemplates subfolder).

That's normal and expected behavior for applications using partial frame buffer updates (most frequently that applies to letterbox'ed widescreen applications with static black bars ot top/bottom). OSD is being rendered on top of the application's frame, if the game is not erasing those areas on each frame - you'll see exactly the same overlapping OSD text. It can be fixed by moving OSD down to refreshable parts of framebuffer.

Quote:

Originally Posted by dr_rus

Out of all games checked Halo Wars DE is the only one using DX11 - might be why it's not detected?

Nope, Minecraft W10 edition and Ori and the Blind Forest Definitive Edition, which I mentioned above, are DX11 as well and working fine. I'd say it is something specific to that game engine implementation.

Got both Halo Wars DE and Halo Wars 2 installed. Issue with missing OSD in Halo Wars DE is reproduced and fixed, new beta with Halo Wars DE support will be uploaded today in the evening. However, I cannot reproduce any crashes in Halo Wars 2.

Heh, it looks like this evil UWP development gonna cost me additional $50 to purchase Halo Wars 2 Ultimate Edition. I'll buy it and peek inside.
If HW2 crash on startup issue is indeed having the same roots as Forza, then it can be temporarily bypassed with similar application profile, simply create new profile template for it and copy forza_x64_release_final.exe.cfg/ForzaMotorsportApex.exe.cfg (both can be found in ProfileTemplates subfolder).

Tried this, still crashes if the OSD is enabled before the level is loaded and the intro video has played. So probably some other issue.

Quote:

Originally Posted by Unwinder

Got both Halo Wars DE and Halo Wars 2 installed. Issue with missing OSD in Halo Wars DE is reproduced and fixed, new beta with Halo Wars DE support will be uploaded today in the evening. However, I cannot reproduce any crashes in Halo Wars 2.

1. Launch AB
2. Launch HW2
3. Turn the OSD on with a button (if it wasn't on)
4. Start a new campaign, skip the tutorial (will skip automatically if you've played it once), skip the intro video, let it load the first map of the campaign (The Signal).
5. Click "continue", the video at the first level starts playing and right after that video (you can watch it or skip it, doesn't matter) the game crashes even if the OSD is turned off with a button again.

It doesn't crash if AB is not loaded or the OSD wasn't enabled between game's launch and this point. 100% reproducible here.

Just tried something different: restarting the mission after loading and enabling OSD after that leads to the same crash on mission start.

This is a game+driver issue as stated in the release notes, nothing to do with AB or RTSS.

The problem I said it only happens when Riva Tuner is on. If it's off it works properly. That problem already happened some months ago. It's not a driver problem because I've unistalled and installed last version drivers in the last months and the problem was still there.

I repeat once again that I cannot confirm it and I'm not working on solution. But if you believe that it is RTSS issue and hope that it will be resolved with new version, let it be so. I'm just informing that no fix is coming from my side. Please avoid discussing it in this thread, it is intended for testing new UWP functionality.

I think I fixed hang on startup related issues with Forza Horizon 3 and Forza Motorsport 6: Apex. Most likely beta 2 with these changes and with OSD support for Halo Wars Definitive Edition will be uploaded tomorrow.

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.

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.

I still couldn't reproduce crashes in Halo Wars 2 with OSD enabled, but I tried to create a profile for Halo Wars 2 with tweaks similar to what I've done with Forza series games. So please try Halo Wars 2 to see if it works better now for you.

I still couldn't reproduce crashes in Halo Wars 2 with OSD enabled, but I tried to create a profile for Halo Wars 2 with tweaks similar to what I've done with Forza series games. So please try Halo Wars 2 to see if it works better now for you.

I'm doing Halo Wars 2 extensive testing with RTSS beta 2, so far:

- it still crashes almost instantly after the map loads (skirmish, see below) when you start RTSS before Halo Wars 2

- Enabling RTSS after i load a map - gives random crashes (no error message, nothing, game just closes), sometimes as soon as few minutes in, sometimes like 20-30 minutes after but it always happen.

It seems to happen faster if i leave RTSS enabled, if i show it / hide it (via shortcut in afterburner) it seems to crash later. This needs additional testing, which im doing now.