I have (now) 0.2.8 with PP_Table IMO it will work NP with Vega. Note: Please change Version into 0.2.9 Note 2: Fan settings not working, it's all greyed out.
As is not my tool I prefer to not to change the version to don't have misunderstandings. But maybe I would have to add some thing at the verison, I don't know. I pmed tede like a mounth ago, but I didn't had response. Yes, fan settings is not working because for polaris is not working ok, for my, and I don't know how to solve it. So is greyed out by default with FanDeactivatedGpus=0 at the ini file. But you can use it clicking on it with crtl pressed.
Hi, I have done today some fixes to my ONT version. I have added to its name R.B.R.T Edition, to don't have misunderstandings with tede's version, and I have fixed some minor errors I saw at my code. Also I am going to post two versions. V1.1 that is the first version with some fixes to some errors I saw at my code. And V2.1 that is downvolting more by temperatures DPMs 1 to 6. V1.1 V2.1
Think I found my happy settings. No issues playing Gears 5 and Doom Eternal @ 4K with highest settings.
Hey, is there a fix for this? Whenever i set the values for these and click apply, they reset. I want to atleast lock the p0 voltage and core clock so i would have less fluctuation.
Those values are locked by the driver and can't be edited, I have tested to try to enable them at ONT but I didn't had success. But you can edit them at the ONT registry PPtable editor. Also you can disable/enable those P stateas as is said by tede at the first post: "-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."
Thank you so much! Disabling P0 state worked for me. I cant believe how much time i've spent around this thing, and yet that the solution was so simple.. Thank you so much again!
Hi! I too am finding Wattman buggy and I want to use this tool. However, I have a 5700XT. Is this supported? I created the Windows Schedule and it just says 'Running', and its been a few minutes. Shouldn't this be relatively instant if no other tasks are running? Arguements: -r0 -p0"5700XT F Drive"
Hi. Your tool is working great with my Vega64. Now I can use manual fan curve with ZeroRPM. That is not possible with Wattman. Can you explain me, what is Acoustic Limit (Mhz)? Thank you for this great tool!
Maybe check this chief it resets vega 64 voltages badly leaving them broken until the adapter is removed from control panel https://forums.guru3d.com/threads/overdriventool-tool-for-amd-gpus.416116/page-27#post-5769431 if you want a manual fan curve with zero rpm edit amd settings xml file for wattman here's one of mine for as an example 1672 1045 10pl.xml Code: <?xml version="1.0" encoding="UTF-8"?> <GPU DevID="687F" RevID="C1"> <PPW Value="3"/> <FEATURE ID="4" Enabled="False"> <STATES> <STATE ID="0" Enabled="True" Value="852"/> <STATE ID="1" Enabled="True" Value="991"/> <STATE ID="2" Enabled="True" Value="1084"/> <STATE ID="3" Enabled="True" Value="1138"/> <STATE ID="4" Enabled="True" Value="1200"/> <STATE ID="5" Enabled="True" Value="1401"/> <STATE ID="6" Enabled="True" Value="1536"/> <STATE ID="7" Enabled="True" Value="1672"/> </STATES> </FEATURE> <FEATURE ID="12" Enabled="False"> <STATES> <STATE ID="0" Enabled="True" Value="800"/> <STATE ID="1" Enabled="True" Value="900"/> <STATE ID="2" Enabled="True" Value="950"/> <STATE ID="3" Enabled="True" Value="1000"/> <STATE ID="4" Enabled="True" Value="1050"/> <STATE ID="5" Enabled="True" Value="1100"/> <STATE ID="6" Enabled="True" Value="1150"/> <STATE ID="7" Enabled="True" Value="1200"/> </STATES> </FEATURE> <FEATURE ID="5" Enabled="True"> <STATES> <STATE ID="0" Enabled="False" Value="167"/> <STATE ID="1" Enabled="False" Value="500"/> <STATE ID="2" Enabled="True" Value="800"/> <STATE ID="3" Enabled="True" Value="1045"/> <STATE ID="4" Enabled="False" Value="0"/> <STATE ID="5" Enabled="False" Value="0"/> <STATE ID="6" Enabled="False" Value="0"/> <STATE ID="7" Enabled="False" Value="0"/> </STATES> </FEATURE> <FEATURE ID="13" Enabled="False"> <STATES> <STATE ID="0" Enabled="False" Value="800"/> <STATE ID="1" Enabled="False" Value="800"/> <STATE ID="2" Enabled="True" Value="950"/> <STATE ID="3" Enabled="True" Value="1100"/> <STATE ID="4" Enabled="False" Value="0"/> <STATE ID="5" Enabled="False" Value="0"/> <STATE ID="6" Enabled="False" Value="0"/> <STATE ID="7" Enabled="False" Value="0"/> </STATES> </FEATURE> <FEATURE ID="9" Enabled="False"> <STATES> <STATE ID="0" Enabled="False" Value="0"/> </STATES> </FEATURE> <FEATURE ID="8" Enabled="False"> <STATES> <STATE ID="0" Enabled="True" Value="0"/> <STATE ID="1" Enabled="True" Value="0"/> <STATE ID="2" Enabled="True" Value="10"/> </STATES> </FEATURE> <FEATURE ID="17" Enabled="False"> <STATES> <STATE ID="0" Enabled="True" Value="2"/> </STATES> </FEATURE> <FEATURE ID="18" Enabled="True"> <STATES> <STATE ID="0" Enabled="False" Value="0"/> </STATES> </FEATURE> <FEATURE ID="19" Enabled="False"> <STATES> <STATE ID="0" Enabled="False" Value="0"/> </STATES> </FEATURE> <FEATURE ID="20" Enabled="False"> <STATES> <STATE ID="0" Enabled="False" Value="0"/> </STATES> </FEATURE> <FEATURE ID="21" Enabled="False"> <STATES> <STATE ID="0" Enabled="False" Value="0"/> </STATES> </FEATURE> <FEATURE ID="22" Enabled="True"> <STATES> <STATE ID="0" Enabled="True" Value="30"/> <STATE ID="1" Enabled="True" Value="30"/> <STATE ID="2" Enabled="True" Value="50"/> <STATE ID="3" Enabled="True" Value="33"/> <STATE ID="4" Enabled="True" Value="56"/> <STATE ID="5" Enabled="True" Value="43"/> <STATE ID="6" Enabled="True" Value="59"/> <STATE ID="7" Enabled="True" Value="54"/> <STATE ID="8" Enabled="True" Value="62"/> <STATE ID="9" Enabled="True" Value="58"/> </STATES> </FEATURE> </GPU>
My new options of my ONT version are not compatible and are not working for navi gpus that uses Overdrive8 API. The up to 40 Mhz should not be seen for your gpu, I must have done something wrong. The fan section is greyed out at my version becase I had some problems with my rx 590 fans when applying a config. Even not changin any thing at fan section, fans where behaving diferent than at stock. So I let it greyed out for caution. I don't know if it's only a problem caused by some specific drives or if it's solved now by a new driver. But I don't know how to solve it at ONT code or if the problem can be solved at it.
Thanks I found out how to un gray them but yes your right they don't seem to take effect great work tho
I didnt say it doesnt work i said it doesnt work properly there's a difference I have pointed out the problem if you choose to break your voltage table specific to you chip bin so be it but i told u If you apply settings it works fine if you ever hit that reset button your voltage table is broken until you remove the adapter in windows and let it reinstall
