search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.47k stars 1.07k forks source link

Control Ultimate Edition (870780) #4157

Open olav-valle opened 4 years ago

olav-valle commented 4 years ago

Compatibility Report

System Information

I confirm:

steam-870780.log

Symptoms

Generally low performance, though seemingly close to ready for whitelisting.

Game is stuttering (seems like a frametiming issue) almost constantly, with frequent hitches (though these are probably caused by shaders still being cached).

On medium settings at 1440p the performance on a GTX1080ti and i9 9900k is lower than seems reasonable (hovering around 50-55FPS), considering the recommended specs are a GTX 1060 and an i5.

Possibly also experiencing some artifacting in regards to reflections and transparency appearing low res/grainy, but this has not been compared visually to native. The severity of this seemingly comes and goes, and I haven't found a reliable way to reproduce it yet. See screenshots. The silver/white particles on jacket, hair, edges or reflective surfaces of various objects, and entire floor in background of second image.

Before artifacting: 870780_20200828003156_1 870780_20200828003222_1

After artifacting: 870780_20200828000811_1 870780_20200828000823_1

Also, the game really doesn't like being alt-tabbed.

Reproduction

Click play.

McMarius11 commented 4 years ago

the performance for me is also not great, please rename in the main game folder Control_DX11.exe to Control_DX12.exe. this fixed the stuttering for me, the game will now use the DX11 exe.

Proton Proton-5.9-GE-5-ST Distro: Manjaro Linux Kernel: 5.8.1-3-MANJARO RAM: 24 GB GPU Driver: NVIDIA 450.56.06 GPU: NVIDIA GeForce GTX 1070 CPU: Intel Core i5-7600K @ 3.80GHz

olav-valle commented 4 years ago

the performance for me is also not great, please rename in the main game folder Control_DX11.exe to Control_DX12.exe. this fixed the stuttering for me, the game will now use the DX11 exe.

If you rename the DX11.exe, the game won't start because of a 'file not found' error for the DX11.exe file. Are you sure you have this right? Do you mean rename DX11 to DX12, and DX12 to DX11?

McMarius11 commented 4 years ago

the performance for me is also not great, please rename in the main game folder Control_DX11.exe to Control_DX12.exe. this fixed the stuttering for me, the game will now use the DX11 exe.

If you rename the DX11.exe, the game won't start because of a 'file not found' error for the DX11.exe file. Are you sure you have this right? Do you mean rename DX11 to DX12, and DX12 to DX11?

yes, I renamed the DX11.exe to DX12.exe and DX12.exe to DX11.exe then the game will use the DX11.exe which is named DX12.exe

it still stutters but its much better then with the DX12.exe

i would recommend installing the Nvidia 450.66 driver disabling Global Reflection might also help

Saancreed commented 4 years ago

I'll never understand why people keep renaming executables (which will probably be undone by every game update), but oh well. In case of Control, you can actually append -dx11 or -dx12 to your launch options to bypass the launcher / feature detection logic and force it to immediately start your choice of Control_DX11.exe or Control_DX12.exe instead.

I believe for this game using d3d11 with DXVK is recommended over d3d12 with vkd3d, but your mileage may obviously vary. Right now DXVK might have some additional stuttering, but should be more stable than vkd3d and over time the stutters will be reduced due to Fossilize kicking in.

RiantAnda commented 4 years ago

The issues shown in the screenshots in the first post are also present on Windows with DX12. These are not Proton issues. To get ride of those, "Global Reflections" has to be set to "OFF" in the "Display" tab under "Options".

sebastian-de commented 4 years ago

The game is playable with -dx11 and medium graphics settings on a Radeon RX570 here (Arch Linux, linux-zen, mesa-git). Performance could be better, but one of the Valve-hired Mesa developers seems to be on track to improve that:

Significantly improves performance of a Control compute shader. Also seems to increase FPS at the very start of the game by ~9% (RX 580, 1080p, medium settings, no MSAA).

from https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6558/diffs?commit_id=4baea6ce0921f9060649f98045f2b9db76dc87e2

