MSI Afterburner 4.3.0 Final is Released

Yes I saw, but The Divison or GRAW WildLands don't use it.



EDIT: by The Division it was like so, I updated to 6.6 beta5? and it worked, then after restart it didnt anymore, then while ingame I changed from raster back to vector and from framebuffer to viewpoint and it worked again, on 3rd reboot it didnt work anymore.
edit2: If it matters I had that steam overlay workaround enabled, I have steam version with both steam and uplay overlay.

By GRAW Wildlands just uplay, after I overwrite back to 6.5 it started working again.



But I saw you added that 15sec overlay delay, that looked great :nerd:

 

It's still common. He'd have to add an addition function to determine the current install location. It's only an issue for those doing a custom install right?

 

Veeeeeeeery interesting. You've found a way to make OSD work with UWP?

 

awesome!!!

 

What am I looking for in the screenshop?

 

It's a UWP / Win10 "app" in this case I think it's one of the Forza games, in any case Afterburner couldn't monitor this type of software before so it's nice to see it supported even if it's probably going to be a while before 6.7.0 sees a release.
(Those two Forza games, ReCore, Gears of War 4, Dead Rising 4, Quantum Break, Halo Wars 2 and various indie or other smaller games and probably some I forgot.)

EDIT: Well couldn't and couldn't, screenshots and I guess recording worked far as I tested but the OSD didn't show up.


EDIT: Heh I made this way more complicated than it had to be now that I'm re-reading this.

Basically OSD support for Windows 10 UWP "WinStore" apps in addition to the existing Win32(and x64) support.
(Forgot exactly what Microsoft called these, they have some name for this type of software or at least a development name or code name.)

 

Ahh I get it. Thanks.

 

RTSS in UWA

It's interesting because I have been using OSD during benching and gaming for many years now (since it was invented) and can't feel right about doing it any more without it. It sucks that it did not work in UWA games.

However, it's also kind of sad if that gets fixed because UWA filth needs to die and OSD not working was just one of the excellent reasons it needs to go bye-bye. Losing a reason for it to fail/die is not a positive thing. It was a positive thing that OSD being broken diminished my experience with UWA games... helps keep the fires of hate burning, LOL.

 

Can you be in contact with BattlEye developers too for future updates?

Thanks for updated.

 

I sent a request.

 

Check your PMs.

 

Thank you Bastian :supercool

 

EDIT: Nevermind.

 

installed RTSS 6.6.0 over the 6.5.0 and it seems that it doesn't work as i wanted ( no OSD toggle )


i'll remove MSI AB + RTSS and install them again fresh

edit:

turns out removing both >restart>install RTSS 6.6.0 1st then AB fix the problem

 

For me when it comes to updating Riva Tuner Statistics Server I've noticed that occasionally RTSSHooks64.dll will still be in use by some system process, usually application frame host.exe or the windows shell experience host .exe

Still haven't found a good way to replicate how or when this occurs, I'm thinking it's more of a local issue with my current Win10 system as if it was a issue with Win10 in general everyone would have encountered it, in any case it's probably not very common.
(But it also makes it difficult to figure out the exact cause behind why this happens or at least for me as somewhat of a amateur on how this all works or how to say.)

To resolve this I used to log out and then log in again but there's a quicker way, make sure Afterburner / RTSS is shut down and then bring up the task manager and shut down shell experience host, it'll pop up of it's own again in a few seconds (Refreshes the Win10 start menu too.) and then do the same for application frame host, whenever you next start a app be it some Win10 game or just the store or settings software said process will start as well.

Just to be sure I also restart explorer.exe, doesn't hurt to make sure the entire shell is unloaded far as I see it even if it might not be needed.

After that I delete RTSS64.dll to make sure it's currently not in use by anything (If it is a error prompt will appear showing which software it's currently used by which is how I narrowed it down to those two in the first place.) and then I install the new version of Afterburner or well in this case just the separate Rivatuner software.

If you want you can also rename the profiles folder or just the files "global" and "config" if you want a clean config though I usually don't do it unless there's been some major changes.
(Profiles folder for the user made profiles and settings, not the ProfileTemplates folder, full uninstall before installing the new version also works if you want to be thorough.)

Might be overkill and generally upon finalizing the installation RTSS will prompt for a reboot if it couldn't replace a file which will then be handled upon boot when it'll no longer be in use by the system.

So if said prompt doesn't come up the install should have finished without error though a reboot can't hurt to ensure everything is clean and nothing is residing in memory or is in use by either the OS or other third party software.


EDIT: Seeing how these are both .exe files I also tested adding profiles for ApplicationFrameHost.exe.cfg and sihost.exe.cfg but nope, just setting "EnableHooking=0" wasn't enough.
(Further hinting at it being a system issue I'd guess, not that I can say for sure but RTSS shouldn't try to inject into these with hooking disabled from my understanding of how this works.)