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

Why did you remove the defaults values? Why did you remove VRAM usage? Mapping for timings? #8

Open
1usmus opened this issue Mar 19, 2023 · 0 comments

Comments

@1usmus
Copy link

1usmus commented Mar 19, 2023

  1. Why did you remove the defaults? I only see the maximum value, the minimum value, the step and the current value. Where are the default values for VID, CORE and so on?
    I have to do a reset of the adapter and then read the current settings to get the defaults.

  2. To get the VRAM usage I have to call the function to get the standard information about the adapter and its maximum capacity and only after that I will monitor the current memory size to get the percentage.

  3. The timing settings are controlled through mapping. Have you even seen the number of timing options for VRAM? There are 2 for RDNA2 / RDNA3. For previous generations there are 3. For this mapping?

  4. Speed of execution. ADL polling of all sensors - less than 1ms, ADLX - >50ms (GetCurrentGPUMetrics > 50ms).

  5. Set Core Freq, Core VID, Mem Freq > 580ms. Instead of 16ms?

The code was written by people who have never seen a video card?
Do you think this is the "new generation" of ADLs? It's a shot in the foot.

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

1 participant