topic Re:Vulkan API Issue - vkGetPhysicalDeviceMemoryProperties returns incorrect values in Graphics

Vulkan API Issue - vkGetPhysicalDeviceMemoryProperties returns incorrect values

retroNUC — Sun, 10 Oct 2021 22:40:24 GMT

Follow-up on my previous closed issue - Vulkan - BETA Drivers Break RetroArch/ParaLLel-RDP - Intel Community

Worked with the developers as suggested, who identified an issue with the Vulkan API implementatio on Intel Graphics drivers since 27.20.100.9616:

"ParaLLel-RDP crashes on current Intel Xe drivers. On newer drivers vkGetPhysicalDeviceMemoryProperties calls incorrectly populates the VkPhysicalDeviceMemoryProperties struct values meaning that all contained memoryTypes->propertyFlags fields return 1 instead of the or'd flag values."

[Parallel-RDP] Crashes on load for newer Intel Xe drivers - "This device probably does not support 8/16-bit storage" · Issue #383 · libretro/mupen64plus-libretro-nx (github.com)

Fix Parallel-RDP on Intel Xe by stuken · Pull Request #388 · libretro/mupen64plus-libretro-nx (github.com)

Could this be passed along to engineers to potentially investigate the issue? Thank you!

Re: Vulkan API Issue - vkGetPhysicalDeviceMemoryProperties returns incorrect values

retroNUC — Mon, 11 Oct 2021 22:53:29 GMT

With further debugging from the software developers, it turned out to be a separate issue, so feel free to ignore this. Thanks.

Re:Vulkan API Issue - vkGetPhysicalDeviceMemoryProperties returns incorrect values

AndrewG_Intel — Wed, 13 Oct 2021 04:57:19 GMT

Hello @retroNUC

Thank you for posting on the Intel® communities.

We understand that this is a separate issue that you are debugging with the software developer and as per your request, we will ignore this request, therefore, we will proceed to close this thread now.

Best regards,

Andrew G.

Intel Customer Support Technician