Juste Cause 2 is a DirectX 10 game and I think Proton does not integrate yet the DirectX 10 feature from DXVK (look at the changelog). Anyway, Just Cause 2 is too unstable to be playable with last Wine version and DXVK https://github.com/doitsujin/dxvk/issues/567.

Using Proton 3.16-1 Beta Just Cause 2 can be launched after several attempts.

Overwhelmingly unstable, despite great performance (constant 60 fps).
If anyone wanted to give it a try, here is some hints (noticed when tested earlier DXVK d3d10):

• don't try to disable vsync, more fps - more frequent crashes
• HBAO, SSAO and VSync are unstable options, use /FailSafe command-line parameter to restore
• use e.g. /HBAO=0 /FramerateCap=30 /SSAO=0 /VSync=1 command-line parameters for longer sessions
• more info : https://pcgamingwiki.com/wiki/Just_Cause_2

I am using Proton 3.16-2 Beta. still unable to launch it
here be the log

System info:

PROCESSOR:          Intel Xeon E5-1607 0 @ 3.00GHz
    Core Count:       4
    Extensions:       SSE 4.2 + AVX
    Cache Size:       10240 KB
    Microcode:        0x714
    Scaling Driver:   intel_pstate powersave

GRAPHICS:           Gigabyte NVIDIA GeForce GTX 750 Ti 2048MB
    Frequency:        1032/2700MHz
    OpenGL:           4.6.0
    Display Driver:   NVIDIA 410.57
    Monitor:          DELL 1908FP
    Screen:           1280x1024

MOTHERBOARD:        INTEL X79
    BIOS Version:     4.6.5
    Chipset:          Intel Xeon E5/Core
    Audio:            Realtek ALC662 rev3
    Network:          Realtek RTL8111/8168/8411

MEMORY:             16384MB

DISK:               160GB Western Digital WD1600JD-55H + 200GB SAMSUNG SP2004C
    File-System:      ext4
    Mount Options:    relatime rw
    Disk Scheduler:   CFQ

OPERATING SYSTEM:   Arch rolling
    Kernel:           4.18.11-arch1-1-ARCH (x86_64)
    Desktop:          KDE Plasma 5.13.5
    Display Server:   X Server 1.20.1
    Compiler:         GCC 8.2.1 20180831 + Clang 7.0.0 + LLVM 7.0.0 + CUDA 10.0
    Security:         KPTI + __user pointer sanitization + Full generic retpoline IBPB IBRS_FW + SSB disabled via prctl and seccomp Protection

The Game doesn't launch for me as well. In the log file is a trace. steam-8190.log

None of the parameters posted by @pchome helped.

Sysinfo: https://gist.github.com/NoXPhasma/0342aabb8fe583a36509c772718c179d
Proton: 3.16-3 Beta

@NoXPhasma
can be launched after several attempts means dozens (sometimes), where it mostly crashing on loading screen for me.

I'm not going to smash the launch button just to be lucky at some point. If you look into my log file, you will see that there is a trace, so something wents really wrong and needs to be fixed or considered to be garbage.

If you look into my log file, you will see that there is a trace, so something wents really wrong and needs to be fixed or considered to be garbage.

Backtraces for this game are considered useless, even when I launch this in environment full of debug symbols -- I can see different points every time.

Backtrace:
=>0 0x7c0da0ce _ZN4dxvk18D3D11DeviceContext15BindFramebufferEi+0x28e() in d3d11 (0x0313fbd8)

Backtrace:
=>0 0x7c0e17e6 _ZN4dxvk21D3D11ImmediateContext9MapBufferEPNS_11D3D11BufferE9D3D11_MAPjP24D3D11_MAPPED_SUBRESOURCE+0x186() in d3d11 (0x0032f1c8)

Backtrace:
=>0 0x7c0b1072 _ZN4dxvk18D3D11DeviceContext18BindShaderResourceEjPNS_23D3D11ShaderResourceViewE+0x52() in d3d11 (0x0302f948)

and so on.

I'm not going to smash the launch button just to be lucky at some point.

Aaa..nd you shouldn't.

Here's a log from Proton 3.16-4 Beta
steam-8190.log

still no joy.

Fun fact: the game now works for PROTON_USE_WINED3D11=1 (aka DXVK disabled).

