These logs are easier to read perhaps.
Last Epoch_d3d11.log.gz
Last Epoch_dxgi.log.gz
info: Presenter: Actual swapchain properties:
info: Format: VK_FORMAT_B8G8R8A8_UNORM
info: Color space: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
info: Present mode: VK_PRESENT_MODE_FIFO_KHR (dynamic: yes)
info: Buffer size: 2560x1440
info: Image count: 3
debug: Compiling shader FS_074d6f963b3faa9499dadbbfcbb3cb908d4e26df
debug: Compiling shader VS_735573e7185f5ec44694ce6f2fc26e217270b418
debug: Compiling shader FS_64e72a40e660e9997042bce1dd1722022493868c
debug: Compiling shader CS_738245f11290b70a490d59cd68376f2097252166
debug: Compiling shader CS_8cb8d18a74013a0a281287fa6a3c9b640b3702e4
debug: Compiling shader CS_32efd6005a36dec1638458b6805a3c78626edb5d
debug: Compiling shader CS_e281622b15526ebdf96b35bc9fab8d263b9c74c5
debug: Compiling shader VS_23856efb644642552388782b4d3a160f8ec65b23
debug: Compiling shader FS_04b0aa563622a25aa7baa089c01409c42b6c580b
debug: Compiling shader CS_bfd8b4adb7d3169a4b058223ab1dbafaa0cda81d
debug: Compiling shader CS_64a1b889ab3c26b2351bcf1efdb5be027c5b9355
debug: Compiling shader CS_2e9f5c93b55eb548ac16b06dc3dc446d1edcdc17
debug: Compiling shader CS_f89d91cd86c09bed1682acd9296b491047de15c8
debug: Compiling shader CS_42622a6181cd63c32d63db234a27e1c8bd6da54d
debug: Mapped memory region 0x7398ddc00000 - 0x7398debfffff
info: Presenter: Got VK_SUBOPTIMAL_KHR, recreating swapchain
info: Presenter: Actual swapchain properties:
info: Format: VK_FORMAT_B8G8R8A8_UNORM
info: Color space: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
info: Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR (dynamic: yes)
info: Buffer size: 2560x1440
info: Image count: 3
err: Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
This looks like a driver issue unfortunately.
Multi GPU setups are always "fun". What I've found to work rather reliably is using a device filter on dxvk side, like so: DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce". PRIME offloading doesn't really hide the GPUs, only selects the right one for the driver, but dxvk (as well as any other Vulkan apps/games) will still see both.
Game already uses the NV card, so I doubt that applying a device filter changes anything.
vkCreateSwapchainKHR failing is firmly outside our control, and while there was a wine issue that would cause this to happen in some full-screen apps at some point, that should have been resolved as well.
Game already uses the NV card, so I doubt that applying a device filter changes anything.
Exactly, this isn't the classic Hybrid issue with selecting the correct card afaict.
First it says:
info: Present mode: VK_PRESENT_MODE_FIFO_KHR (dynamic: yes)
then
info: Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR (dynamic: yes)
is there a way to force a certain mode?
I guess the Nvidia driver and the Intel driver can't agree on the buffer format to present or something like that.... ?
is there a way to force a certain mode?
You can do it with MangoHud.
https://github.com/flightlessmango/MangoHud?tab=readme-ov-file#vulkan-vsync
DXVK_CONFIG="dxgi.syncInterval=1" would force FIFO.
Is the game trying to go into fullscreen mode or something? If so, do you happen to have any sort of display scaling enabled?
Last time we had issues with this, the reason was that we got an incorrect surface size from the driver.
Game already uses the NV card, so I doubt that applying a device filter changes anything.
Exactly, this isn't the classic Hybrid issue with selecting the correct card afaict.
Fair point, and it may not help on this issue, but do note there might still be some oddness when both GPUs are available, as the reported order might change due to power saving kicking in or other driver-side shenanigans. I have not ever had issues with a device filter applied though.
No display scaling here. I tried all the DXVK_CONFIG="dxvk.tearFree = True; dxgi.syncInterval = 1;" combinations.
I could edit the config file to set the window size to 1024x768. Now it starts!! I guess it was running out of VRAM?!
Then I could go into the game and lower settings from Medium to Very low. Now I can play the game in 2540x1440 fullscreen also.
proton experimentalx1 2025-05DXVK_CONFIG="dxvk.tearFree = True; dxgi.syncInterval = 1;"x1 2025-05DXVK_CONFIG="dxgi.syncInterval=1"x1 2025-05DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce"x1 2025-05
Last Epoch fails to create Vulkan swapchain on this computer.
It first displays a 2D splashscreen, then hangs when it's about to setup a 3D context (?).
I have tried many Nvidia version, all the Proton version. Tried both X11 and Wayland.
Tried Nvidia on-demand and Performance mode.
Tried with
VK_DRIVER_FILES=/usr/share/vulkan/icd.d/nvidia_icd.json %command%Tried with
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%Tried disabling Steam overlay.
Other DX games runs fine afaict.
OS: Ubuntu 24.04, Gnome. Tried with compiled Mutter 46.9 also.
Software information
Last Epoch, out-of-box setting
System information
vulkaninfo.txt
steam-899770-vulkan-issue.log.gz