I'm not good with hints, haha. What do you mean by this? I feel really dumb for not figuring this one out. These are the settings I picked: And this is what is displayed in a game: Is there something I missed or was my installation botched?
To me looks the same if i can already monitor that stuff and i can see it onscreen, maybe it changes only the way it is done. If not, an explanation would be appreciated of the differences
I didn't see this mentioned but in 4.4.0 Beta 18 RTSS 7.0.0 Beta 29 the OSD isn't working for me in UPlay games, Ghost Recon Wildlands and Watch Dogs 2. It's working with all my other games including UWP games, GOW 4. It was working in Uplay games before this update. Don't know if the changes have affected Ubisoft's "cheat defenses".
Then your usage scenario is covering just 1% of functionality used by those who prefer to monitor the system at deeper level. The world is not rotating around just seeing some number in OSD in realtime for hardware reviewers or advanced users, seeing immediate state of hardware there doesn't let you to analyze monitoring history in post-realtime logs collected from multiple monitoring apps and synchronized in time. The main aims of pugins architecture are: - Providing user extendable architecture, allowing you to add any custom performance sources for your needs. Like this one. Existing HwInfo and AIDA plugins are just simple open source samples showing other plugin developers how to import some new data source into hardware monitoring module. - Providing unified hardware monitoring hub, allowing collecting data from unlimited number of independent sources, log it in one place, use unified OSD formatting layout for it regardless of application supplying the data, send it to iOS/Android client applications in unified way.
Oh it's part of that. Thanks. Well since I refuse to play a game where my AB/RTSS OSD isn't working (or use a GPU I used to have where AB isn't fully functional) I guess I'll just go back to Project Cars 2, etc.
Alright, that seems to work. Thanks! I remember I used to be able to change the color through Rivatuner though. When did this change happen?
Thx for explanation and yes, for me suffice to see if my temps are fine and if clocks work as intended during gaming. This a bit too complicated for me @@
You may switch to "classic" (old one) or "modern mono" layout so entire OSD color will be monochrome and defined by RTSS color settings. For new "modern" layout parts of OSD can be additionally colored from MSI AB side. All that can be customized in layout editor.
Guys, what do you need to change in MSi so that I can have 3 graphics like in the top picture of the article? I can only seem to have only 1 graph undernearth the main window.
Is winamp milkdrop OST not detected anymore in win10 rs2? Dxtory or fraps still works. I see now milkdrop2 uses another nv.dll (nvldumd.dll), could this be the cause?
No ideas, never used it and don't plan to Are you sure that the application is NOT into OSD exclusions list?
Ok, will have a look. Thanks EDIT: ahh, I feel so stupid, I checked pre-created profiles and by winamp it was detection level: none, I've set it to low and it showed right away.. lol
IMHO nothing better than AB/RTSS fine OSD while gaming to tell you how your hardware is performing. Come to think of it why don't all Hilbert's fine gaming graphic performance reviews include OSD game video? . If a picture says 1,000 words, an AB OSD game video says a million words.