I successfully launched it three times in a row, just for curiosity.

d3dx10_42, d3dcompiler_43, d3dcompiler_47 are set to native

@pchome does not work for me. Then Winetricks can not install d3dcompiler_47, how did you install it?

I copied it from another prefix into game's directory.
But you can try winetricks from git. There is d3dcompiler_47 verb.

The game is stable for me with DXVK built from current git master.
SSAO should be disabled.

FPS =~50-60 with everything maxed (except AF/AA).
GPU Water Simulation wouldn't work, due to missing D3D10 implementation in nvcuda (this option will only appear if you using nvapi).

Also, see above referenced issue, if you trying to launch the game on odd days :face_with_head_bandage: .

Just Cause 2 crashes at startup for me as well. I added PROTON_LOG=1 %command% to the game's launch options and received the following log:

steam-8190.log

My system:

https://gist.github.com/Simmonz/43bcff5808cdb180aa995542353a6bb6

Good news... sorta. Proton 4.2 loads it to a black screen (doesn't crash beforehand at least). Had to Alt F4 and wait for the window manager to offer to kill the process.

steam-8190.log

Good news... sorta. Proton 4.2 loads it to a black screen (doesn't crash beforehand at least). Had to Alt F4 and wait for the window manager to offer to kill the process.

steam-8190.log

Proton 3.16-8 beta has always lead to a black screen on Just Cause 2 for me. Takes 2-3 minutes for the screen to load up though.

The game is fully functional on wine 3.21 and above (oldest version I tested) so this is definitely a proton issue.

There's some talk on here about the game being unstable with certain options selected. I don't use vsync, but the game runs butter smooth with everything as high as they can go on Nvidia's latest drivers in regular wine.

I tested JC2 with Wine 4.2 staging (Lutris version) + Steam for windows. The game launched and I can go to the aim menu and launch a demo.
With Proton 4.2 nothing happened.
I joined you the Proton log.
steam-8190.log
https://gist.github.com/legluondunet/8570a65372c3f7b9fea9c365c449cc59

@tsalwierz Ahh thanks. I thought I had tried on 3.16 and was getting the instant crash. Good to know.

Proton 4.2-3 still no joy getting it to run.
steam-8190.log
https://gist.github.com/lucifertdark/584c14275612e8e3c4a8070d428d8a02

It works with a cracked .exe and then install with protontricks: d3dcompiler_43, d3dcompiler_47 and d3dx10.
It's not a good thing to use a cracked exe, I hope this DRM will be supported.

The DRM is, with no surprise, CEG. See https://github.com/ValveSoftware/Proton/issues/753

This game seems to work with recent Wine-Saging 5.5 version (and so soon in a future Proton version?).

After a lot of tests, I can finally launch this game (steam version).
If you own the game on Steam, try this recipe:
Install Windows Steam client in a 64 bits wineprefix, then you have to install some dll with winetricks:
winetricks d3dcompiler_47 d3dx10_43
and not use wine vanilla but wine-staging 5.5.

After some debugging myself, I can confirm the game crashes in Proton due to the Steam DRM working improperly. Code that should get mapped to a certain address doesn't, and the game crashes on an invalid instruction due to this.

Even once that's fixed, it tries to compile shaders that are unsupported with Wine's current built-in d3dcompiler and ends up hanging at a black screen. Hopefully this adds some context for anyone trying to work on this in the future.

I'm curious if this game will end up working on the Steam Deck. Valve did say they couldn't find a game that didn't just work.
Does that mean there's an in-house Steam build with the necessary DRM-implementation in place?

Works for me on latest beta client and experimental proton. Just had to run some proton fixes to fix direct x issue.

Just had to run some proton fixes to fix direct x issue.

@smintman What DirectX issues are you talking about? I made the game work with DXVK back in 2019, are there any issues with it now?

Can’t remember the exact error but was something about Direct x 10 fatal error

Looked in proton db and some where suggesting

using

protontricks 8190 dlls d3dx10 d3dcompiler_43 d3dcompiler_47

Which did the trick and ran amazingly. If I could run it without using the above proton ticks that would be even better?

steam-8190.log

Seeing a black screen, then a crash when using, after running the protontricks.

I have gotten the game to work properly including a workaround for the game staying permanently minimized. The game seems to detect the xbox 1 controller ok as an option menu shows up for x360 controller. The benchmark tool runs. I didn't actually play the game yet though.

Currently you need to switch Proton Experimental to the "bleeding-edge" beta. Then set the following launch options for the game.
PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% /borderless=1
Then in steam re-validate the game files then launch it. Launch is kinda slow but it works. :+1:
Esync or Fsync may actually work with CEG but I didn't test. Benchmark showed the game running at 144fps at max settings already.

Note that at least for me the game will be permanently stuck minimized if you don't use the borderless command line switch option. This may work differently depending on DE or number of monitors connected. The game doesn't have a borderless switch in the game, just fullscreen on/off so you have to set it on command line. The game has a binary settings file so even if you could set borderless in the settings file it would be difficult.

Edit: also I had ran "protontricks 8190 d3dx10 d3dcompiler_43 d3dcompiler_47" on the prefix.

Actually, i had to flatpak install flathub com.github.Matoking.protontricks and after had to flatpak run com.github.Matoking.protontricks 8190 d3dx10 d3dcompiler_43 d3dcompiler_47 But i confirm, i can open it.

I did not have to "PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% /borderless=1" yet.

I did some test on the campain, it's did go well untill the Casino. Unfortually, i do freeze a lot, had to restart the pc many times. I did try "PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% /borderless=1" Not but changes. I will wait for @BillFleming to get pass the Casino to see if he also have issues.

Apparently, my problem wasn't Wine-Proton based but windows players also have it.

There is the solution : https://steamcommunity.com/app/8190/discussions/0/154644598510833416/?ctp=23

I did disabled Decals & Bokeh Filter.

Probably that the Casino scene had more gunfights and action than the precedent scenes.

protontricks 8190 dlls d3dx10 d3dcompiler_43 d3dcompiler_47

After running this command (this is a prerequisite for DXVK's DX10 support, IIRC) the game is playable.

Proton Experimental with the protonricks from above it gets to splash screen for 1 second and then crashes out

https://gist.github.com/parkerlreed/42118febd90183f763b087bdf25d763c

steam-8190.log

Seems to bail at ERROR: Could Not Get Primary Adapter Handle right after wine's built-in avrt.dll audio?

EDIT: Finally got a popup saying fatal DirectX error (Same log entries) after switching back to Experiemental.

Trying WWINED3D ends in the same errors but spits out some more info about typeless format errors.

steam-8190.log

I don't know what it is or what it was, completely uninstalling the game and prefix, reinstalling, and using the protontricks from above has finally made this game work.

If it's not one thing it's another... Was able to play a little bit into the tutorial with no issues. Very shortly after getting the first gun and then hopping on the turret to take out helicopter, a weird mouse issue appears.

Anytime the mouse is moving (which is a lot in an FPS...) the frame rate drops to 0. Stop moving the mouse, back to 60

I've seen this in one or two other games but thought they were one offs and don't recall which ones.

https://gist.github.com/parkerlreed/42118febd90183f763b087bdf25d763c

New log if it's at all helpful

steam-8190.log

Video

https://user-images.githubusercontent.com/841440/174467931-414d72d7-ce0e-47e4-ac2a-3e607399e5f6.mp4

Appears to be a re manifestation of https://bugs.winehq.org/show_bug.cgi?id=46976

Setting the USB HID polling rate to 125Hz (off the default 1000) and re plugging my G400s allows the game to work properly.

Unfortunately I cannot reproduce any noticeable video dropouts with a high polling rate mouse (G502 Hero), so I can't speak for it being anything but a specific hardware quirk.

One thing I've noticed about JC2 is that it has some NV specific effects when nvapi is enabled - unfortunately, current Experimental seems to lack the ability to enable this for other games, but using the GE fork of Proton I can use PROTON_ENABLE_NVAPI and set a dll override for nvcuda to be enabled. Using this allows the Nvidia-exclusive options "Bokeh Filter" and "GPU Water Simulation" to be toggled in the Advanced Display options, but using either causes the game to crash.

A log, for what it's worth.

Given the recent efforts to enable NVAPI in Experimental, will there be plans to allow this game to be enabled for nvapi support in upstream Proton? And if so, could the nvapi-related crashes in this title be addressed? If not, would this be considered a DXVK-NVAPI issue (considering it's only affected by having the NVAPI enabled), or an upstream DXVK one (because of it causing crashes, presumably unimplemented functions in that side)?

@SeongGino You mean running with PROTON_ENABLE_NVAPI=1 in regular Proton doesn't expose the extra options but does with Proton GE?

nvcuda is a dll included with valves wine fork from what i can see. But it doesn't actually contain any code.
Tho i see wine staging have some work/patches for it.

I'm pretty sure the Wine Staging version doesn't support D3D interop, especially not with DXVK.

I think it's possible to implement (a lot of the CUDA interop work is already done for DLSS) but I don't think anyone is going to do it.

@SeongGino You mean running with PROTON_ENABLE_NVAPI=1 in regular Proton doesn't expose the extra options but does with Proton GE?

nvcuda is a dll included with valves wine fork from what i can see. But it doesn't actually contain any code. Tho i see wine staging have some work/patches for it.

Indeed. This is all just history from my experimentation with Batman: Arkham Asylum's PhysX and what I found (typically) allowed real HW accelerated CUDA operations.

I guess I'm not all that surprised that support for these functions in JC2 may not come; I was simply being thorough with reports when going through my PhysX/CUDA-utilizing games library--it's the only game I've found which doesn't work with Nvidia extras. Would be nice if it ever came tho - even if it's just for some minor graphical nicety.

So far didn't have any problem playing using the Protontrick method
protontricks 8190 dlls d3dx10 d3dcompiler_43 d3dcompiler_47

tested under Ubuntu 22.04.2 LTS x86_64 with Proton Experimental, full controller support and gyro.

The game does not launch, whatever the tips I tested on Protondb.
I can only see the first screen, then the game exits.

https://gist.github.com/legluondunet/8c353105c386d1a121041a3ad1b4a2b4

steam-8190.log

I uninstalled the game and reinstalled it today, it launched fine, without any tricks, no need to install anything with protontricks either, you changed something that could explain this good news ?

Game still gets stuck on a black screen on launch on my oled deck.

steam-8190.log

I got it working, here are my steps:

1. Install game
2. Set to use Proton-GE under Settings (Proton-GE 9_4)
3. Do not launch the game, run protontricks 8190 dlls d3dx10 d3dcompiler_43 d3dcompiler_47
4. Launch the game, it should load without issue.

However, I was running into one issue. The game would launch but immediately crash with this error:

Fatal DirectX error!
Code: 1
Result: 0x80004005: E_FAIL
The game will now exit. Try starting the game with /failsafe if the problem persists.

The solution was the install the following packages:

lib32-vulkan-radeon
lib32-vulkan-mesa-layers
lib32-vulkan-icd-loader

DXVK was throwing these errors:

6611.335:0124:0128:err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3
6611.335:0124:0128:err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3
6611.351:0124:0128:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\winevulkan.dll" : builtin
err:   DxvkInstance::createInstance: Failed to create Vulkan 1.1 instance

Thus the missing 32-bit libraries were needed, as the game is indeed 32-bit and not 64-bit.

Arch Linux, 6.6.28-1-lts

proton-ge-custom-bin 1:GE_Proton9_4-1

lib32-vulkan-icd-loader 1.3.279-1
lib32-vulkan-intel 1:24.0.5-1
lib32-vulkan-mesa-layers 1:24.0.5-1
lib32-vulkan-radeon 1:24.0.5-1
vulkan-headers 1:1.3.279-1
vulkan-icd-loader 1.3.279-1
vulkan-intel 1:24.0.5-1
vulkan-mesa-layers 1:24.0.5-1
vulkan-radeon 1:24.0.5-1
vulkan-tools 1.3.269-1

@waspennator @jessienab
I just uninstalled "Just Cause 2" on Steam and reinstall it:

• default Proton: NOK , black screen
• experimental Proton: NOK
• GE-Proton-4: OK

I never need to install anything with Protontricks, I think it is no more necessary, Steam already install all this dependencies at first game launch.

Result could depend your config too, this is mine:

Manjaro 23.1.4 Vulcan
Kernel: x86_64 Linux 6.6.25-1-MANJARO
Proc: AMD Ryzen 9 5900HX
GPU: AMD Radeon RX 6600M
Drivers: Mesa 24.0.2
Resolution: 1920x1080
32 Go RAM
DE: Xfce4

One more thing:
once I launch the game with GE-Proton-4, I can launch it with standard Proton and experimental too...
GE-Proton-4 changed something in game Proton prefix that permit the game to launch with others Proton version too.

This game is currently not working with Proton Experimental (2024/07/31), 9.0-2 and 8.0-5. I've tried it on X11/Wayland with/without DXVK. When we add the d3dcompiler_47.dll (32bits) it at least shows the splash screen, but crashes after a few seconds.

Proton logs: steam-8190-just-cause.tar.gz

Main error lines (without d3dcompiler_47):

940.072:012c:0198:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
940.072:012c:0198:err:d3dcompiler:D3DCompile2 Shader log:
940.072:012c:0198:err:d3dcompiler:D3DCompile2     <anonymous>:6:121: W5300: Implicit truncation of vector type.
940.072:012c:0198:err:d3dcompiler:D3DCompile2     <anonymous>:6:225: W5300: Implicit truncation of vector type.
940.072:012c:0198:err:d3dcompiler:D3DCompile2     <anonymous>:6:160: W5017: Loop unrolling is not implemented.
940.072:012c:0198:err:d3dcompiler:D3DCompile2     <anonymous>:6:243: E5002: Expected literal sample index.
940.072:012c:0198:err:d3dcompiler:D3DCompile2 

Main error lines (with d3dcompiler_47):

1617.865:0128:01dc:warn:seh:dispatch_exception EXCEPTION_WINE_CXX_EXCEPTION exception (code=e06d7363) raised
1617.865:0128:01dc:trace:seh:dispatch_exception  eax=0b8cf5f4 ebx=00436390 ecx=00000000 edx=0b8cf608 esi=0b8cf680 edi=0b8cf610
1617.865:0128:01dc:trace:seh:dispatch_exception  ebp=0b8cf64c esp=0b8cf5f4 cs=0023 ss=002b ds=002b es=002b fs=0063 gs=006b flags=00000213
1617.865:0128:01dc:trace:seh:call_vectored_handlers calling handler at 7978BE60 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_vectored_handlers handler at 7978BE60 returned 0
1617.865:0128:01dc:trace:seh:call_vectored_handlers calling handler at 793AC410 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_vectored_handlers handler at 793AC410 returned 0
1617.865:0128:01dc:trace:seh:call_vectored_handlers calling handler at 7997CFB0 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_vectored_handlers handler at 7997CFB0 returned 0
1617.865:0128:01dc:trace:seh:call_vectored_handlers calling handler at 7A20D310 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_vectored_handlers handler at 7A20D310 returned 0
1617.865:0128:01dc:trace:seh:call_stack_handlers calling handler at 00D91C90 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_stack_handlers handler at 00D91C90 returned 1
1617.865:0128:01dc:trace:seh:call_stack_handlers calling handler at 00D91C90 code=e06d7363 flags=1
1617.865:0128:01dc:trace:seh:call_stack_handlers handler at 00D91C90 returned 0

Specs:

• OS: Arch
• Kernel: 6.6.42
• GPU: RX 6700 XT (Mesa 24.1.5)
• CPU: Ryzen 7 5700G (8c/16t)

@ranplayer have you tried clearing local stored shader cache?
~/.cache/mesa_shader_cache

(I am not a dev not Valve employee but just from the non replaced .dll error maybe that might work?)

Just mentioning as I launched today with 9.0-5 and 8.0-5 without issues... didn't try experimental. X11 with DXVK, same Arch Linux, kernel 6.6.40-lts, RX580, mesa 1:24.1.3-1, Ryzen 3700X. No custom launch options.

@jessienab unfortunately the same problem

just cause 2 uses ceg drm, you might need to verify game files for the game to start.

Just tested:

1. uninstall game/Reinstall game to test with a clean install
2. Game did not launch with Proton Experimental
3. install Ge-Proton9.11 from https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton9-11, the game launched OK

Then, once time I launch the game with Ge-Proton9.11, then I can launch it with Proton too

steam-8190.log

Config:

Manjaro 24.0.5 Wynsdey
Kernel: x86_64 Linux 6.6.41-1-MANJARO
Proc: AMD Ryzen 9 5900HX
GPU: AMD Radeon RX 6600M
Drivers: Mesa 24.1.3
Resolution: 1920x1080
32 Go RAM
DE: Xfce4

Tried testing again on my oled, but it got stuck on updating executable.

I did have an older prefix for JC2 installed before, which still works. But trying to make a prefix from scratch w/ GE9-16 seems to be a bust atm. I'll have to look later when I get some free time to see what's up with that.

debian bookworm, game is unlaunchable on proton 9.0-4

@mathew2214 Set the launch options to PROTON_LOG=1 %command% and launch the game. That will create a log file in your home directory with a name that starts with steam-. Post that and someone can look into it.

it works after moving from nfs4 to local btrfs. Steam didnt used to have any issues with playing form nfs, did something change recently?

Hard to say what the issue is without logs, though it generally isn't advised to use ntfs on linux. If the filepath in the ntfs happened to be too long, there's a chance the game would have worked with PROTON_SET_GAME_DRIVE=1 %command%, it's also possible there were corrupted files and that moving them forced a verification, etc.

https://gist.github.com/Keenwhisk/ef1f3e5cab546c202c9662f2fff48d35

steam-8190.log

Hello. In Proton Experimental the game renders in incorrect resolution, and is not allowing to change resolution, showing no available ones, which renders all the fonts and the game itself weird and incorrectly:

In Proton 9.0-4 it works normally and reports correct resolution:

Also, SSAO (ambient occlusion) effect introduces weird stripes with both Proton 9.0-4 and Expiremental (just like in my Borderlands 2 report)

Disabling SSAO fixes it:

I can't reproduce the resolution selection issue. Please try the latest version of Proton experimental.

Can you post your save for the SSAO issue? Or even better: make an apitrace? It's very subtle and finding a spot where this happens is gonna take forever.

@Keenwhisk The resolution issue you are experiencing is a problem when you are using fsync with this game and I can see you are running fsync in your log. Do you know if you have a launch option disabling NTsync? Could you also try with Linux kernel 7.0.12-arch1-1 please?

@Keenwhisk The resolution issue you are experiencing is a problem when you are using fsync with this game and I can see you are running fsync in your log. Do you know if you have a launch option disabling NTsync? Could you also try with Linux kernel 7.0.12-arch1-1 please?

Nope, I used default Proton Expiremental without any launch parameters. I already tried on older kernels as well, it was the same on Proton Expiremental, same were happening on proton-cachyos. This does not happen on proton-cachyos when I use PROTON_ENABLE_WAYLAND=1 enviromental variable. But on Proton 9.0-4 it works good, only issue is SSAO introduces artifacting.

Replying to https://github.com/ValveSoftware/Proton/issues/670#issuecomment-4801754280

I have just tried again with the latest Proton Experimental, and I have the same issue. I am able to choose the resolution, but it just isn't applying. Sometimes it suddenly applies, but after re-entering to the game it resets, and then I am not able to apply my resolution, it applies it but everything is blurry.

Regarding SSAO: I don't know how to make an apitrace, if you could tell me I can try. Just take a ride with any ground vehicle on the roads. Look at those "dots" here:

They disappear once I disable SSAO. Happens on both Expiremental and 9.0-4.

If you need the exact location, it's here, but you can literally see this glitch at any part of the map:

Also, whenever the game is able to choose my resolution, with MSAA enabled the game introduces those weird transparency graphical artifacts. It was reported on ProtonDB also.
Does not happen on Proton 9.0-4, but happens on Experimental.

Might have something in common with my Alan Wake report

@Keenwhisk The main issue here is that NTsync is not working on your machine and that is breaking the resolution because it is broken with current fsync. For some reason NTsync is not working on your device. Your log says fsync: up and running. which is not good. Nothing has changed regarding NTsync since it has been released, which indicates it may be a problem outside of Proton.

Something you can try is deleting the prefix and trying again with Proton Experimental. Using prefixes from broken Protons (10.0-4 for example in this specific case) or non-official Proton builds (proton-cachyos for example) can cause problems which switching around.

If you want to see if fsync or ntsync is running, in your Proton log it will say either fsync: up and running. or ntsync: up and running., and you want ntsync to show up when using Proton 11 or newer.

Also, can you add a gist of your System Information please? The gist you added before was the Steam Runtime Diagnostics which is the option right below System Information.