search

ValveSoftware / Proton

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

New World (1063730) #5772

Open masonnl opened 2 years ago

masonnl commented 2 years ago

Compatibility Report

System Information

I confirm:

Symptoms

Steps to Reproduce

Scenario 1:

Scenario 2:

kisak-valve commented 1 year ago

New World

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6920. @HydeFromT70s posted on 2023-07-09T15:13:16:

Compatibility Report

System Information

I confirm:

Proton log as Gist

Symptoms

The game stopped launching after the last update on July 6. In steam it has the status "Running", but after a few seconds the game crashes with an error as in the picture. Before the update the game was running without any problems.

Crash Error

NOTE: The game starts normal with Proton 7.0-6.

Reproduction

Just start the game with Proton Experimental or Proton 8.0

KorinFlakes commented 10 months ago

Game won't even launch for me no matter what version of proton I use. Proton log has nothing written in it after the kernel line. Specs: https://gist.github.com/KorinFlakes/5bae39554652107692169a4338dcc1bc

kisak-valve commented 10 months ago

Hello @KorinFlakes, a header only Proton log hints that something went wrong before the game itself had a chance to run. If you completely close Steam, then run steam-runtime from a terminal, are there any hints in the terminal spew when you tell Steam to start the game?

KorinFlakes commented 10 months ago

Thank you, there was a problem with the compatdata/1063730 folder so I deleted that and re-ran the game and it launched.

kisak-valve commented 9 months ago

New world crashing very often during loading screens

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7234. @Kitsab77 posted on 2023-11-04T22:32:48:

Compatibility Report

System Information

I confirm:

https://drive.google.com/file/d/1LVnKnSszH5Usy1HA-ZPTzLCaj5I76WrZ/view?usp=sharing Game always crashes with a bunch of: err:sync:RtlpWaitForCriticalSection section 000000017006F2A0 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0340, blocked by 0784, retrying (60 sec) at the end. ## Symptoms

The game is crashing during loading screen (mostly in bigger cities or crowded places) The crash always happens during loading screen. When logging into the game it needs sometimes up to 10 tries to logon. Also happening when using recall to tavern or fast travel portals to cities. Sometimes also happens outside of cities. Tried mesa drivers, tried amdgpu driver installed from Archlinux[Aur], tried different wine versions. Actual launch options: PROTON_LOG=1 DRI_PRIME=1 %command% -dx12 -high -novid -nojoy -vulkan -disable_d3d9ex -nohltv Basic launch options I tried: DRI_PRIME=1 %command% -dx12 -high

Reproduction

Could be reproduced very well, happening everytime I play the game.

I searched the web for err:sync:RtlpWaitForCriticalSection, I found this should have been fixed by release Wine6.1

I tried a lot chaning graphic details, but this seems to be replated to a internet/game server connection timeout issue, or may I misunderstand this?

Thanks and best regards kitsab

Kitsab77 commented 9 months ago

New world crashing very often during loading screens

[Edit, did not solve the issue - it happened again]

Hello,

possibly I found something after long repeating duckduckgo - searches. There was a message board post relating to this issue https://www.reddit.com/r/linux_gaming/comments/143tjqb/tales_of_arise_overloading_ryzen_5600x_when/ They advice to modify this: sysctl vm.max_map_count vm.max_map_count = 65530 to 2147483642 with the command sudo sysctl -w vm.max_map_count=2147483642 This is a system memory handler argument from my understanding. The discussion refers to this information: https://www.phoronix.com/news/Fedora-39-VM-Max-Map-Count

I had the issue trying to logon ~10 times again, after modifying this value it worked instandly - hopefully this solves the problem.

Best regards

Kitsab

kisak-valve commented 8 months ago

New World Crashing on Startup

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7341. @bigwheel50 posted on 2023-12-13T18:31:14:

Compatibility Report

System Information

I confirm:

steam-1063730.zip

Symptoms

The game crashes immediately during startup.

