Vulkan error, vk::PhysicalDevice::createDeviceUnique: ErrorFeatureNotPresent
|
To switch do DX11, the production_Config.ini must not only have the renderer set, but it must have it set in the DISPLAY section.
So if your file is empty, you have to put the following text to get it working: " I learned this the hard way when trying to launch a fresh install. The reason for this 'Vulkan error, vk::PhysicalDevice::createDeviceUnique: ErrorFeatureNotPresent' problem is that the system vulkan implementation is missing some "features" that are requested by PoE. In vulkan, a device supports and advertises a subset of predefined features. The application, upon initializing vulkan, has to specify which features it uses. If the application requests a feature that is not supported by the system (software or hardware), then the 'vkCreateDevice' returns 'VK_ERROR_FEATURE_NOT_PRESENT'. This gets translated to the error we all see. So, basically PoE requests some feature that is not available in the implementation of vulkan, at least for my integrated intel card (with mesa 23.1.8) I'm afraid this may affect all Intel integrated graphics cards. One can learn which features are supported by running the vulkaninfo command (no arguments required). Results for my system are over there: https://pastebin.com/Y3De65e2. Maybe someone with access to the source code can point which feature is required by PoE and missing in that output... |
|
|
DX11, and DX12 crash every 3-5min, Vulkan sucks with the crashes but there is less frequency, and I'm still hoping that GGG comes with an actual solution.
Hello guys.
|
|
|
ah, thanks for the explanation! make sense.
|
|
" Thanks for this tip. I'm on Linux and couldn't get the game to load, due to the exact same error message you quoted above. After I deleted "vulkan", the game did finally launch (it worked fine last league for some reason). However, it only took a few seconds until it crashed. Didn't see any error messages, but I looked up the log in Heroic game launcher, and found the suspected DeviceLost issue that I've seen many PC players complain about too. With Vulkan not working (which is usually the preferred choice for Linux due to less "overhead"), and DX simply crashing, it looks like I'm outta luck. Thankfully it works fine on PS5, but I wanted to see if playing on PC again was an option. Edit: This is my "vulkaninfo" on pastebin: https://pastebin.com/AmK6S971 It's a Linux Mint system with a Nvidia GTX 770 graphics card. End of the mentioned log file
Spoiler
err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkDevice: waitForIdle: Operation failed err: DxvkSubmissionQueue: Command submission failed: VK_ERROR_DEVICE_LOST Last edited by Pangaearocks on Nov 10, 2023, 11:33:31 AM
|
|
|
I'm having the same issue. Switching renderer from Vulkan to DirectX11 results in a fps rate of about 2. Unbelievable that this made it out to production. Beyond disappointment to get some time to play and update the game to this.
| |
|
i bought new pc, all works right now
| |
|
| |
|
This is actually helpful thank you
|
|
|
Same problem here on Linux with Wayland :c
|
|
|
Was having the same issue.
11th Gen Intel Core i7-11370H NVIDIA GeForce RTX 3070 Laptop (DDR6 8GB) vulkaninfo: https://pastebin.com/2f5pYywm In my case, it looks like it was ignoring the external GPU. Updating GPU drivers fixed it |
