ghost commented 6 years ago

Occurs on proton 3.7.3 and 3.7.4 installed with steam

Logs from proton default logging config: steam-prune-379430.log

Each time I've seen the system crash, I've seen the following lines in journalctl:

Aug 24 17:37:37 HOSTNAME kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=64337, last emitted seq=64339
Aug 24 17:37:37 HOSTNAME kernel: [drm] GPU recovery disabled.

A journalctl log from when I left the machine running after the initial hang: journalctl-crash-379430.log

Finally a workaround to get the game to get past black screen:

Needed to copy d3dcompiler_46.dll and d3dcompiler_47.dll from: ~/.steam/steam/steamapps/common/KingdomComeDeliverance/Bin/Win64Shared/ to: ~/.steam/steam/steamapps/common/KingdomComeDeliverance/Bin/Win64/

Further, this game DOES work under wine 3.12 staging, with DXVK 0.64 (Configured with Lutris) dxvk--lutris.txt

When i use the above configuration, I do not see the errors described above.

Game logs for those who care: Launcher.log kcd.log

System Specs, short:

Ubuntu 18.04
AMD RX 480x w/ amdgpu-pro-18.30-633530 (--pro flag enabled)
Linux HOSTNAME 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Desktop environment: i3wm

System Specs, long: steam-system-report.log

kisak-valve commented 4 years ago

Hello @xorgy, please verify you have both the 64 bit and 32 bit variants of mesa's vulkan drivers (like mesa-vulkan-drivers mesa-vulkan-drivers:i386) from your package manager.

xorgy commented 4 years ago

Hello @xorgy, please verify you have both the 64 bit and 32 bit variants of mesa's vulkan drivers (like mesa-vulkan-drivers mesa-vulkan-drivers:i386) from your package manager.

That wasn't the problem, though I changed a Steam setting (the default Proton) and it inexplicably deleted KCD (the whole thing), then reinstalled it; then it started working. I love when evidence is destroyed automatically.

jarrard commented 4 years ago

Yeah sometimes proton itself can install incorrectly. For example on my system it keeps installing to NTFS on new distro installs, never defaults to the .steam folder path. Proton doesn't like that.

Patola commented 4 years ago

Hi, I just want to include my gamingonlinux post here so that it can be seen by more people. Kingdom Come: Deliverance works correctly, BUT its performance is horrible. My post:

Hi all,

Anyone playing Kingdom Come: Deliverance -- https://store.steampowered.com/app/379430 -- on Linux via Steam Play? The game is great but its performance is horrible. I am trying to get as much performance as I can while preserving detail and high quality of textures, because even using the high resolution textures my GPU is seldom used above 4GB.

I have a RTX 2070 SUPER 8 GB and even then I can't get higher than 20 fps on the Rattay Tourney setting. It oscillates between 12 and 18 and sometimes goes up to 20. 2560x1080p, ultrawide, fullscreen.

I am not using any DXVK/PROTON variables (so, I am not using WINED3D11) and my launch options only has gamemoderun %command%. I run more than a hundred other games via proton with a very high framerate, including classics like The Witcher 3 and No Man's Sky.

What I have already done:

