mangoapp: pull engine from gamescope #1498
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pac85
force-pushed
the
gamescope_engine_master
branch
from
77b9b8d to
9483d28
Compare
pac85
force-pushed
the
gamescope_engine_master
branch
from
9483d28 to
b897ed7
Compare
|
I've continued using this + the gamescope PR over the past weekend, and it was accurate in every instance I tried: VULKAN, VKD3D, DXVK, and Gamescope all were matched correctly in the mangoapp overlay. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gamescope side: ValveSoftware/gamescope#1653
With that patch gamescope will use it's layer to pull
engineNamefromVkApplicationInfoand send it to mangoapp.This change will make it use that information, this allows to have the engineName displayed in a simpler way without MangoHud's layer.