Discussion in 'MSI AfterBurner Application Development Forum' started by Unwinder, Feb 20, 2017.
Buildzoid? Hell no I won't even watch the review. That fella hate ASRock & can't be trusted.
Thats delusional lol
oh great news ali you are always the guy I want to see with a card first.
looking good so far cant wait to utilize ab with this series
I spent whole weekend playing with NVIDIA Scanner integration in MSI Afterburner so I have some interesting observations to share with you. All the facts I’ll post are rather generic things (still useful for reviewers), which don’t seem to be covered by NDA, so I hope that green rays of love from California won’t burn me alive
- NVIDIA’s Scanner API is purely 64-bit only. Which means that in order to support it we would also either need to start releasing both 32-bit and 64-bit branches of MSI Afterburner or make MSI Afterburner pure 64-bit application only (and this way drop support for 32-bit OS’es and leave huge part of user base without updates, which makes me absolutely unhappy because I do my all to keep backward compatibility and still provide support for ancient Window XP OS and 10 years old GPUs starting from GeForce 6 or newer and RADEON HD 2000). As a compromise solution, our implementation is an independent 64-bit MSI OC Scanner application bundled with MSI Afterburner and communicating with it via MACM shared memory interface. Such modular architecture will allow us to update scanner independently of MSI Afterburner in future as well as let us to provide OC scanner component’s source code to GPU vendors for their internal tests.
- It was declared by NV that scanner API is using embedded NVIDIA tests for stressing GPU and testing overclocking stability. It is closed proprietary technology, so it is not clear now how much hardware dependent is the implementation, it is quite possible that it will work exclusively on RTX 20x0 series only.
- OC Scanner will provide you two main modes: test and scan. In test mode your manually configured voltage/frequency curve is being stress-tested, result is returned as GPU stability confidence level in % (0% - unstable, 100% - stable). I’ve never seen 100% result even on stock clocks BTW, it always seem to max on 90% on all cards we tried so probably it is just a precaution from NV side, no need to worry if you see <100% result. In scan mode scanner’s proprietary algorithms are trying to detect the maximum stable overclocking achieved by your GPU, result is returned as average core clock overclocking in MHz. Modified overclocked non-linear voltage/frequency curve is also sent to MSI Afterburner by scanner in the end of scanning process. Test mode takes approximately 5 minutes to complete, scan mode takes 15-20 minutes to complete.
- It is very convenient to keep voltage/frequency curve editor window open while the scanner is running. V/F curve editor is showing you current GPU clock and voltage levels with horizontal/vertical dotted lines directly on the curve in real time (2070MHz / 975mV on the previous screenshot). This way you can visually control the process of scanning, so you always know which point of voltage/frequency curve is currently being tested or overclocked. In scan mode it doesn’t try to overclock each point independently, as it would take much more time than just 20 minutes. Instead of doing so, it is detecting working range of voltages on the first stage, split this voltage range on a few fixed parts (4 key points on the screenshot above) then try to find the maximum possible overclock for each of those key points by fixing the voltage in each point and slowly increasing the clock until instability is detected. You can see this process on the previous screenshot as well on jigsaw core clock graph. Each tooth of this jigsaw is the process of finding the maximum possible clock for each of 4 key points. Once the maximum stable overclocking is detected in each key point, the scanner is building whole curve by linear interpolation between the points and sending result to MSI Afterburner.
Do you see possible AMD releasing something similar?
Why not? Both AMD and NVIDIA were experimenting with different forms of automatic overclocking and maximum stable overclocking detection about two decades or so.
Does the API also OC memory or it is just core?
I doubt this will work on older cards, well maybe 10xx but my guess that would be it.
The thing with AMD or Nvidia doing auto OC they need to make sure there enough headroom to make it worthwhile, or marketing wise it not worth it IMO.
Just core. But I believe that test mode also check current memory clock stability.
Ok, Sounds interesting I will be checking on reviews of how this works for such a short test runtime.
Also how dot hey handle TDP, that IMO would be big limiter as if I remember they said something along the lines 2080 was 180-200w (I can't remember #, but pretty sure was mention at launch)
Overclocked V/F curve is detected by scanner for currently set overvoltage, power and thermal limits. Once you change one of those parameters, you'll need to rescan.
I see, thanks for the info.
I played FORZA HORIZON 4 DEMO the OSD was working, but with screenshots, the game crashed.....
I used MSI AB 188.8.131.5219.
Now I'll update BETA5, and I'll try.
My English is poor，So sorry
MSI AB doesn't support screenshotting for UWP apps.
I see. Thank you for your reply.
Shadow of the Tomb Raider crashes with RTSS enabled on DX12.
399.24 / Win 10 latest
Cannot confirm that, works fine. No need to continue that in development thread please.
Yes, you're right, it was the Fast Sync. As soon as I changed it, game started booting again.
You could literally have figured out that it was not RTSS by simply closing MSI AB (which closes RTSS) then trying to start the game.
Asrock's firmware engineers aren't the best, makes the product less than stellar.
If buildzoid says theres an issue with asrock boards for any reason, prick your ears up and listen, don't stick your head in the sand and be one of those "well we told you so" victims.
I'm not your dog or the fella's dog. There's issue with every boards, but the fella skipped it. I don't wish to argue with daug.