-
-
Notifications
You must be signed in to change notification settings - Fork 216
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
Dynamic Response Time aka Overdrive missing #1291
Comments
Hmmmm that is a tricky... what was the default value for it? Was it off by default? |
Anyway, let's start with a WMI dump from Gen 9, because I don't have it yet. Please post the output of this powershell script:
|
Yep it's off by default |
I'll do this tomorrow for you |
https://pastebin.com/ECyw0hKU here is the dump |
btw i have the 240hz panel, not sure if that makes any difference for you |
Hmmm... ok let's try something... Check if this returns different values depending on what you select in the dropdown. Make sure that you click "Done" after each change:
If it works, write down the values it returns for each of the options from the dropdown, so I can map them correctly. |
1 for enabled 0 for disabled |
Great, we have a jackpot 😎 thanks for testing! |
no problem |
Here is a test build you can try: installer Please upload a log as well and see if some other options didn't disappear, because I did a small refactoring too. |
nothing has disappeared but overdrive still does not show up |
I think you had another instance running because log is broken. |
yep my bad, heres another log |
Shit, I made a typo :D Here's another one: installer |
yep it shows up now |
Rules
Version
Latest Beta
OS
Win 11 Latest
Device
Legion 5 Gen 9
BIOS version
NMCN22WW
What's wrong?
well lenovo renamed the overdrive mode to dynamic response time, overdrive mode doesnt show up in LLT at all for Legion 5 Gen 9
How to reproduce the bug?
Its missing entirely
What is the behavior that you expected?
Expect Overdrive/Dynamic Response Time to be there
Logs
dont think its possible to log
Additional information
No response
The text was updated successfully, but these errors were encountered: