Skip to content

xess xmx: Enable the Vulkan extensions and features XeSS requires - #3379

Open
damian-tomczak-intel wants to merge 2 commits into
HansKristian-Work:masterfrom
damian-tomczak-intel:xess-release
Open

damian-tomczak-intel wants to merge 2 commits into
HansKristian-Work:masterfrom
damian-tomczak-intel:xess-release

Conversation

@damian-tomczak-intel

Copy link
Copy Markdown
Contributor

Enables the Vulkan instance and device extensions and features that XeSS needs when Proton forwards XeSS to the Linux library. XeSS records its work into vkd3d-proton's VkDevice, so the device has to be created with them.

The list is taken from XeSS itself: if libxess.dll exports xessVKGetRequiredInstanceExtensions, xessVKGetRequiredDeviceExtensions and xessVKGetRequiredDeviceFeatures, vkd3d-proton enables what they report. If libxess.dll can't be loaded or doesn't export them, nothing changes.

Part of the [XeSS XMX] series, see the comment below for the other PRs.

@damian-tomczak-intel

Copy link
Copy Markdown
Contributor Author

This is one of four [XeSS XMX] PRs that together add XMX-accelerated XeSS to Proton:

The Proton PR bumps the other three submodules, so it should go in last.

Query libxess.dll's own API for the instance/device extensions and
features it needs and enable them, instead of hardcoding them by hand.
Best-effort: a missing libxess.dll just skips silently.
LoadLibraryA, GetProcAddress and FreeLibrary don't exist in native Linux
builds. Use the vkd3d_dlopen() wrappers instead and only try to load
libxess.dll on _WIN32, since it's a Windows DLL that native builds can't
load anyway.
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.

1 participant