Dear forum visitors, Two things I'd like to note. First, I won't directly comment the thread @ reddit (linked in the previous post) about Vulkan OSD in DOOM because some AMD fanboys (including our local LocoDiceGR who post under valantismp there) already crapped and derailed it, so discussion is flooded by trolls with false rumors about it as a part of GPP, about shady MSI tactics or about "crappy MSI AB hammering CPUs". But I'll gladly refresh memory of our forum readers and remind that DOOM Vulkan OSD rendering specifics on AMD GPUs and higher than normal overlay related performance hit on such systems were documented in details since day one when we released Vulkan OSD support for this game on AMD graphics cards: "Vulkan OSD should now work properly in Vulkan applications when frames are being presented from non-graphics queue. The only currently existing Vulkan application behaving this way is DOOM (only on AMD graphics cards), because it is asynchronously presenting frames form async compute queue in AMD codepath. Such presentation implementation makes Vulkan OSD rendering rather expensive in performance hit terms, because it requires forcible graphics and async compute queues synchronization. So now rendering OSD in DOOM/Vulkan on AMD cards may reduce performance by approximately 5% (the same applies to Steam FPS counter in DOOM/Vulkan on AMD), but I believe that there is some space left for optimization and it can be improved in future versions." Second, my apologies on delaying 4.5.0 release a bit. Sadly I'm having some issues in my real life now, so currently I cannot invest too much time into MSI AB. We planned to release 4.5.0 right after Win10 Spring Creators Update but it is delated due to issues I mentioned above. I hope that I'll have a bit more free time on the next week so I'll be able to post 4.5.0 RC in this thread, then we'll put MSI AB 4.5.0 and RTSS 7.1.0 in Guru3D downloads and make them visible to update servers. It won't be much different to previously posted 4.5.0 beta 5, just some minor GUI fixes and one new feature: - Fixed invisible hardware monitoring selection in hardware monitoring log viewer - Plugin specific hardware monitoring graph names are localized properly in hardware monitoring log viewer - Hardware monitoring correction formulas are more powerful now, now you can use values from sibling hardware monitoring graphs in formulas. For example, you may define x - "RAM usage" correction formula for Pagefile usage (Commit charge) to subtract current RAM usage from this value.