MSI AB / RTSS development news thread

I believe how social media algorithms work is, any attention from you or action by you (positive or negative) will bump the content.

That means that if you don't wish to support some content or content creator at all, all you can do is avoid clicking, reading, watching or reacting to the content altogether. Trying to work against them actively does the opposite: by getting worked up enough to "dislike" shows the algorithm that you care, which means the content is worth something for the platform in the form of more views, comments and reactions (collectively: engagement).

This is also why YouTubers say to "remember to comment, like, dislike" in their videos and they actually mean it; Each action will promote the video.

(And sorry about the offtopic. I'll stop now.)

 

Ive found an annoying bug in MSI AB with custom clock curves, which is present for a while, isnt fixed in latest beta. I have saved a custom clock curve to undervolt my GPU with it. The bug is, that it randomly gets altered (shifted) on the flat curve I have set in the back area, with high chance when starting AB.

I am noticing this, because I am monitoring vcore in games via RTSS. Whenever I see, the vcore isnt the desired 0.875V at max boost, I toggle out into AB, press ctrl+F and see, the curve is altered. I then toggle back and forth several times the profiles, until checking ctrl+F and the curve is the one I desire, change back into game, and it is working again.

This is my custom curve:


And this randomly happens:


Clicking the profile and apply doesnt work most of the time. The broken curve still stays. Doing it a bit back and forth and somewhen it is working again and checking vcore also is correct 0.875V in game with RTSS.

It would also be nice, if you could export curve profiles into a file you can import again easily.

 

I think that isn’t a Bug from Afterburner but more a NVAPI thing.

 

I do it as you sad and it works perfectly. As F@H User I must say, that the OC Scanner Curve is really good. For Benchmarks or Games, I can set a little more OC but for Folding@Home that is very sensitive for instability, give me in a very short time errors. The OC from the curve has never given errors.

Great what Nvidia has done huere, an your implantation Unwinder is the best. In EVGA Precision I only get, an average Score, I'm not even able to apply the new curve (at least with the last version tested). Perhaps of that behavior, a lot of User use, Afterburner the wrong way. They think it works like the other tool.

Because Nvidia pushed Precision so much, the average users have tried that tools first. Only after they realize that it is only crap, the try Afterburner.

By the way, as RTX User, is there something Special, you want tested? Until now I hadn't have bug, so I couldn't report anything.

 

Hi! For RTX card need adjust voltage slider? I don`s see difference

 

This has got to be one of the most frustrating behaviors of GPU overclocking, because if you want to set a curve, you must do so after letting the card cool down from load and wait. Make a change, then click the profile again and see if the curve is *actually* making only that change. Otherwise,
for example if you want to modify one point down 13mhz then save it, you've saved an ENTIRELY DIFFERENT CURVE that will now behave ENTIRELY DIFFERENTLY. I took me a while to catch on this was happening - my card is always stable at 2126MHz on 1.093v up to the highest temperature it will reach. I have to set it to 2139MHz just to get 2114MHz after a while, but worse is under no circumstances do I want 2152MHz as my card has the potential to crash under heavy load above certain temperatures, but that's what my card will run at sometimes during the first few minutes of the game or in menu IF I MESS UP THE PROFILE by saving changes when clicking the profile and hitting apply do not match.

So although I know my best performing stable clocks, I have to put up with worse performance as manually compensating by starting higher will give me instability before it drops clocks. This is all just for the 1.093v point.

I understand this is how Nvidia does it by design. But what possible argument could there be for this being desirable or good behavior??

So forgive me for being blunt, -because I don't understand how this idea could possibly be a bad thing- What MSI Afterburner NEEDS is a GPU Boost CLOCK COMPENSATION mode. Where it detects GPU boost changing clocks for ANY perfcap reason on a voltage point and automatically offsets an equally opposite amount so clocks remain the same on their respective voltage points. EG: 1.093v should always correspond to 2126MHz because that's what I set. Throttling voltage and the usual behavior for curves still exists, clocks just don't change on individual points normally (power perfcap is separate from this AFAIK and is more dramatic).

Unwinder I greatly respect your expertise, I want to be clear that am not questioning it or claiming there is a bug. I just don't understand why it needs to be this way for individual voltage points. Is a compensation system such a terrible idea?

 

@cookieboyeli Thank you very much for your post, at least someone tried to explain. Yes, youre totally right of course, I see it the same as you. It doesnt make any sense, as usual, to be like "that is by design, deal with it" and be ignorant about improvement concepts. A simple solution for this could be a manual overwrite mode to activate in AB, and then AB tries to keep a curve and apply it again maybe every x seconds to work against Nvidias driver compensation. My card is 100% stable with this curve I tried out and the undervolt it achieves in this example 0.875V at the max boost frequency of around 1750MHz. Or even have a simple automatic mode, where you define an upper maximum voltage value, and AB tries automatically to find a value around it, maybe tries in steps to lower the frequency every x seconds, waits, lowers it, and then tries to be stable around a defined value. Especially for undervolt scenarios, where there is the desire to run the card as cool as possible, and not as "fast as possible".

 

Hi @Unwinder I used the oc scanner on my Gigabyte 2080 Ti Gaming OC, but there's something strange on the final result.

I've do the following steps :

1. Set power limiter to max
2. Set memory frequency to +400
3. Leave voltage control at default
4. Temperature limit to max
5. Hit scan button

At the end of scan (15 minutes ) as overclocking results +138mhz on core clock.

Hit apply on Afterburner and then saved as profile.

In the end I've launched GPU-Z (ver. 2.14) and with my surprise the gain of the overclock was only 70mhz on core clock and not + 138mhz as OC scanner curve result.

Where did I wrong to do??

 

@Alberto

You done nothing wrong. But that you consider, that you get +138mhz, that is the wrong way of seeing it.
You get a new Curve, where some points are +70, +165, +128..... (examples) so the +138mhz is perhaps average but not at all you OC.
GPU-Z is not the best way, to see the clock Speed. If you open the Curve and click on the different Points you see, which one was raised and how much.

An If you watch in Afterburner you Core Clock Slider, you should see 2Curve" as value and not an +XY mhz.


Edit: too slow

 

I've reread and I've understood that the oc scanner give an average result and it is different on V/F curve points.

On Afterburner what should I set for the core clock? The OC curve or the average value manually? (in my case +138mhz)

Please @Unwinder I'm a terrible newbie