Disabled motion blur. It helps a little.
Tried changing drivers, from 435.21 to 440.26 (graphics-drivers ppa -- https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa). No noticeable change except that in the first minutes it stutters a little (maybe recompiling shaders?).
Tried the Valve fsync kernel -- https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ -- to use fsync instead of esync. Confirmed it was running ("fsync: up and running" on ~/.steam/error.log). No noticeable change.
Used the console to change "r_BatchType" -- https://www.protondb.com/app/379430#JgHjecc_a9 -- between 0 and 1. No noticeable change.
Used Feral's gamemode -- https://github.com/FeralInteractive/gamemode -- (added gamemoderun to the launch parameters, confirmed it was launching this way). No noticeable change.
Used Proton-GE (Proton-4.19-GE-1 -- https://github.com/GloriousEggroll/proton-ge-custom/releases), confirmed it was launching correctly under this version. No noticeable change either!
Toggled amongst windowed fullscreen, fullscreen and windowed modes, but I already run the game under a window manager (LXDE + Openbox) that does not use compositing -- https://dquinton.github.io/debian-install/config/lxde-openbox.html#8 -- so that should not really make a difference. There was no noticeable difference indeed.

Any other tips on what I can do to improve performance without losing detail? It is of note that according to DXVK HUD I am using the GPU at 100% capacity during the game, except during the intermissions of course.

My setup:

System: Host: risadinha Kernel: 5.0.0-23-lowlatency x86_64 bits: 64 Desktop: LXDE (Openbox 3.6.1) Distro: Ubuntu 18.04.3 LTS Machine: Device: desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x serial: N/A UEFI: American Megatrends v: 5220 date: 09/12/2019 CPU: 8 core AMD Ryzen 7 2700 Eight-Core (-MT-MCP-) speed/max: 2873/3400 MHz Graphics: Card: NVIDIA Device 1e84 Display Server: x11 (X.Org 1.19.6 ) driver: nvidia Resolution: 2560x1080@144.00hz OpenGL: renderer: GeForce RTX 2070 SUPER/PCIe/SSE2 version: 4.6.0 NVIDIA 440.26 Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 Drives: HDD Total Size: 8241.7GB (86.3% used) Info: Processes: 424 Uptime: 5:01 Memory: 4311.6/32161.0MB Client: Shell (zsh) inxi: 2.3.56

After @doitsujin asked me for more details, including my in-game settings: My in-game settings: Graphics settings: Resolution: 2560 x 1080 Window Mode: Fullscreen Overall image quality: custom HD Textures: On Show FPS: Off VSync: Off Vertical FOV: 75

Advanced Graphics Settings: Antialiasing: SMAA 1TX Object Quality: Very High Game effects: High Lighting: High Particles: High Physics: High Postprocess quality: High Shader quality: High Shadows: High Textures: High Water details: High Volumetric effects detail: High Vegetation detail: High: Object distance: (about 2/3 of bar) LOD distance: (about 1/3 of bar) Vegetation draw distance: (about 1/3 of bar) Motion Blur: Off

I used both nvidia-smi and nvidia-settings to get the GPU utilization from moment to moment and it was between 98-100% all the time. Curiously, as I am typing now, with the game minimized, nvidia-settings is telling me GPU utilization is fluctuating between 91% and 100%.

I have screenshots of all settings and nvidia-settings and nvidia-smi if you need.

xorgy commented 4 years ago

@Patola For a datapoint, I'd like to just say that I get excellent performance when running KCD on RADV on my Radeon VII; often at or near my 165Hz refresh rate at 1440p, never below about 100fps except during initial shader compilation. I'm running ordinary stable Mesa releases on Archlinux with a 5.3 series kernel.

If you are having performance that bad, it is probably an issue specific to your card/drivers/compositing window manager/something else, and not a general issue with KCD on Proton.

Patola commented 4 years ago

@Patola For a datapoint, I'd like to just say that I get excellent performance when running KCD on RADV on my Radeon VII; often at or near my 165Hz refresh rate at 1440p, never below about 100fps except during initial shader compilation. I'm running ordinary stable Mesa releases on Archlinux with a 5.3 series kernel.

If you are having performance that bad, it is probably an issue specific to your card/drivers/compositing window manager/something else, and not a general issue with KCD on Proton.

I don't think so, my experience is shared by other people who use NVIDIA and I have tried changing driver versions a couple times, as I told in my post. As I also said on the same post, I use a Window Manager without compositing. And as I also said in that post, other games work great - I get more than 200 fps on RE2 and RE7, for example, and close to 100 on the Witcher 3 on ultra. I have more than 100 proton games installed, all but KCD working with full performance.

And this seems something specifically introduced in 1.9 release of the game. I will see if I can get some time to install the last 1.8 patch to see if the performance gets better, but of course almost everybody who buys this game to be played on proton will still use the latest 1.9.4, so if it is indeed some difference from the Windows drivers (which perform great as I have read), it's better to fix that in proton.

Patola commented 4 years ago

To try and give more info... Here's the steam-379430.log I get when I run the game with PROTON_LOG=1, under Proton 4.11-9. steam-379430.log

xorgy commented 4 years ago

@Patola

I don't think so, my experience is shared by other people who use NVIDIA...

That's kinda what I meant to say, without sending out the "NVIDIA's driver is fickle and opaque" vibes that start flame wars. The issue you're describing is at least specific to NVIDIA's Vulkan Driver combined with DXVK combined with the current release of the game.

jarrard commented 4 years ago

Proton-GE can often cause a massive fps cap of about 43ish fps with this game. Try switching to normal proton, test (no need to delete container), then if that fixes the issue try switching back to GE.

I have experienced this terrible performance issue myself and it was just a matter of doing the above to resolve it.

The only benefit for using proton-GE is it switches the keyboard to US or something which allows console use. It might also fix some key bindings, I dunno.

Patola commented 4 years ago

Proton-GE can often cause a massive fps cap of about 43ish fps with this game. Try switching to normal proton, test (no need to delete container), then if that fixes the issue try switching back to GE.

Thanks, but I have tried that not one time, but multiple times. And to different versions of proton and proton-GE too.

I have experienced this terrible performance issue myself and it was just a matter of doing the above to resolve it.

Do you also have a NVIDIA? Which one? How many FPS do you get, what are your settings in-game?

The only benefit for using proton-GE is it switches the keyboard to US or something which allows console use. It might also fix some key bindings, I dunno.

I didn't notice this difference. I was able to use the console under Proton, I think.

jarrard commented 4 years ago

For starters, I have a 1080TI latest drivers, my configuration is going to be wildly different to yours, I play with medium to high settings with SMAA+CAS from reshade(If I remember correctly) AT 4k I get 40-50fps, at 1800p I get 50-60fps (what I use atm).

I have a console issue because my keyboard is not US based, its a Spanish English one, can cause issues at times for some games. Bought it because it was less then half price of the English version one.

PS. I also use mods, custom user.cfg, and optimized graphics mod

Patola commented 4 years ago

Which ones are the latest drivers? Production drivers 440.26 / 440.36 or beta drivers 435.21 / 435.27 ? What's the page of these optimized graphics mod?

jarrard commented 4 years ago

440.31 release drivers https://www.nexusmods.com/kingdomcomedeliverance/mods/743 READ THE INSTRUCTIONS, MOST PEOPLE DON'T AND HAVE ISSUES!

My user.cfg file (-- text is excluded)

``` -- Needs +exec user.cfg in steam launch options -- Bow reticle wh_pl_showfirecursor=1 -- Better Targetting wh_cs_playermaxopponentdistancetolock = 8 wh_cs_playermaxopponentdistancetounlock = 8 wh_cs_playerunlocktimeout = 0 wh_cs_playerverticalunlockdelay = 0 wh_cs_playerhorizontalunlockdelay = 0 wh_cs_playerlockopponentanglebias = 2 wh_cs_playermaxopponentangletolock = 0.8 wh_cs_playermaxopponentangletounlock = 0.8 wh_cs_playerinputcombatunlockdelay = 0 wh_cs_playerinputcursorunlockdistance = 0.05 wh_cs_playerinputlockingtolerance = 20 wh_cs_playerinputlockareawidth = 0.6 wh_cs_playerinputmouseunlockxthreshold = 60 wh_cs_playerinputmouseunlockmintime = 0 wh_cs_playerinputmouseunlockreturntime = 1.5 wh_cs_playerinputmouseunlockminoppangle = 20 -- Ambient Occlusion Fix r_ssdo=1 r_ssdoAmountAmbient=1.4 r_ssdoAmountDirect=2 r_ssdoAmountReflection=4 r_ssdoHalfRes=2 r_ssdoRadius=0.04 r_ssdoRadiusMin=0.07 r_ssdoRadiusMax=0.1 e_svoTI_SSAOAmount=1.545 e_svoTI_SpecularAmplifier=0.82 e_svoTI_TemporalFilteringBase=1 e_svoTI_MinReflectance=0.19 e_svoTI_DiffuseAmplifier=1.12 -- Shadow fix r_ShadowsAdaptionMin = 1.12 r_ShadowsAdaptionSize = 1.28 r_ShadowsAdaptionRangeClamp = 0.008 -- testing, maxfps set so GPU doesn't overheat r_TexMaxAnisotropy = 16 r_antialiasingMode = 3 -- r_antialiasingTAASharpening = 1.3 r_sharpening = 0 r_fullscreen = 1 sys_maxfps = 64 ```

lwho commented 4 years ago

The update from Proton 4.11-10 to 4.11-11 has caused a severe performance regression for me. Where previously I got between 30 and 60 fps I now hardly get 5 fps. I put a self-compiled 4.11-10 into compatibilitytools.d and by using that it's back to normal, so definitely caused by 4.11-11.

GPU: Nvidia GTX 1660 Super Driver: Nvidia 440.44 CPU: i5-3450 (3.1Ghz) RAM: 16 GB Distro: Kubuntu 18.04

user.cfg:

wh_pl_showfirecursor=1
sys_budget_videomem=6000
sys_budget_sysmem=12000
r_TexturesStreamPoolSize=2048
e_ShadowsPoolSize=1024
r_MotionBlur=0
sys_maxfps=30

kisak-valve commented 4 years ago

Hello @lwho, with Proton 4.11-11, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

lwho commented 4 years ago

steam-379430.log (with Proton 4.11-11 run until the main menu; up to 7 fps there)

kisak-valve commented 4 years ago

Possible line of interest from the log: err: D3D11: Cannot map a device-local image

troylights commented 4 years ago

Major performance regression with KCD using Proton 4.11-11 compared to older 4.11 versions. Previously, I got 77-79 fps at the main menu while now I am getting 38-40. In-game framerates (Sasau town and area) in the 20s to 30s, though I can get in the 50s if I look up at the sky. This is at least 50 % lower than what I experienced in earlier Proton 4.11 versions (over 50 hours of gameplay).

Game settings: 1080p, everything on 'high' except medium LOD and shadows, HD sound and textures, 'medium' AA and motion blur. Settings have not been changed for over 40 hours of play time.

System configuration: Ryzen 3 1300x @ 3.6 GHz, RX 580 8 GB, 16 GB DDR4 3200 RAM, 1080p 144Hz adaptive sync monitor, Ubuntu 18.04, 5.0.0-37-lowlatency, Mesa 19.3-ACO (Valve PPA), Feral Interactive's Gamemode (launch option 'gamemoderun %command%').

ghost commented 4 years ago

Only get to try with Proton 4.11-11 so I cannot say that the performance get worse, but it's is terrible nonetheless, I can't get pass 40s fps even on low settings. Although, when I try enabling fsync, the game runs immensely better. screenshot + settings 1080p with HD Texture

Specs: Ryzen 2200G, RX570 4GB, 8GB DDR4 2400 RAM. Manjaro 5.4.3-arch1-1-fsync

jarrard commented 4 years ago

tried with proton-421-ge-2 and well it ran about 1fps lol. Not sure what the issue was, didn't investigate but yeah its broken atm :(

See if I can get fsync installed and going. Tho I don't see why that should be the fix.

jarrard commented 4 years ago

It seems after messing with the graphics settings and changing resolution the performance jumped back up, which was about 44fps on the main menu scene at 4k with medium to high settings.

In game I normally run at 1800p to try and gain a extra 10fps to make up for lost performance by running it via proton and not on native windows.

Keep in mind I'm using a 1080TI, so the issue with general performance regressions might be mostly hitting AMD users.

Patola commented 4 years ago

No news about the performance problem of KCD 1.9 and greater?

jarrard commented 4 years ago

I dunno if I'm experiencing it, try changing resolutions up and down etc.. I think its partially a game bug.

Just tested this out and there does appear to be maybe a performance issue. At 1800p I was getting 25-27fps but normally I get above 50fps in the same area. Not sure what to think.

jarrard commented 4 years ago

YEP Changed resolution from 1440p 1800p 2160p, virtually no difference in performance/framerate, something is going on here for sure!

Ok I seem to have fixed it, a few things to note. 1) When proton updated it decided it would exist on my NTFS drive from now on, this is bad! 2) I deleted the prefix folder (back up saves) and rebuilt it again with the correct proton version selected (which now exists in my ext4 home folder as it should be!)

Now the fps does change when switching between resolutions and is on par with what I got before. With my 1080TI and Medium to high settings @ girlfriends house whatever her name is outside rattay, 1440p ~66fps 1800p ~50fps 2160p ~40fps

The framerate swings in this game are pretty crazy at times depending on where you are and which direction your looking, I've tried to advocate for getting Vulkan happening from the developers but it kept falling on deaf ears, their not interested in upgrading the engine sadly :(

This game is built on cryengine, which supports vulkan!

Patola commented 4 years ago

Tried reinstalling. Even tried to remove remaining shader caches and such and then installed and configured it all from scratch without any mods whatsoever. SAME THING. Same framerate. :-( On the Rattay Tourney, less than 20 fps. That's ludicrous.

jarrard commented 4 years ago

What resolution? I am using the optimized_graphic_presets mod but it doesn't give you that much better fps (maybe 5fps)

The only other thing worth mentioning is I'm using a fsync kernel version (linux-zen). You could also try installing Proton-GE or Proton-TKG builds and test them out to see what happens.

Something is definitely going wrong, it would be helpful if other people chimed in on their experiences.

Patola commented 4 years ago

2560x1080, same one as I said in "my setup" post here -- what changed is that now I am using NVIDIA driver 440.44.

jarrard commented 4 years ago

Yeah I would say you should be getting like 80FPS or close to. I wonder if NVAPI is somehow being enabled in your case.

Patola commented 4 years ago

For some reason performance is now good. Not sure if it is due to the updated nvidia driver or proton itself. Framerate at the Rattay Tourney is exactly double of what is was before. The game is much smoother now, without any difference in the graphical settings. Proton 4.11-12. Also tried Proton 5.0 but the game does not run under it.

AsciiWolf commented 4 years ago

@Patola What happened when you tried to run Kingdom Come with Proton 5.0? Was there any error?

Patola commented 4 years ago

No. It stays a while in the "launching" state then finishes. The screen doesn't even blank. I am attaching the proton logfile for you to see. steam-379430.log

AsciiWolf commented 4 years ago

Interesting. From the log it really seems to be caused by some Wine regression. However, it also looks like you don't have proper Vulkan support.

Patola commented 4 years ago

Interesting. From the log it really seems to be caused by some Wine regression. However, it also looks like you don't have proper Vulkan support.

What? Haha. That's absurd. I use Vulkan since the very beginning and I have almost 200 installed games using dxvk and also lots of native games using the Vulkan API. I use Valve's fsync kernel and my ulimit nofiles is 1048576 just in case esync is used. I am using NVIDIA driver 440.59 and I often turn the "Enable Graphics API Visual Indicator" on nvidia-settings on, so that I can see the game is using Vulkan. I also often use the DXVK HUD which only works with Vulkan.

kattjevfel commented 4 years ago

@Patola do you have any previous workarounds active? Like the one to make it work in 4.11. I just installed KCD and it runs fine without any modifications on my end.

system info tl;dr: Ryzen 1600X + GTX1080, nvidia 440.59 steam-379430.log

Patola commented 4 years ago

@Patola do you have any previous workarounds active? Like the one to make it work in 4.11. I just installed KCD and it runs fine without any modifications on my end.

system info tl;dr: Ryzen 1600X + GTX1080, nvidia 440.59 steam-379430.log

No. I wasn't even aware of these workarounds until you said it (I went on to see it on protondb).

AsciiWolf commented 4 years ago

KCD runs great with latest Proton 5.0-5 on AMD RX 580 with Mesa 20.0.1, however I have noticed a smaller graphical glitch:

![flickering](https://user-images.githubusercontent.com/2339930/79152470-908a3b00-7dcc-11ea-8205-c0c3ea3492c5.gif)

kisak-valve commented 4 years ago

@AsciiWolf, please do not "veto" a moderator edit. Your gif was not removed, it can be shown when clicking on your comment.

AsciiWolf commented 4 years ago

@kisak-valve Oops, I did not notice my post was edited by you. Sorry for reverting your edit.

AsciiWolf commented 4 years ago

Another issue that I just noticed is that I cannot draw a bow. I have both bow and arrows equipped, but pressing "2" to draw a bow does nothing. Do someone else have this issue with KCD under Proton? As far as I know, this should work fine. It can be some configuration issue on my side, but I was not able to workaround this issue so far.

edit: It was caused by a non-English keyboard layout. Remapping the sword/bow keys to F1 and F2 fixed the issue.

AsciiWolf commented 4 years ago

KCD runs great with latest Proton 5.0-5 on AMD RX 580 with Mesa 20.0.1, however I have noticed a smaller graphical glitch:

I just found out that the same issue also happens when running the game on Windows. So, this is definitely a game issue, not a Proton/DXVK/Mesa one. :-)

jarrard commented 3 years ago

Been testing this game out with 6800XT and still experience odd framerate issues.

The silver mine has a overlook towards the prologue area is a good testing area. Sometimes if I stand there the fps will dip to 30-35, if I exit game and reload to exact spot I can get over 60fps... but waiting a minute and it drops to 35fps again...

I just can't figure out what is going on with this game, I suspect wine/proton is flipping out over something and kills the performance randomly.

So right now my game is flipping between 25 and 60+ fps (vsync is on). There isn't a explanation for it.

UPDATE: After doing some reason it seems the engine is just not happy with AMD GPU's. Have yet to find a fix to the bad performance. On average my 1080TI ran better then this 6800XT with this game.

jarrard commented 3 years ago

After extensive testing I've come to believe KCD has a LOD (LevelOfDetail Model/Object) loading issue where it does not cull or unload lods. I believe this to affect AMD users the most.

There are areas of the game where it appear to have issues regardless, but after testing many proton versions and e/f-syncs on/off, and different compilers (aoc/llvm), the issue remained! Which was where walking around would reduce fps performance rapidly so instead of getting 60+ fps you'd get 20-35fps in many areas. (and the fps hit would linger)

There were areas that gave the worse performance in game and I was able to save in the exact spot and reload the game and got my max vsync framerate provided I didn't move about too much. As soon as I walked over to a heavy LOD area and then walked back to the exact original spot, I'd lost 20-30fps or more.

My conclusion is that there is a fundamental game engine bug occurring that probably can't be fixed at the driver end.

NVIDIA users probably don't experience the same issue. I only had a 1080TI prior to this which is not a good 4k test case since it struggled to maintain over 40fps most times anyway. Maybe I'll switch back to NVIDIA come next GPU generation and see what happens.

KCD is no longer being worked on so there won't be any AMD GPU related patches or fixes, this issue is what we get.

PS. Yes this same exact problem is present under Windows10 last time I tried. I have not tested with the past couple AMD driver updates. Will need to do that sometime. Is not related to GPU core/mem clocking bugs, I tested for that also.

Savefile below: Its at the plateau silver mine quarry, if you move to the north-side and overlook the river and starting town its very LOD heavy. Looking side to side and up or down can change the FPS performance dramatically, but you will notice the performance hit can remain as you move back to the original save position. This is evidence of the game struggling to correctly cull loaded in scenery inc lod data. There are many more areas you can test, but this is probably one of the most obvious examples of the issue.

With AMD cards (Navi+ in particular), depending on where you look can dramatically affect performance even when no perceived detail has changed. Its very random and patchy problem which leads one to believe the game is struggling to cull lod/data correctly for some reason.

exit.whs.zip

It MAY be worth opening a ticket over on AMD's bug forum/tracker. But given this is a old game, I very much doubt they will care. (it can also be a cryengine issue as I've read mentions of NAVI users having issues with all cryengine games)

AND that concludes my KCD Navi2 experience. I won't be updating this unless it magically gets resolved under Windows with a driver update, which won't help Linux users but would at least signal that it can be fixed driver side... (unlikely tbh)....

jarrard commented 3 years ago

Tested under windows10 with latest AMD driver. Couldn't get the problem to materialize.

Settings the same, this is the exact viewpoint and area that would murder fps under proton for unexplained reasons. I have FPS capped at 61 here due to vsync. Under linux it would get between 25-40fps at this viewpoint.

Note FPS is 61 (win10) which my monitor is 60hz and I cap it due to tearing. Actual fps could be decently higher but unlikely to be above 75-80fps... win10screenshot

matty-r commented 3 years ago

I've experienced the exact same issues. Previously running with an nVidia GTX 1080ti I would get nearly consistent 100 FPS, i've since upgraded to an AMD RX 6900 XT and barely able to reach 50-60 FPS in most locations.

jarrard commented 3 years ago

KCD isn't the only game affected, but its one of the easier ones to test thanks to its mostly static environments and world.

I've noticed the issue in GTA5 for example, in spots where the FPS would tank (testing at 4k which shows the issue the most). Then directly compared it to windows which has no such issue at all.

I believe I also had this issue in CP2077 but that game has performance issues built in and such so it was really hard to nail down what was causing it most the time. (the game or driver/gpu/mesa)

