Skip to content

Conversation

@pac85
Copy link

@pac85 pac85 commented Dec 5, 2024

Gamescope side: ValveSoftware/gamescope#1653

With that patch gamescope will use it's layer to pull engineName from VkApplicationInfo and 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.

@matte-schwartz
Copy link
Contributor

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.

Comment on lines +20 to +22
uint16_t displayRefresh;
bool bAppWantsHDR : 1;
bool bSteamFocused : 1;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These additions (displayRefresh, bAppWantsHDR, bSteamFocused) seem unrelated to adding engine name. But it looks like gamespace has a different definition.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah so the point was to sync it up with gamescope https://github.com/ValveSoftware/gamescope/blob/master/src/mangoapp.cpp#L31

Since I've added a field I had to add the fields before it as well.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, already through so.

@pac85 pac85 force-pushed the gamescope_engine_master branch from d9dd0ba to 2b2a20e Compare December 12, 2025 16:49
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

Successfully merging this pull request may close these issues.

3 participants