xTeixeira commented 4 years ago

I can't alt tab out of this game. The game window instantly comes back to the top. I'm running GNOME on Xorg, Arch Linux.

Also, the game doesn't launch when using Proton 5.13-1. Proton 5.0-9 works fine except the alt tabbing issue.

jrgp commented 4 years ago

I get very good perf for this game using Proton 5.0-9 without any additional changes/command line args. (Except I have mangohud)

FPS: 110-150 Nvidia driver: 455.23.04 GPU: RTX 3080 CPU: AMD 3950x Ram: 64GB Kernel: custom compiled 5.6 Ubuntu 20.04

I have not tried alt-tab

joshas commented 3 years ago

Having strange issue with this game on AMD RADEON 5600XT, with Proton 5.13-4 and 5.0-10. After varied amount of time (from minutes to hours) game freezes and displays last frame with pixelated streaks of red, green and blue pixels randomly(?) splattered across the screen. Freezes happen not always, got quite a few gaming sessions without any issues. CPU and GPU temperatures are decent, freezes happen on any graphic detail level. control-freeze

Related error messages from system log:

kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=7794353, emitted seq=7794355
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Control_DX11.ex pid 26902 thread Control_DX:cs0 pid 26941
kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset begin!
kernel: amdgpu 0000:0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed
kernel: amdgpu 0000:0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed
kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
kernel: [drm] free PSP TMR buffer
kernel: amdgpu 0000:0c:00.0: amdgpu: GPU BACO reset
kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset succeeded, trying to resume
kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
kernel: [drm] VRAM is lost due to GPU reset!
kernel: [drm] PSP is resuming...
kernel: [drm] reserve 0x900000 from 0x817e400000 for PSP TMR

Has anyone seen anything similar? Any ideas how to figure out what exactly causes this freeze?

kisak-valve commented 3 years ago

Hello @joshas, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Was the game working without issue in the past or have you been seeing this issue as long as you've been playing the game?

joshas commented 3 years ago

Here's the Steam System Info and I got Proton log too, but I cannot find any related error messages in it.

This is my first play-through of this game, I've purchased it just last week. Looking at reports from other players I expected a crash or two, but now I'm interested, if this issue is specific to my hardware setup only, or not? Only other occasion I've seen similar issue on my system was playing Ori and the Will of the Wisps (1057090), but there was only one or two freezes in total; screen just went full black and similar pixelated pattern appeared. Of course from that time Proton and my OS got few updates.

hollisticated-horse commented 3 years ago

Replying to https://github.com/ValveSoftware/Proton/issues/4157#issuecomment-746699083

hey there, i've similar problems but in blender for some reason ? same thing, crash, black screen for a few seconds, then a frame with weird artifacts... RX 5700XT

hollisticated-horse commented 3 years ago

heya, been having problems with the game... i have a freeze and then a weird window opens and tells me the following :

File IO failure: readFileFailed, error code 21, filename Z:\mnt\sdb1\steamapps\common\Control\data_packfiles\ep100-000-pc.rmdp

File IO failure: openFileFailed, error code 998, filename renderer.ini

i can cycle between the two with a retry and exit button

(i have a few screenshots)

Has happened every time i've played. Other then that, i confirm i also have the particule artifact same as original issue, though maybe less.

I have changed from 5.0 to 5.13, same issue.

joshas commented 3 years ago

@hollisticated-horse I've been getting same issue (freeze with pixelated frame) in native Linux games too, but got that partially fixed by switching from Wayland to Xorg. Although I still managed to get same freeze, but only once in about 30 hours of total gameplay. Probably video driver issue, as there are issues with same bug descriptions on mesa and amdgpu repositories, so Proton is not at fault here.

hollisticated-horse commented 3 years ago

@joshas yeah probably true, been talking with the guy how maintains the amd linux-firmware ppa, couldn't find an explanation either...

That said, is it better ?