Reproduction

  1. Launch game
  2. [Don't] Profit

Have tried multiple versions of Proton, GE-Proton, launch options, etc.

kisak-valve commented 8 months ago

Hello @bigwheel50, looking at your system information, it looks like Vulkan is broken in general on your system (https://gist.github.com/bigwheel50/9387dd7d7460814ca43f6b0fa78a766f#file-gistfile1-txt-L3573-L3584) I suspect this is from something setting DRI_PRIME=pci-0000_5c_00_0 (https://gist.github.com/bigwheel50/9387dd7d7460814ca43f6b0fa78a766f#file-gistfile1-txt-L153) which is then breaking the Vulkan render path.

Blind guess, if you completely close Steam, then run steam from a terminal, does that have an effect on that environment variable getting set and the game's behavior?

bigwheel50 commented 8 months ago

Thank you for the quick reply! Launching steam through the terminal does seem to impact the DRI_PRIME code (it no longer appears at all in the runtime diagnostic output), however, Vulkan seems to remain the same, as does the crashing issue.

stiangrindvoll commented 8 months ago

With New World's season 4 update it started to crash for me as well after the loading screen. On Proton v7.0-6 that i have been using, it gives me this error, dont have any more logs than this for now. Screenshot from 2023-12-13 19-21-04

bigwheel50 commented 8 months ago

I've gotten that same error when trying older versions of Proton/GE-Proton as well.

As @stiangrindvoll mentioned, the issue started this morning after a large patch. Up until this, things were running smoothly.

stiangrindvoll commented 8 months ago

Here is my proton steam log file steam-1063730.log.gz

Blisto91 commented 8 months ago

I assume you both have high core count CPUs. Can you check if it works by limiting the amount of logical cores to 26? WINE_CPU_TOPOLOGY=26:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25 %command% Or even lower if that doesn't help.

Edit: Playing with 16 seems stable so far

stiangrindvoll commented 8 months ago

Yes this worked! Thank you @Blisto91 im currently testing with 18.

bigwheel50 commented 8 months ago

Wooo! Can confirm that worked for me as well! 26 still failed, however, I tried the aforementioned 18 count and that did the trick!

Blisto91 commented 8 months ago

Cool thanks. 26 seemed to do the trick for me, but might be a bit random. Shouldn't hurt the game either way.

Edit: actually 26 could still crash ingame at times. 16 seems stable so far

stiangrindvoll commented 8 months ago

i had crashes at 18 too, randomly while in the game. At 12, i've had no single crash yet.

mailhotz commented 8 months ago

New World eventually hard crashes my machine and have to hard reboot.

Compatibility Report

System Information

Screenshot from 2023-12-20 19-10-31

I confirm:

steam-1063730.zip

Symptoms:

Game loads in fine, occasionally crashes after character select or sporadically during gameplay. It may be of note that my journal gets flooded with the following log line, on average it's posting the overrun log with different values about every 2-3ms

localhost.localdomain pipewire-pulse[2847]: mod.protocol-pulse: 0x55a26846aaa0: [New World] overrun recover read:230400 avail:17408 max:15360 skip:13568

Example of frequency:

Dec 20 19:00:34 localhost.localdomain pipewire-pulse[2847]: mod.protocol-pulse: 0x55a26846aaa0: [New World] overrun recover read:41568768 avail:28160 max:15360 skip:24320
Dec 20 19:00:35 localhost.localdomain pipewire-pulse[2847]: mod.protocol-pulse: 0x55a26846aaa0: [New World] overrun recover read:41846528 avail:16640 max:15360 skip:12800
Dec 20 19:00:35 localhost.localdomain pipewire-pulse[2847]: mod.protocol-pulse: 0x55a26a998b50: [New World] overrun recover read:40660480 avail:16896 max:15360 skip:13056
Dec 20 19:00:39 localhost.localdomain pipewire-pulse[2847]: mod.protocol-pulse: 0x55a26a998b50: [New World] overrun recover read:42370816 avail:16640 max:15360 skip:12800
Dec 20 19:00:42 localhost.localdomain pipewire-pulse[2847]: mod.protocol-pulse: 0x55a26a998b50: [New World] overrun recover read:43474176 avail:17152 max:15360 skip:13312

Do not seem to have this log appear in any game besides New World.

Game crash in journal after freezing machine

Reproduction:

Unaccounted4 commented 6 months ago

I have a similar issue to what @mailhotz is reporting. On my end it doesn't crash the entire OS but the game itself will crash after 2 hours of continuous play. Checking journalctl reveals it spews that message several times per second.

System specs: https://gist.github.com/Unaccounted4/2e1ee0dd64ccc5c6801740e3cbe4ab89

Sample of 2 seconds in journalctl:

jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:148922368 avail:16384 max:15360 skip:12544
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:149659136 avail:25088 max:15360 skip:21248
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb4b890: [New World] overrun recover read:161242624 avail:41472 max:15360 skip:37632
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:149684224 avail:16384 max:15360 skip:12544
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:148938752 avail:32768 max:15360 skip:28928
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb4b890: [New World] overrun recover read:161337856 avail:19968 max:15360 skip:16128
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:149754368 avail:19968 max:15360 skip:16128
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149017600 avail:27648 max:15360 skip:23808
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb4b890: [New World] overrun recover read:161380864 avail:17920 max:15360 skip:14080
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:149797376 avail:17920 max:15360 skip:14080
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149060608 avail:33792 max:15360 skip:29952
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:149853696 avail:27136 max:15360 skip:23296
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149117440 avail:34304 max:15360 skip:30464
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb4b890: [New World] overrun recover read:161479424 avail:17664 max:15360 skip:13824
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:149896192 avail:25600 max:15360 skip:21760
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149151744 avail:40960 max:15360 skip:37120
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb4b890: [New World] overrun recover read:161512448 avail:17408 max:15360 skip:13568
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:149929472 avail:25088 max:15360 skip:21248
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149192704 avail:32768 max:15360 skip:28928
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb4b890: [New World] overrun recover read:161568256 avail:18944 max:15360 skip:15104
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353bf77ab0: [New World] overrun recover read:246136576 avail:24832 max:15360 skip:20992
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb4b890: [New World] overrun recover read:161587200 avail:16384 max:15360 skip:12544
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149240832 avail:33792 max:15360 skip:29952
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:149977600 avail:42496 max:15360 skip:38656
jan 29 22:35:00 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149274624 avail:16384 max:15360 skip:12544
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149298688 avail:16896 max:15360 skip:13056
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb4b890: [New World] overrun recover read:161641984 avail:18944 max:15360 skip:15104
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:150027776 avail:49664 max:15360 skip:45824
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149323264 avail:25088 max:15360 skip:21248
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149348352 avail:16384 max:15360 skip:12544
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353bf77ab0: [New World] overrun recover read:246257408 avail:18688 max:15360 skip:14848
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb4b890: [New World] overrun recover read:161691648 avail:26624 max:15360 skip:22784
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:150108160 avail:26624 max:15360 skip:22784
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb4b890: [New World] overrun recover read:161718272 avail:16384 max:15360 skip:12544
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:150134784 avail:16384 max:15360 skip:12544
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149380096 avail:41984 max:15360 skip:38144
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353cb3c090: [New World] overrun recover read:150158848 avail:16896 max:15360 skip:13056
jan 29 22:35:01 Desktop pipewire-pulse[4597]: mod.protocol-pulse: 0x56353a5daa10: [New World] overrun recover read:149422080 avail:24576 max:15360 skip:20736
AMFrancq commented 3 months ago

Repeatedly crashing in game after 15-40 minutes of gameplay. Happens in a variety of locations.

Startup settings: ENABLE_VKBASALT=1 RADV_PERFTEST=gpl YMMV_VULKAN_ICD=RADV WINE_CPU_TOPOLOGY=8:0,1,2,3,4,5,6,7 %command% > ~/NWout.log 2> ~/NWerr.log

Here is the ourput of NWerr.log:

ERROR: ld.so: object '/home/ash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/ash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/ash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
x86_64-linux-gnu-capsule-capture-libs: warning: Dependencies of libnvidia-pkcs11.so.550.78 not found, ignoring: Missing dependencies: Could not find "libcrypto.so.1.1" in LD_LIBRARY_PATH "/usr/lib/x86_64-linux-gnu/libfakeroot:/lib/i386-linux-gnu:/usr/local/lib:/lib/x86_64-linux-gnu:/lib:/home/ash/.local/share/Steam/steamapps/common/New World", ld.so.cache, DT_RUNPATH or fallback /lib:/usr/lib
esync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Setting breakpad minidump AppID = 1063730
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561198055466734 [API loaded no]
[356:360:20240429,123858.830:WARNING registration_protocol_win.cc:103] SendToCrashHandlerServer(): CreateFile("000000000376CCD0") failed.: File not found. (2)
Fossilize INFO: Overriding serialization path: "/home/ash/.local/share/Steam/steamapps/shadercache/1063730/fozpipelinesv6/steamapprun_pipeline_cache".
Setting breakpad minidump AppID = 1063730
SteamInternal_SetMinidumpSteamID:  Caching Steam ID:  76561198055466734 [API loaded no]
Fossilize INFO: Overriding serialization path: "/home/ash/.local/share/Steam/steamapps/shadercache/1063730/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/home/ash/.local/share/Steam/steamapps/shadercache/1063730/fozpipelinesv6/steamapprun_pipeline_cache".
*** stack smashing detected ***: terminated
pid 5923 != 5922, skipping destruction (fork without exec?)

The error log shows up to "Fossilize INFO" while starting and then the crash is always "stack smashing detected". I've tried this on Proton 7, 8, 9 beta, and experimental through Steam's compatibility tool.

Does anyone have any idea on next steps? I keep crashing in combat and dying.

AMFrancq commented 3 months ago

The game seems to have a problem with multi-threading and proton, I have been able to achieve stable performance (albeit not great performance) with the following change to my launch options: WINE_CPU_TOPOLOGY=4:0,2,4,6

EDIT: @blae-s why thumbs down?

Milor123 commented 4 weeks ago

Someone solution for the crashes? I have a rtx 4070 and a i5 13500, i am using proton 9-10 and Manjaro with wayland