Discussion in 'MSI AfterBurner Application Development Forum' started by Unwinder, Feb 20, 2017.
umm the new MSI AB Beta 10 is kinda broken
RTCore64.sys should have a digital signature by Micro Star (MSI) though, odd.
(Right click on file. -> Properties. -> Digital Signature and it should be listed there.)
EDIT: Perhaps an old version is still in the Windows driver repository folder?
(Unless I missed a version somewhere the file and signature dates should be May 28th 2017)
edit: nvm i fixed it
Focus group testing just got more interesting...
Rime has frame pacing issues?
Gsync kills them mostly though
disable digital signature
i got the same pop-up message though (RTcore64.sys) but MSI AB+RTSS worked just fine
Add a frame cap in that RTSS window of yours. Make sure the game hits it. The line in the graph should be quite flat after that
Can u saw us/me the RTSS Settings (Monitoring Tab)?!
I like tha style of that OSD Viewing.
Thanks a lot!
Doing that makes all BattleEye protected multiplayer games (pubg, arma) fail to open though... is Unwinder aware of this issue? And does anybody have the link to the previous beta?
There is no issue. Beta 10 is available for everyone for weeks here, in beta thread.
Had Beta 7 I think installed, went to install Beta 10 and had the same dialog as in the other user screenshot (RTcore64.sys not signed), using Test signing mode works, but as I said BattleEye does not like that.
I've tried doing a few complete uninstall and reinstall cycles but the dialog keeps appearing, the file in the AB folder is indeed signed but Win 10 seems to not care.
Will return to 4.3.0 and wait for new updates.
all MSI AB versions work fine it's just beta 10 that got me this problem
i'm on the latest update for windows10 ( 1 week old )
Did you install original beta 10 I provided here about a month ago?
i installed the one from guru3d front page but i'll give this one a try
this is working 100% no problems here
RTSS beta 24 is also installed
Damn, the installer on the front page is compiled and re-signed @ MSI from the same files, looks like code signing certificate is corrupted on their system.
Hilbert, can we remove that distributive from downloads until MSI compile correct one?