(for my own issue, i'm looking into a faulty ssd :P// could it be that ? )

hollisticated-horse commented 3 years ago

okay, so i've installed the game on my hdd, to see if the ssd was at fault for the sudden crash, and i'm getting a :

Wine C++ Runtime Library : Runtime error!

Program: Z:/home/'user'/.local/share/steam/steamapps/common/Control/Control_DX11.exe abnormal program termination Press OK to exit the program, or Cancel to start the Wine de bugger.

I'm on Ubuntu 20.10, using proton 5.13.

help ?

Edit: i'm hearing sound from the game ... the game window is stuck on loading the game. I can access the game menu but not the game itself ...

Edit 2: @kisak-valve should i start a new issue ? i'm not using the same GPU and system as the initial post.

kisak-valve commented 3 years ago

Hello @hollisticated-horse, in general, we're using one issue report per unofficially supported game title. This is the right place to discuss everything related to Control Ultimate Edition when run with Proton.

Please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

hollisticated-horse commented 3 years ago

steam-870780.log @kisak-valve here's the log file. Same error as mentioned above. Anything else that might help ?

hollisticated-horse commented 3 years ago

aha, progress !! I think my ssd was dead or dying or just not mounted properly mounted ... So now my game just plain old crashes on an HDD... and still got the weird artifact from before, as in same as the original issue.

i'll try to replicate the crash with PROTON_LOG=1 %command%.

any suggestion to help me debug ? i have no clue what i should be working on...

hollisticated-horse commented 3 years ago

And got a good old green screen and crash. Still those AMD gpus not functionning correctly

steam-870780.log

axelgenus commented 3 years ago

I can't run this game with Proton 5.13-5 but it work flawlessly with Proton 5.0-10. Performances are not great but it's mostly playable/enjoyable ;)

The regression seems to be related to pressure-vessel because it fails with the following error: pressure-vessel-wrap[44654]: openat(/proc/self/fd/21): Too many levels of symbolic links

Anyone has the same problem? I remember having a similar issue with the Flatpak version and I had to use the Proton community package, built w/o pressure-vessel.

hollisticated-horse commented 3 years ago

hey @axelgenus, i don't have that. I'll give 5.0-10 a try.

I've had a couple of errors with sometimes DirectX11, sometime for no reason crash... Seems to fuck up my drive though, since i need to fsck at reboot because of inode issues...

ChemiKyle commented 3 years ago

Game launches on my system, menu works fine. Upon starting a new game, screen remains black, I sometimes get dialogue, and computer freezes, requiring me to power cycle. I have tried a handful of different proton versions (4.11, 5.0, 5.13, experimental, WineHQ staging 6.3 via lutris) and flags, if the game launches at all it results in a total system freeze (though I still get sound if there was sound).

Attached is a log using the -dx11 flag and the output of "Help > System Information" as a .txt file.

steam_system_info.txt steam-870780.log

There is a lot of noise from 388:fixme:d3d12_swapchain_GetFrameStatistics: iface 00000000073bbd40, stats 000000003583fcd8 stub!

My issue likely stems from the Humble Bundle "standard" release not separating DX12 and DX11, there is only DX12 at time of posting: https://steamcommunity.com/app/870780/discussions/0/3103515084616505152/

aqxa1 commented 3 years ago

DX11 support is back today.

gadanidis commented 3 years ago

Out of the box, the game fails to launch on my machine, apparently due to a failure to load mscoree.dll. The attached log is with 5.0-10 but I've tried several different Proton versions (6.3-1, 5.13-6, 5.9-GE-8-ST, and others) and get the same error. Relevant lines from the log:

511.103:00d4:00d8:err:module:fixup_imports_ilonly mscoree.dll not found, IL-only binary L"Control.exe" cannot be loaded
511.103:00d4:00d8:err:module:LdrInitializeThunk Importing dlls for L"Z:\\home\\tim\\games\\steam\\steamapps\\common\\Control\\Control.exe" failed, status c0000135

mscoree.dll does exist in the prefix so I'm not sure why I'm getting this error. The game itself seems to work fine if I rename Control_DX11.exe to Control.exe, replacing the original Control.exe, so this seems to just be a problem with the launcher or something. (The suggestion above to use -dx11 or -dx12 did not work for me, only renaming the files worked.)

