-
Notifications
You must be signed in to change notification settings - Fork 177
Changed preset framerates; Add "low power" preset. #1422
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
Conversation
Awesome :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love this solution!
It was ksuprynowicz's idea. Give him the credit. :p |
Nah, I just wanted to switch off frame limiter on all presets. Kalila recommended adding power saving mode :) |
Everything works correctly on Linux |
I think we should test and merge this PR before doing a release. Current frame limiter on Medium and Low is very confusing. |
default: | ||
// Do nothing anymore | ||
// Do nothing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any reasonable way of getting here? There should either be no default for a compile-time warning, or a warning log instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know what UNKNOWN was intended for. I didn't really look into it but I don't remember seeing it used anywhere. It's not even the default mode. It wasn't related to this PR though so I didn't want to make too many unnecessary changes. Might be good to try logging it for a while and see if the log ever appears? If not, then remove it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think a log would be good here. I don't think anything should be reaching this point legitimately.
A fresh install with a fresh configuration yields the same results. OS Name Microsoft Windows 10 Pro |
Can you try from different Windows user account? |
So the Resolution Scale is set to minimum when you switch to HIGH (and only HIGH)? Does it change when you switch to any other preset after that? |
Yeah, it goes back to a normal 1.0 scale for the other options. |
I'm compiling something to test. Will push for you to test if it works for me. |
Can you test with that change? |
Regarding the low resolution for HIGH setting, see the following line in
|
Yeah, I just pushed that change to test. I'm not sure why the problem didn't occur for me or ksuprynowicz though. Maybe bad luck with our monitors? |
Once it builds then I will give it a shot. :) |
The following links are available: build (macOS-10.15, full) build (ubuntu-18.04, full)
build (windows-latest, full) build (self-hosted_debian-11_aarch64, full)
|
The issue appears to be solved now. Can anyone else download a copy from GH and check to confirm as well? |
I just tested it on Windows 10, and it works perfectly, both in VR and in Desktop mode |
default: | ||
// Do nothing anymore | ||
// Do nothing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think a log would be good here. I don't think anything should be reaching this point legitimately.
I could add the logging now but I wouldn't be able to test it for several days and it's kind of outside the scope of this P.R. I think it would be better if someone makes the change outside of this P.R. If you do want it here, feel free to make the change yourself. Edits by maintainers is enabled. |
No description provided.