Command Line:
-p[gpu_id]"Name"
apply profile "Name" to GPU with id=[gpu_id], silently
-c[gpu_id]"Name"
same as above, but with confirmation message that application started and everything went ok.
-r[gpu_id]
reset GPU with id=[gpu_id], silently
cp[gpu_id]"Name"
compare current values of GPU with id=[gpu_id] with profile "Name", and eventually set this profile if not equal, silently
cm[gpu_id]"Name"
compare current values of GPU with id=[gpu_id] with profile "Name", and eventually set this profile if not equal, with additional message if not equal found
co[gpu_id]"Name"
only compare current values of GPU with id=[gpu_id] with profile "Name", with message if not equal found
-consoleonly
displays all messages (eg. errors) in cmd.exe console window, instead of gui messages. Only commands that are put after -consoleonly are affected, example:
"OverdriveNTool.exe" -consoleonly -r0 -p0"1" -r1 -p1"1" -r2 -p2"2" - will affect all commands
"OverdriveNTool.exe" -r0 -p0"1" -r1 -consoleonly -p1"1" -r2 -p2"2" - will affect -p1"1" -r2 -p2"2" commands only

[gpu_id] - it's the first number taken from GPU description, for single video card it's 0
"Name" - name of the profile that was saved ealier, must be quoted if has spaces inside

example:
OverdriveNTool.exe -p0myProfile -p1"Profile 2"
In this example application starts without gui, then sets "myProfile" to GPU with id=0 and "Profile 2" to GPU with id=1 and then exit.

commands can be used all together, for example:
OverdriveNTool.exe -p0myProfile -r0 co1"Profile 1"
On configs with more than 10 GPUs [gpu_id] must have 2 digits, for GPUs 0-9 leading 0 need to be added, example: 00,01,02,03,04,05,06,07,08,09,10,11,12. Usage example: -p05"Name"

Additional info
Workaround for bug in 17.7.2 drivers, when driver sometimes uses default voltages instead of user settings: use reset and re-apply profile.
It's possible to disable/enable each P state. To do this click on P0, P1.. etc. label. If P state is disabled it will not be used by GPU.
I2C currently supports: IR3567B (RX470, RX480, some RX5xx), up9505 (MSI RX5xx)

I tried it on my 390 and it seems to be working, despite not being listed as one of the supported cards. The changes that I make with your tool are shown as being applied inside Radeon Settings and MSI Afterburner.

I like your tool, mainly due to the ability to save a profile + the ability to change State 0. Radeon Settings doesn't let me do so, only State 1 through 7. By changing State 0 I don't need to use Clockblocker anymore, which worked well, but this seems like a more elegant solution to me (unless changing State 0 brings with it some risks I'm unaware of, a possibility).

For Polaris P0 states always revert back to default, are you sure they are changed?

Click to expand...

If Afterburner and Radeon Settings/Wattman are to be believed, the core clock stays to what I've set it to. If I change every State except 0, my core clock will downclock itself and spike up and down due to activity while I'm idle. And then when I'm playing a game with relatively low requirements it'll sometime be at what I've set it as (1040mhz) and sometime drop down to lower clocks.

When I used OverdriveNTool to change every state, including State 0, to 1040mhz, my core clock remains stable at 1040mhz. Even if I'm idle on my desktop, it's at 1040mhz. In games, even after I close a game, it stays there. Afterburner doesn't show the "power limit" changing unless I restart AB, it shows the rest changing. Wattman shows the power limit change.

I've tried recording a short video showing it, in it you can see the activity graphs of both AB and Wattman. In AB we see the small spikes and then the solid 1040mhz. In Wattman you can see the orange line, which goes from being low to being solid at a higher level. You can also see the states all being at the same level.

I ended up cutting out the end part, where I launched a game, walked around, closed it and looked at the software again before using the "reset all" button to bring everything back to default. When I was doing it everything worked just fine, but the recording software (OBS) stopped recording properly after I opened the game. I think it's because I used the CPU to record and the CPU usage spiked when I opened the game. If it helps you any, I can do the same test later on but record with ReLive + the 'record desktop' option.

Nice May i ask why you need such high clocks and voltages in all states? It's power uneficient..
And resetting doesn't reset Fan for you?

Click to expand...

The 'reset all' button does reset the fan for me, I can hear the fan ramping up or down as I use the tool.

The reason I want the high clocks and voltages in all states is only for gaming, I bring them back to default values when I'm not gaming. There are some games where the power requirements can change quite quickly (depending on how much action is happening on screen or how I move the camera around) and when that happens, the card will by default try to change my clocks by itself to give me the power I need while still keeping my clocks low to save power. If the power requirements by the game change too quickly too often, it leads to stutters and I dislike that. I haven't been able to stop that from happening through the drivers themselves, but using your tool to change all of my states (and state 0) fixes that entirely. It'll be inefficient, but it completely fixes the problem and I don't mind being inefficient for as long as I'm gaming. Once I'm done with the game, I bring the values back to default and let the card downclock itself.

I tried it on my 390 and it seems to be working, despite not being listed as one of the supported cards. The changes that I make with your tool are shown as being applied inside Radeon Settings and MSI Afterburner.

I like your tool, mainly due to the ability to save a profile + the ability to change State 0. Radeon Settings doesn't let me do so, only State 1 through 7. By changing State 0 I don't need to use Clockblocker anymore, which worked well, but this seems like a more elegant solution to me (unless changing State 0 brings with it some risks I'm unaware of, a possibility).

Great work ,, really we were looking for a tool like this since wattool has stopped developing his tool ,
so i have an important note !!!
GPU is NOT listed the same arrangement of MSI afterburner or new claymore version
some for example I tested your tool in 2 rigs

1st rig was like this
calymore OverdriveNTool
0 1
1 0
2 3
3 2
4 5
5 4

2nd rig was like this
calymore OverdriveNTool
0 5
1 0
2 1
3 2
4 3
5 4

As you see from the previous list there is no constant rule of listing GPUs