Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] State table clock ranges do not save with the profile #270

Open
ryannathans opened this issue May 14, 2021 · 2 comments
Open

[BUG] State table clock ranges do not save with the profile #270

ryannathans opened this issue May 14, 2021 · 2 comments

Comments

@ryannathans
Copy link

When saving a state table profile the "set ranges" window does not save and must be manually set every time the profile is loaded.

For example, this radeon vii oc profile I have made has a peak clock of 1925mhz and such every time I apply the profile (almost every boot) I must manually open this window and change 1801 to 1925mhz and also bump up the max memory clock to 1200mhz.
image

@Oxalin
Copy link
Contributor

Oxalin commented Jan 27, 2023

Is this still an issue? I could have a look at it under my fork.

@ryannathans
Copy link
Author

@Oxalin not sure, I swapped to using corectrl and a 6900XT and now I only have one voltage control lol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants