MSI AB / RTSS development news thread

I do not understand, what are the subtleties between these four metrics in MSI Afterburner 4.6.3 beta 4? Aren't 2 of them redundant?

GPU1 memory usage [internal]
GPU1 dedicated memory usage [GPU.dll]
GPU1 memory usage \ process [internal]
GPU1 dedicated memory usage \ process [GPU.dll]

 

Hi, am I going mad but isnt this the same build (4.6.3 beta 4 build 15910) as the one ive been using since November? I uninstalled my previous one to install this and it says the same details but its only just been uploaded? Have I misunderstood something? Love the software BTW nothing gets close, cheers

 

MSI Afterburner somehow lost GPU clock in OSD. It's not even listed anymore as an option to be displayed. It worked without problems until today when it disappeared during the gameplay

Can anyone help me, please?

 

@Pr3t3nd3r and this has what to do with development of the current beta?
For user related problems, please use own thread.

 

Maybe it's a bug and is reported?

 

its not a bug. OSD doesn't just go missing,

reinstall the driver.

 

I literally did nothing and Core Clock is back again...strange behavior...anyways, thank you for your help and sorry to bother you. I am kinda new here and just wanted to share my xp with it

 

a device TDR can cause applications using nvapi to lose the device sensors.

 

Hey all, just looking for some perspective on how to interpret the results of the new OC Scanner. Last night I let it run with the voltage, power, and temp limits cranked up to max and got the following results...

Code:

17:42:45 Connected to MSI Afterburner control interface v2.3
17:42:47 GPU1 : VEN_10DE&DEV_1F02&SUBSYS_10713842&REV_A1&BUS_9&DEV_0&FN_0
17:42:47 Start scanning, please wait a few minutes
17:42:47 Scan failed with code 22h
17:42:49 GPU1 : VEN_10DE&DEV_1F02&SUBSYS_10713842&REV_A1&BUS_9&DEV_0&FN_0
17:42:49 Start scanning, please wait a few minutes
17:59:00 Scan succeeded, average core overclock is 80MHz, memory overclock is 200MHz
17:59:00 Dominant limiter
17:59:00   No load
17:59:00 Results are considered unstable
17:59:00 Overclocked curve exported to MSI Afterburner

It seems to work if I hit "Scan" a second time after the first failure, but the results seem to indicate that the scan wasn't very accurate. Hence "No load" and "Results are considered unstable." Is there something I can do to get this working properly? Thanks!

EDIT: Forgot to mention, this was run on my EVGA 2070 Black

 

Hi,

i get both the below errors when i try to launch OC Scanner!

some details:
-using MSI Afterburner 4.6.3 Beta 4
-Driver version is the latest 460.89
-fresh install of Windows 10
-my GPU is an RTX 3090.

will appreciate the help on this

 

Install the corresponding Microsoft Visual C++ Redistributable Packages, you'll find them online.

 

visual C redist 2015/17/19 to be exact.

 

thanks!

 

Is there any way to assign a different color to a range of values in the new overlay editor?

So for example the current GPU temperature value would be green by default but would become yellow if it's in range, say, of 60-80C and red if it's above 80C?