Looks like a new version was pushed out 1.2.0.3, but I can’t find what changed or patch notes.
Still same issue tho.
Also tried the command line options posted above one at a time and all together. No change. 
Hi,
Also experiencing the same issue since the latest season patch. I’m on NVIDIA 1070 with only 8GB of VRAM. For me it helped changing all graphics related settings in le_graphicsmanager.ini[1] to Low from Medium and making sure to run it on 1920x1080 screen, 3440x1440 ran out of memory after a while.
Has some client crashes and one instance where nvidia driver crashed and caused all graphics on system to hang. It was otherwise responsive (not really helpful on a desktop system) though.
It’s something at least…
Sometimes it fails to launch though. It starts and uses 200% CPU (two full cores) forever (well… forever is unconfirmed…) in the background (no GUI).
This error shows up in kernel ring buffer when this happens:
kernel: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000a00] Failed to allocate NVKMS memory for GEM object
[1]: ~/.local/share/Steam/steamapps/compatdata/899770/pfx/drive_c/users/steamuser/AppData/LocalLow/Eleventh\ Hour\ Games/Last\ Epoch/le_graphicsmanager.ini
1 Like
Looks like the problem lies in DXVK and whatever Update 1.2 changed in the graphics pipeline.
A workaround is to do the following:
Step 1: set Last Epoch’s launch options to:
PROTON_USE_WINED3D=1 %command%
Step 2: run the following to update your Wine config
tee -a ~/.steam/steam/steamapps/compatdata/899770/pfx/user.reg > /dev/null <<EOF
# This prevents an overly dark display when using OpenGL
[Software\\\\Wine\\\\AppDefaults\\\\Last Epoch.exe\\\\X11 Driver]
"UseXVidMode"="Y"
EOF
That’s it. The game will now run using Wine’s Direct3D → OpenGL translation layer rather than DXVK’s Vulkan one, which completely solves the poor frame rate and stuttering problem. Using VSync may result in more stable frame rates.
You can read this old reddit post for more information.
2 Likes
Didn’t work for me.
I am experiencing the same on 3080TI, nvidia-550 driver.
This method resulted in a black screen in the game. (The video didn’t crash, just the game)
The solution above doesn’t work for me.
The stuttering started in less time when using OpenGL ~45 minutes gameplay vs ~1 to 1.5 hours under Vulkan - however this does seem to be a function of VRAM usage and not time directly, i.e. entering new zones over time increases VRAM usage from ~8GB baseline to somewhere between 9.5GB and 10GB of usage when the stuttering begins, at least that has been my experience.
Side note: For those with Ryzen chips (having integrated GPU) as well as dedicated, if you notice that your FPS is terrible in menus when logging in and selecting character after applying the “fix”, try:
DRI_PRIME=1 PROTON_USE_WINED3D=1 %command%
so that OpenGL uses your dedicated GPU.
Managed to get mangohud working and reproduced what Nixiam saw i.e. frame time spikes related to stuttering when character is moving vs smooth when standing still.
I have this same symptom, but don’t get that error message. I do have it in my logs but at completely unrelated times, so I know it’s not that the log is disabled or something.
It happens about 50% of the time.
I also have a different issue than I think is described here - there’s a huge hitch occasionally, usually right after a champion spawns. The whole game freezes up for 1-4 seconds. Sometimes when it comes back I’m dead (fortunately I play softcore anyway). Sure seems like a shader/texture loading issue given the context. I tend to have 4GiB of VRAM free while playing (the game uses around 10), so it’s not a problem of lacking VRAM.
Sorry,
I did rewrite/add additional information the message. That error shows when the nvidia driver fails to allocate memory (first part of my message regarding game hanging/crashing). Second part (regarding game not launching successfully) there are, indeed, no errors at all. It just runs in the background.
All issues gone as of today. My issue must have been server side.
1 Like
Unfortunately no, just crashed after 5 minutes of playing
Don’t have any issue on my Arch system with a 9800X3D and a 7800XT, 0 crash since 1.2 after something like 30 hours.
Only trouble is the game sometime don’t start, I have to restart it a few time for it to work.
RADV_DEBUG=nodcc MESA_GLSL_CACHE_DISABLE=true PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 WINEDLLOVERRIDES=winemenubuilder.exe=d GDK_BACKEND=x11 %command%
Adding mesa startup params worked for me and fixed the issue. Small explanation of the arguments:
**RADV_DEBUG=nodcc**
Disables DCC compression on AMD GPUs, which helps prevent VRAM fragmentation and memory leaks.
**MESA_GLSL_CACHE_DISABLE=true**
Turns off the shader cache, reducing VRAM usage. Might cause slightly longer loading times, but improves stability on long play sessions.
**PROTON_NO_ESYNC=1**
Disables Eventfd-based synchronization (esync). Some games are more stable without it.
**PROTON_NO_FSYNC=1**
Disables futex2-based synchronization (fsync), similar to above. Increases compatibility in some setups.
**WINEDLLOVERRIDES=winemenubuilder.exe=d**
Prevents Wine from showing unwanted system dialogs or popups.
**GDK_BACKEND=x11**
Forces the game to use XWayland instead of native Wayland. This improves window handling and prevents invisible game windows on some systems (especially KDE Plasma with high-DPI monitors).
You maybe should remove GDK_BACKEND=x11 if you are not using wayland
2 Likes
I’ve finally resolved my stuttering issue.
LD_PRELOAD="" with Proton Experimental is all that is required - when I originally tried to test this, I ran into the issue where the game window doesn’t launch and so I stopped attempting to use this setting as I mistakenly attributed it to that env var.
As I also use KDE Plasma with Wayland, I used the suggestion from EricV1993 above and added GDK_BACKEND=x11 also which fixed the launch issue for me - it now seems to reliably launch every time.
My final launch options:
LD_PRELOAD="" GDK_BACKEND=x11 %command%
1 Like
1.2.1.2. just dropped and now my low FPS issue (less than 35 FPS) is back.
Also now getting the “launching the game doesn’t always work” issue.
Prior to latest patch could get some sessions to work for a while, post latest patch unable to get the game to play for more than 30 fps for more than a few seconds. None of the posted fixes seem to help.
1 Like
I’m also in the same situation. Before the patch I was playing for a couple hours without any issues but after this last patch, it’s a major issue after 30-40 minutes. Nothing but fps from 60 to 12 none stop over and over for me.
1 Like
And I’m back over 150FPS today.
Ugh…this is frustrating. What changed? Has to be server side IMHO.
RADV_DEBUG=nodcc MESA_GLSL_CACHE_DISABLE=true
I can’t really find an equivalent set of commands for nvidia gpus, someone tried something similar?
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.