jarrard commented 3 years ago

For completion-ism here is a screenshot of how it runs on Linux, same settings. I have tried different mesa versions, difference window rules such as with and without compositor etc... Lots of things tried. Sometimes it will be 35fps but is pretty random patchy performance.

Note FPS is 25fps. Game is not enjoyable with this performance issue. KCD Linux Performance Issue 6800xt

matty-r commented 3 years ago

I've learnt this is a problem with AMD GPUs and CryEngine games, and had been for years. This also affects Windows. Unfortunately it's AMD not caring about it and not fixing the issue, and likely never will. It's been around since the Vega 64.

I've returned my card. Pretty garbage.

jarrard commented 3 years ago

Having e/f sync enabled and using newer proton versions such as experimental can yield a extra 9fps or so. Still WAY too slow to be playable, even if its patchy, having the game randomly dip down to 25-35fps every time you turn around or look in a specific direction is beyond frustrating.

This also affects Windows. Unfortunately it's AMD not caring about it and not fixing the issue

The latest AMD windows10 drivers appeared to have fixed this issue. I posted a screenshot as evidence, but who knows if their next driver update will break KCD or cryengine games again.. Seems the fix isn't in for Linux mesa amdgpu drivers... if its the same problem (which I'm pretty sure it is, whatever it is...)

There may also be issues with Unity3D games, but I've yet to fully confirm that. Only Unity3D games I've tested recently were Battletech and Pillars2. But they also have a slew of other issues to consider when performance testing making the overall process difficult to do basic problem isolation.

Eventually I might consider getting my second ITX system up and running and slap a decent NVIDIA card in it for testing purposes.

matty-r commented 3 years ago

Ah well - I've given up on it. I've never had issues like this with NVIDIA so I'll just wait and get a 3080 at some point.

Patola commented 3 years ago

what's e/f sync?

ValveSoftware / Proton

Kingdom Come Deliverance (379430) #692

My setup: