The same for me on 3.7 and 3.7-4 beta
The game exits when starting a Skirmish.
Ubuntu 18.04 + NVIDIA GTX 1060 6GB
Proton 5.0-2 with system info
Here is the proton log https://gist.github.com/adrianlshaw/0a00c32e8a3f1ce9197e2164d5710691
Hello @adrianlshaw, is this a recent regression for you? Please check if PROTON_USE_WINED3D=1 %command% has an effect.
Separately, please check if PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% has an effect.
From the log:
err: DxvkMemoryAllocator: Memory allocation failed
err: Size: 33177600
err: Alignment: 256
err: Mem flags: 0x6
err: Mem types: 0x681
err: Heap 0: 575 MB allocated, 499 MB used, 686 MB allocated (driver), 5105 MB budget (driver), 6144 MB total
err: Heap 1: 416 MB allocated, 381 MB used, 584 MB allocated (driver), 15000 MB budget (driver), 15000 MB total
7760.791:0036:0037:trace:seh:MSVCRT_raise (22)
Unable to read VR Path Registry from C:\users\steamuser\Local Settings\Application Data\openvr\openvrpaths.vrpath
terminate called after throwing an instance of 'dxvk::DxvkError'
Hi @kisak-valve thanks for the swift response.
Adding PROTON_USE_WINED3D=1 fixes it.
Separately, adding PROTON_FORCE_LARGE_ADDRESS_AWARE=1 also seems to work.
I don't know with certaintiy if it's a regression, however I just reverted to 4.11-12 and it works perfectly without any launch options.
Thanks for checking, Proton 5.0 enabled DXVK/D3D9 by default, and it's using more resources than before. You'll want to use PROTON_FORCE_LARGE_ADDRESS_AWARE=1 for this game going forward because the WINED3D render path is expected to come with a performance penalty.
As requested by @kisak-valve, I am reposting my feedback in this thread.
The game crashes whenever you alt-tab to another running application if you are running the game in fullscreen mode. The game will not crash if you are running it in windowed mode. I have used both Proton 5.0-5 and 4.11-13.
Here is my system details, and here is the logfile. To generate the logfile, I first cleared whatever logfile is present for the game and then started the game in fullscreen mode. Once I reached the main menu, I alt-tab to another window.
Wasn't sure whether to make a new issue or not so apologies if this is the wrong thread.
In the latest version of Proton and GE the game will close without an error after approximately 10-20 minutes.
Ubuntu 22.04.1
Occurs on Proton 7.0-5 & GE-Proton7-42
Have tried PROTON_FORCE_LARGE_ADDRESS_AWARE=1
I've attached a log below
The game worked fine previously, not sure if this is a system issue on my end or with the game.
Hello @Jackson-Bondy, what's the newest Proton version you know wasn't affected by that behavior? Also, 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.
As a side note, PROTON_FORCE_LARGE_ADDRESS_AWARE got enabled by default for all games run with Proton a fair while ago, so manually setting that on will have no effect these days.
Hello,
I'm not sure on the previous version that was unaffected but I have just tried an hour or two on 3.7-8 without any crashes.
Thanks for the information on the parameter and I've pasted my system information below:
Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: ROG STRIX X470-I GAMING
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 5 5600X 6-Core Processor
CPU Family: 0x19
CPU Model: 0x21
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 4650 Mhz
12 logical processors
6 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Ubuntu 22.04.1 LTS (64 bit)
Kernel Name: Linux
Kernel Version: 5.15.0-56-generic
X Server Vendor: The X.Org Foundation
X Server Release: 12201001
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime_0.20221019.0
Video Card:
Driver: AMD AMD Radeon RX Vega (vega10, LLVM 13.0.0, DRM 3.42, 5.15.0-56-generic)
Driver Version: 4.6 (Compatibility Profile) Mesa 22.1.0-rc4
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x1002
DeviceID: 0x687f
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 2560 x 1440
Desktop Resolution: 2560 x 1440
Primary Display Size: 23.62" x 13.39" (27.13" diag)
60.0cm x 34.0cm (68.9cm diag)
Primary VRAM: 8192 MB
Sound card:
Audio device: ATI R6xx HDMI
Memory:
RAM: 31999 MB
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_GB.UTF-8
Total Hard Disk Space Available: 233645 MB
Largest Free Hard Disk Block: 31183 MB
Storage:
Number of SSDs: 4
SSD sizes: 500G,480G,250G,30G
Number of HDDs: 0
The runtime information tool is preparing a report, please wait...
Proton 3.7 is from 4 years ago. That's an unreasonable amount of time to ponder your issue as a regression.
I've gone back through every version as far as 5.0-10 which still has the same issue, different log now however which I've attached.
I am almost certain I have played the game in 2021 so I can only think this must be some sort of kernel/Ubuntu update which is causing an incompatibility in newer versions of Proton.
If I get time I will keep working through previous versions until I find one which is working fine.
The end of the logfile is:
X connection to :0 broken (explicit kill or server shutdown).
5274.927:0058:0068:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\drivers\\winehid.sys" : builtin
5274.928:0058:0068:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\hidclass.sys" : builtin
5274.928:0058:0068:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\drivers\\winebus.sys" : builtin
pid 14230 != 14229, skipping destruction (fork without exec?)
Just picked this up today, seems to work just as I remember it on Windows, running on Proton 8.0-2. Only issue I had was switching windows (Alt-Tab) results in a blank screen when returning to the game.
The aforementioned issue was resolved recently - I think with the release of Proton 10.
I don't normally play across different computers but I noticed an issue with file synchronisation similar to what I reported for Kane's Wrath, even though there's no complication with apostrophes in the directory name.
proton 8.0-2x1 2023-05proton 3.7x1 2022-12ge-proton7-42x1 2022-12proton 7.0-5x1 2022-12proton 5.0-5x1 2020-04proton 5.0x1 2020-02proton 5.0-2x1 2020-02proton 3.7-5x1 2018-09PROTON_FORCE_LARGE_ADDRESS_AWAREx1 2022-12PROTON_FORCE_LARGE_ADDRESS_AWARE=1x3 2022-12PROTON_FORCE_LARGE_ADDRESS_AWARE=1`x1 2020-02PROTON_USE_WINED3D=1x2 2020-02PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%x1 2020-02PROTON_USE_WINED3D=1 %command%x1 2020-02
Using Proton 3.7-5 beta, ingame corruption occurs. Also, the 3D render resolution is not 1080p.
https://steamcommunity.com/id/paradox/screenshot/968725783524075202
https://steamcommunity.com/id/paradox/screenshot/968725783524075647
https://gist.github.com/tsalwierz/ee8fc2690d7e3f33c39b35cd8f1a4bea