steam-870780.log

Please disregard this, it was just a configuration problem on my end. For some reason I had mscoree in WINEDLLOVERRIDES in my .profile. Not sure when I did that or why but the launcher works fine now that I've removed it.

ghost commented 3 years ago

The game is working fine in DX11 for me. My problem is when i activate DXR function in VKD3D, it was working fine 2 days ago. Now the game doesn't launch with RT.

OS: Manjaro Gnome 21.0.4
Kernel: 5.12.2-153-tkg-bmq
GPU: NVIDIA RTX 3080 (465.27)
CPU: I7 9770K

steam-870780.log

New log with WINEDEBUG=+vulkan VKD3D_DEBUG=trace %command% steam-870780_debug.log

D33M0N commented 3 years ago

game started fine, but crashed at some point with ...

mai   21 13:03:54 Zen kernel: [drm:gfx_v9_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream
mai   21 13:03:54 Zen kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=7025582, emitted seq=7025584
mai   21 13:03:54 Zen kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Control_DX11.ex pid 13387 thread Control_DX:cs0 pid 13487
mai   21 13:03:55 Zen kernel: amdgpu: [powerplay] Failed to send message: 0x63, ret value: 0xffffffff
mai   21 13:03:55 Zen kernel: amdgpu: [powerplay] Failed to send message: 0x26, ret value: 0xffffffff
mai   21 13:03:55 Zen kernel: amdgpu: [powerplay] Failed to send message: 0x61, ret value: 0xffffffff
mai   21 13:03:55 Zen kernel: amdgpu: [powerplay] Failed message: 0x37, input parameter: 0x0, error code: 0xffffffff
mai   21 13:03:55 Zen kernel: amdgpu: [powerplay] Failed to send message: 0x63, ret value: 0xffffffff
mai   21 13:03:55 Zen kernel: amdgpu: [powerplay] Failed to send message: 0x26, ret value: 0xffffffff
mai   21 13:03:55 Zen kernel: amdgpu: [powerplay] Failed to send message: 0x61, ret value: 0xffffffff
mai   21 13:03:55 Zen kernel: amdgpu: [powerplay] Failed message: 0x37, input parameter: 0x0, error code: 0xffffffff
mai   21 13:03:56 Zen kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
mai   21 13:03:56 Zen kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
mai   21 13:03:56 Zen kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
mai   21 13:03:56 Zen kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
mai   21 13:03:56 Zen kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
mai   21 13:03:56 Zen kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
... (a lot more of those lines)

could be mesa bug though. or kernel or somthing else...

mesa-git 21.2.0_devel.139848.307139c7f94-1
kernel: 5.12.2-1-MANJARO
GPU: Vega 64
hakzsam commented 3 years ago

@D33M0N Is this a recent regression? The "Illegal register access" error is pretty bad.

D33M0N commented 3 years ago

@D33M0N Is this a recent regression? The "Illegal register access" error is pretty bad.

Dunno, Installed Control first time yesterday. Was able to play like half an hour or so fine, until this.

hakzsam commented 3 years ago

@D33M0N Is this always reproducible? that error means the driver emits an invalid register, should be easy to fix if I can reproduce myself.

D33M0N commented 3 years ago

@hakzsam dunno again, managed to do it second time also. Just when you come out of the first "mind game" floating boxes place with your brand new gun, and start exploring the floor and shooting random things and walls and stuff, then it just happens sooner or later. Previous 2 crashes were with the default proton for Control ... 5.13 I assume. Will try different proton version now.

silversquirl commented 3 years ago

The game runs great for me, but strangely seems to steal focus back whenever I try to defocus it. This happens in both full screen and borderless modes, but not windowed mode. Opening the steam overlay lets me defocus it, but focus will still occasionally flicker to Control and back. The game (and overlay) also seems to freeze sometimes due to being defocused, requiring pkill -9 Control - not sure what specifically causes it though.

the-black-wolf commented 3 years ago

I have new NVidia 470.57.02 drivers and I use the latest release and experimental versions of proton. However, the game still does not recognize my 2080Ti as DLSS and RTX enabled. Is there some switch to enable the features now that the driver has them?

RiantAnda commented 3 years ago

@the-black-wolf AFAIK you need to enable DLSS and DXR(raytracing) in the "LAUNCH OPTIONS" of the game at the moment: VKD3D_CONFIG=dxr %command% -dx12 -> Enables DXR and forces the DX12 version of the game, works for me. PROTON_ENABLE_NVAPI=1 %command% -dx12 -> Should enable DLSS, but the game doesn't launch with this option.

misyltoad commented 3 years ago

In Proton Experimental I get weird view snapping in Control which doesnt happen in Proton 6.3

I also get weird flickering when playing and the game covers the full screen in fullscreen or borderless (fshack bug perhaps? or compositor?? need to check...)

Does the view snapping happen for anyone else on experimental?

misyltoad commented 3 years ago

Flickering appears to be my compositor (KWin) somehow, having a window over the game fixes that.

alasky17 commented 3 years ago

@Joshua-Ashton I'm not sure exactly what you mean by view snapping? Could you get a video or describe what you are doing to trigger the behavior?

misyltoad commented 3 years ago

Seems to only happen under KDE Wayland actually... Wasn't able to get a video because no screen capturing works there. Hm...

kisak-valve commented 3 years ago

Hello @joshas, are you still seeing the issue you reported at https://github.com/ValveSoftware/Proton/issues/4157#issuecomment-746699083? Mesa 20.2.3 is fairly outdated at this point, so it'd be nice if you could retest with a current point release or git main.

joshas commented 3 years ago

Kernel Version: 5.13.13-200.fc34.x86_64 Driver: AMD AMD Radeon RX 5600 XT (NAVI10, DRM 3.41.0, 5.13.13-200.fc34.x86_64, LLVM 12.0.1) Driver Version: 4.6 (Compatibility Profile) Mesa 21.1.7 Proton 6.3-6 GNOME + Wayland

Played for about an hour, first on medium graphics setting, then tried on maximum. Ran around various locations using end game save, got into battles - could not reproduce the issue. I can only hope, that issue was actually fixed.

kisak-valve commented 3 years ago

Thanks for retesting. Between your feedback and https://gitlab.freedesktop.org/mesa/mesa/-/issues/4820, it looks like there's no currently known issues between this game and mesa/RADV, so I'm dropping the corresponding labels.

davegorst commented 3 years ago

This previously worked, but now gives me :

System.ArgumentException: XOR data length expected 2046820352, read 3830

While trying to start up. Tried on 2 different machines - one nVidia/Intel and my main AMD machine. Forcing the DX12 version with -dx12 results in it starting correctly.

davegorst commented 3 years ago

Also setting VKD3D_CONFIG=dxr11 is needed to enable raytracing on AMD.

gkeep commented 3 years ago

Crashes while launching with DX12 on Fedora 35. I can see the game opening to fullscreen, but it crashes immediately. Tried with Proton Experimental and Proton-6.20-GE-1. Possibly Vulkan related as I have had DOOM Eternal, F1 2020 (DX12) and Cyberpunk 2077 crash on me similarly.

steam-870780.log (Proton Experimental) steam-870780.log (Proton-6.20-GE-1)

Game runs with DX11 with input lag.

Kernel: 5.14.14-300.fc35.x86_64 GPU: NVIDIA GeForce GTX 1650 SUPER Driver: 470.74.0 Mesa: 21.2.5-1.fc35 DE: KDE Plasma 5.23.2 X11

kisak-valve commented 3 years ago

Hello @gkeep, these look like the lines of interest from your log:

01a4:info:vkd3d_config_flags_init_once: VKD3D_CONFIG='dxr'.
01a4:info:vkd3d_get_vk_version: vkd3d-proton - applicationVersion: 2.5.0.
01a4:info:vkd3d_instance_init: vkd3d-proton - build: 8ff91b23d61a10c.
01a4:err:vkd3d_create_vk_device: Failed to create Vulkan device, vr -3.
01a4:fixme:hresult_from_vk_result: Unhandled VkResult -3.

It might be interesting to test how the game behaves without force enabling dxr with vkd3d-proton. If my memory is correct, nVidia 16xx cards do not have discrete hardware for ray tracing.

gkeep commented 3 years ago

If my memory is correct, nVidia 16xx cards do not have discrete hardware for ray tracing.

You're correct. They are not RTX-capable.

Here are logs without force enabling dxr (launch options are PROTON_LOG=1 %command% -dx12): steam-870780.log (Proton Experimental) steam-870780.log (Proton GE)

EDIT: Looks like the same vkd3d error output as in previous logs.

Proton Experimental, line 1284

01ac:info:vkd3d_get_vk_version: vkd3d-proton - applicationVersion: 2.5.0.
01ac:info:vkd3d_instance_init: vkd3d-proton - build: 8ff91b23d61a10c.
01ac:err:vkd3d_create_vk_device: Failed to create Vulkan device, vr -3.
01ac:fixme:hresult_from_vk_result: Unhandled VkResult -3.
AlexP11223 commented 3 years ago

It seems like the game uses more VRAM than on Windows, which causes issues with the mod fixing blurry textures/texture pop-in on DX12. https://www.reddit.com/r/linux_gaming/comments/qmtlng/blurry_textures_in_dx12_control_fixable_by_mod_on/

Is it expected for VKD3D? Is there any way to optimize VRAM usage?

gkeep commented 2 years ago

Here are logs without force enabling dxr (launch options are PROTON_LOG=1 %command% -dx12): steam-870780.log (Proton Experimental) steam-870780.log (Proton GE)

EDIT: Looks like the same vkd3d error output as in previous logs.

01ac:info:vkd3d_get_vk_version: vkd3d-proton - applicationVersion: 2.5.0.
01ac:info:vkd3d_instance_init: vkd3d-proton - build: 8ff91b23d61a10c.
01ac:err:vkd3d_create_vk_device: Failed to create Vulkan device, vr -3.
01ac:fixme:hresult_from_vk_result: Unhandled VkResult -3.

Looks like I was missing some Vulkan dependent packages. Most notably xorg-x11-drv-nvidia-cuda which fixed my issue with Vulkan and DX12 in Control, Doom Eternal and F1 2020 (DX12).

kisak-valve commented 2 years ago

Control Ultimate edition Stuck in mission = cant finish game

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5994. @mushroomeo posted on 2022-07-14T13:33:12:

Compatibility Report

System Information

I confirm:

PROTON LOG: steam-870780.log

Symptoms

getting stuck by talking with npc. so cant progress/finish game i can rorate camera and and go in menus but nothing happening else. the npcs just standing and no doalogue. = stuck

Reproduction

just do the mission: my borthers keeper, find dylan. and talk to the npc after running through white bridge...

https://user-images.githubusercontent.com/9019563/178994150-e9350a8e-2659-4220-b0a7-a1fd0570db73.mp4

b7useyl

trying verify integrity of game , tryed different protons, tryed find in internet about if someone got same bug, nothing seems to work , its proton or game bug i cant test since i dont have windows OS anymore.

Calinou commented 1 year ago

On i9-13900K + RTX 4090 (NVIDIA 530.41.03), stuttering still seems very present on the latest Proton Experimental, both in DX11 and DX12 mode (with or without raytracing or DLSS). This is in DX11 mode for instance, trying to reach 120 FPS V-Sync while looking at a wall:

image

Disabling V-Sync doesn't improve the situation. This doesn't appear to be shader compilation stutter, as it remains persistent for several minutes in the intro sequence (even if I stand still and do nothing). Even setting the game to its absolute lowest settings and 960×540 render resolution still doesn't yield a stable 120 FPS in DX11 mode (it's as unstable as in the graph shown above).

Note that I'm also using this patch.

Edit: On the same PC, the game runs very smoothly on Windows 11, even with the patch and raytracing enabled.