-
-
Notifications
You must be signed in to change notification settings - Fork 270
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
winecommand: Fix LatencyFleX enablement #2993
Conversation
This is not a driver ICD...
Pylint result on modfied files:
|
Have you tested locally (via a flatpak bundle, either from here or a flatpak built locally) that this works? |
I did not test in the Flatpak but I did on my host. It will work as long as the Flatpak (or it's runtimes) ship LatencyFleX. (Looks like it does here: https://github.com/bottlesdevs/Bottles/blob/main/com.usebottles.bottles.yml#L173) Without this commit, LatencyFleX is being added as a driver ICD which is completely wrong, it is a Vulkan layer and the option is not correctly controlling whether the layer is enabled. |
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.
Everything LGTM, and is in line with upstream behavior. Will test momentarily.
If you could test in Flatpak, that would be greatly appreciated. We don't support native packages at all, and if it only works there, this isn't something I think we're going to worry about. |
It's our responsibility as maintainers to test it :p That said, this is a proper fix and in-scope of what it's trying to achieve. If the LatencyFleX flatpak doesn't work then it's a packaging problem on our end; fixing that would make it out of scope of the MR. |
This is not a driver ICD...