New World: Aeternum (1063730)

[masonnl]

Compatibility Report

• Name of the game with compatibility issues: New World
• Steam AppID of the game: 1063730

System Information

• GPU: GTX 3060
• Driver/LLVM version: nvidia: 510.60.02 / llvm-config: 13.0.1
• Kernel version: 5.15.32-1-MANJARO
• System Gist
• Proton version: Proton 7.0-1
• GE version 7-14
• Proton logfile cannot be uploaded. It exploded to 280MB when created so instead I took the head of the first 10k lines here: steam-1063730-head10k.log
  • EDIT: here's my compressed logfile taken from my comment below: steam-1063730.log.zip

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.
• [x] EAC support has been added to the game's directory under EasyAntiCheat/easyanticheat_x64.so and connects successfully as shown in the EAC logs generated under ~/.cache/com.epicgames.easyanticheat/271/loader.log. I have been able to play upwards of 10+ hours in the last few days (with crashes as described below).

Symptoms

• [RESOLVED] ~Except in the rare occasion when the game actually loads, it will simply crash to desktop while loading into a character (see STR below).~
• Stuttering on various settings (even low) with resolution at 1920x1080
  • Playing at full native resolution of 2560x1440 ran fine and was locked at 60fps (with the same amount of stuttering)

Steps to Reproduce

Scenario 1:

• Hit Play in Steam
• Log in to character
• Loading screen...
• :boom: back to desktop
  • :warning: Very rarely the game will load in and I can play. I have not modified shader files or compat files. It will sometimes just work :shrug:

Scenario 2:

• Hit play in Steam
• Create new character
• Play completely through the tutorial zone and get into the main world with other players. This seems to have worked for me 2/2 times, but I obviously don't want to do to that :D The first time I did it, I played for a few hours without issue (other than stutters).

[gofman]

I couldn't reproduce the crash (loading with existing character worked just fine for me 2 of 2 times).

Could you please try the following:

1. Run the game with official Proton Experimental (or better Proton Experimental [bleeding-edge] branch: select [bleeding-edge] in Proton Experimental's properties, Beta page). It won't work out of the box due to EAC launcher problem which is hacked around in Proton GE build. But it should work with the attached EasyAntiCheat_x86.dll (that is the .dll from EAC SDK correct for Linux EAC). Unzipped dll should be copied over EasyAntiCheat/EasyAntiCheat_x86.dll in the game directory). This way the game should start with the launcher normally with official Proton. 2.If the crash described above still happens with official Proton, could you please attach full (compressed) log (default log from PROTON_LOG=1 %command%). The log may be big but it is compressed very well.

EasyAntiCheat_x86.zip

[masonnl]

Hi @gofman :wave:

Going forward I won't use GE to troubleshoot just to limit the problem space. Assume Proton Experimental is being used unless specified.

It won't work out of the box due to EAC launcher problem which is hacked around in Proton GE build.

As far as I know, the official New World client shipped all the correct SDK files for EAC with a fresh install via Steam on Linux. Are you saying that the game didn't package the linux eac dll?

This way the game should start with the launcher normally with official Proton.

I backed up the eac directory, and placed your attached dll in the eac directory. Launch options: PROTON_LOG=1 %command% and using Proton Experimental. Here's the latest (compressed) crash report: steam-1063730.log.zip

Thanks for your time!

EDIT: I haven't used bleeding edge before so I glossed over that in your request. Here's a log using Proton Experimental with bleeding edge specified: steam-1063730-bleeding-edge.log.zip

[blae-s]

Hi @gofman

GPU: GTX 1060 Driver/LLVM version: nvidia: 510.60.02 / llvm-config: 13.0.1 Kernel version: 5.17.1-xanmod1-1

I removed GE-proton prefix, switched to proton experimental bleeding edge and copied EasyAntiCheat/EasyAntiCheat_x86.dll as you suggested, with PROTON_LOG=1 %command% as launch options.

Starting the game and loading a character worked 5 times in a row and i was able to play a little while, then crashed the 6th times i started the game before even being able to load a character

steam-1063730.log.zip

[gofman]

Thanks for the logs!

@masonnl Somehow both your log gives no clue even on immediate crash reason (that's apparently not your fault). Can you please attach dmesg (or 'sudo dmesg' if your system restricts dmesg to root only) output dumped right after the game has crashed?

@blae-s Your log does have immediate reason but it suggests some very weird memory corruption reason of which I am unlikely to guess without reproducing.

Are there any hints or more details how any of those crashes can be reproduced? I've got a character which I exited the initial ship wreckage / zombies area, got and completed some first "dueling quest" killing some drowners, and loading in to this character. Is that enough? I wasn't able to reproduce any crashes so far.

[masonnl]

Looks to be crashing due to an out of memory dump. Possibly a mem leak or something as it is not an issue with my hardware limitations. dmesg.dump.log

As mentioned, this crash occurs very consistently for me. I am not in the tutorial zone of the game, though which it sounds like you may be? I believe I am logged out in a city.

[gofman]

Hm, if I am not missing something obvious in arithmetic the game takes roughly 10GB of RAM when killed, which is not obviously an issue on 16GB machine. Looks like something potentially explored with the host maybe.

Just in case, is it long to get out of tutorial zone to the city and, provided that is not too long and easy to say, how do I quickly get to a city out of tutorial zone?

[masonnl]

Probably takes 10 minutes from opening the game. Just run where it points you, fight the dude with the laser-beam sword, spawn on the beach, and follow the main road into the nearest town (hit 'M' to reveal the map; you will spawn in 1 of 3(?) random areas so the town name will vary).

[masonnl]

Following up on this with some new discoveries:

I got to thinking about the oom-killer and it made me realized a couple things:

1. The oom-killer was triggered at exactly 10GB with the appropriate kernal-defined leftovers of ~4GB being preserved for the system.
2. This made me realize I do not have a swapfile setup for this system; this will be important later.

To help see if I was indeed hitting some system-defined process memory cap I ran the following command in the background while booting: free -h -s1 to watch available process memory while loading into New World. As you might expect, available process memory approached 0 and the game process was killed.

I added a swapfile to my system, made an fstab entry, and rebooted to make sure I was repeating the above experiment with a clean slate. Upon loading in, I again saw the available process memory approach 0, but this time the kernal utilized the swapfile for the (seriously egregious) memory usage and I successfully loaded in.

[masonnl]

I can confirm that the expanded memory availability resolves the crash I was reporting as part of this compatibility report :tada:

To sum up my findings:

1. Sanity check dmesg to see if there's some system-wide problem that kills the game outside of Proton/Steam. In my case this was an obscene amount of memory use that caused oom-killer to end the NewWorld.exe process. Thank you @gofman for pointing me in this direction.
2. Changing the in-game settings while logged in to a character in New World uses A TON of memory. I resulted to restarting the game to change the visual settings from the main menu screen instead to prevent crashes even after I knew what the root cause was. A swapfile with 8GB is needed on my 16GB system to play on High settings. In game memory usage after 2 hours of gameplay was sitting at <11GB. VRAM was sitting at <6GB. PSA: I had to clear my swap when closing the game so that I could even get things to load upon reopening the game. If others are experiencing crashes related to memory, keep this in mind. If more experienced folks have insight in swappiness fine-tuning, I'd be interested in hearing from you!
3. Adjusting the visual settings did not resolve the stuttering. My settings are as follows, though keep in mind stuttering still occurs with minimum-possible settings (timeframes between 16-50ms consistently):

• Fullscreen (2560x1440)
• High
• vsync ON
• framecap: unlimited
• dynamic resolution: ON (using Proton's nvAPI env var, though I don't think NW utilizes it)

[kisak-valve]

New World (1063730)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5774. @hagenmt posted on 2022-04-19T03:54:17:

Compatibility Report

• Name of the game with compatibility issues: New World
• Steam AppID of the game: 1063730

System Information

Distro: Ubuntu 20.04.4 LTS Kernel: 5.13.0-39-generic RAM:32 GB GPU Driver:NVIDIA 510.54 GPU:NVIDIA GeForce GTX 1060 3GB CPU:Intel Core i7-8700 @ 3.20GHz

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

log for experimental (not bleeding edge run): experimental-steam-1063730.zip

log for 7.0.1: 701-steam-1063730.zip

Symptoms

Tried experimental, 7.0.1, and experimental bleeding edge. It crashes about 2-5 minutes into playing. Early on I was able to play for quite a while, but not that I have about 4-6 hours into the game it crashes every time almost instantly. I am sitting in the wilderness at this point just collecting some ore and hemp and it crashes usually about 3-4 resources nodes into collecting every time.

I only see this other New World issue reported: https://github.com/ValveSoftware/Proton/issues/5772 But it appears to be more related to memory issues, I have 32GB of memory and I have always had a swap file as well so I don't think they are the same issue?

Reproduction

Start steam Launcher options: PROTON_LOG=1 bash -c 'exec "${@/NewWorldLauncher.exe/bin64/NewWorld.exe}"' -- %command% Hit Play Select my character Search the near locations for some hemp or iron nodes and start mining Crash after about 3-4 nodes

[kisak-valve]

Hello @hagenmt, maybe DXVK is having a vram issue with this hint:

err:   D3D11: Cannot create texture:
err:     Format:  97
err:     Extent:  256x512x1
err:     Samples: 1
err:     Layers:  1
err:     Levels:  1
err:     Usage:   28
err:     Flags:   0

---

*** stack smashing detected ***: terminated looks like the actual dying message of the log, could be unrelated to the comment above.

[hagenmt]

Update: I upgraded to Ubuntu 22.04 as soon as it came out few days ago. Didn't help. When proton 7.0.2 came out though shortly after that, also didn't help but I switched to experimental bleeding edge after the 7.0.2 release and it appears the crashes are fixed! Still having the freezes that others have mentioned maybe texture loading related (which have lead to several untimely deaths). But the hard crashes appear to be resolved.

[inittux111]

I'm experiencing crashes/freezes with the game as well, do I add my information in this issue or do I create a new issue?

[kisak-valve]

Hello @Hydranet, we're using one issue report per unofficially supported game title. This is the right place for all information related to running New World with Proton.

[inittux111]

Compatibility Report

• Name of the game with compatibility issues: New World
• Steam AppID of the game: 1063730

System Information

• Distribution: Arch Linux
• GPU: RX 6700XT
• Driver/LLVM version: mesa 22.0.3-1 llvm 13.0.1-2
• Kernel version: 5.17.7-arch1-1
• Link to full system information report as Gist: System info
• Proton version: 7.0-2, but I have the same thing with Proton Experimental.
• Display server/Destkop Environment: Wayland/Sway
• Launch options: gamescope -ef -- gamemoderun PROTON_LOG=1 MANGOHUD=1 %command%

I confirm:

• [X ] that I haven't found an existing compatibility report for this game. (Adding it to this issue)
• [V ] that I have checked whether there are updates for my system available.

steam-1063730.log.gz

Symptoms

Every short while my game freezes and crashes, although I'm getting the impression it's happens more when I'm gaming and switch to my other monitor every now and then to do something on my other monitor but I'm not 100% sure.

Reproduction

1. Launch gaming and enter server.
2. Switch to second monitor to every 10-15 minutes
3. Switch back to my gaming monitor
4. Eventually the game freezes and crashes.

I will do some more testing tomorrow to see what happens if I play for a few hours without switching to my other monitor. If that gives different results I will add it as an update in this post.

[kisak-valve]

Hello @Hydranet, these look like some lines of interest from your log:

err:   D3D11: Cannot create texture:
err:     Format:  97
err:     Extent:  256x512x1
err:     Samples: 1
err:     Layers:  1
err:     Levels:  1
err:     Usage:   28
err:     Flags:   0
[...]
X connection to :99.0 broken (explicit kill or server shutdown).

Followed by an access violation (c0000005). I suspect that X (Xwayland) dying hints that there's a video driver issue to ponder.

[inittux111]

Hello @kisak-valve Thanks for your reply. So if I ran the game with Xorg I wouldn't be having this issue?

[madrang]

Was crashing randomly too much to play, but then I disabled the in-game voice chat and after that no more crashes.

[bmjsmith]

Was crashing randomly too much to play, but then I disabled the in-game voice chat and after that no more crashes.

Thanks - disabling this worked for me too. Up until I tried that I kept getting crashes with: *** stack smashing detected ***: terminated in the console log.

[Kuratius]

Note that the EAC support for this game seems to be semi-broken. You have to wait for it to error out and then immediately log in again without restarting the game every time you start the game.

[carlosglez]

Compatibility Report

• Name of the game with compatibility issues: New World
• Steam AppID of the game: 1063730

System Information

• GPU: NVIDIA GeForce RTX 2080 SUPER
• Driver/LLVM version: NVIDIA 515.65.01
• Kernel version: 5.10.136-1-MANJARO
• Gist:
• Proton version: 1662670002 experimental-bleeding-edge-7.0-24419-20220908-p892322-w0d8152-d5babb2-v2120b0

I confirm:

• [X] that I haven't found an existing compatibility report for this game.
• [X] that I have checked whether there are updates for my system available.

steam-1063730.log.zip

Symptoms

I have tried all Proton version, including Proton-GE. Game runs fine in all version except for the fact that the game crashes at random time-intervals. I have noticed that whenever I join an OPR/Instance and the game crashes, I will log back on to the OPR/instance and the game wont crash for the entire duration of the OPR/instance (Doesn't matter how long the opr/instance takes) until it is over and I get ported back out.

Reproduction

Start steam Launcher options: PROTON_LOG=1 bash -c 'exec "${@/NewWorldLauncher.exe/bin64/NewWorld.exe}"' -- %command% Hit Play Select my character Run around a little, cast a few spells, queue up for OPR. Join OPR. If lucky I will join the OPR before game crashes, otherwise game will crash inside the OPR.

[kisak-valve]

From the log: *** stack smashing detected ***: terminated, which is a symptom, not a cause.

[carlosglez]

From the log: *** stack smashing detected ***: terminated, which is a symptom, not a cause.

Thanks, im pretty new to linux. So I wouldn't know what that means. How do I fix it or further debug it?

I restarted the pc without opening anything else other than steam. Not sure if this is helpful at all but I got another log with the same issue. I also ran dmesg and got the SteamLinuxRuntime_soldier log. Let me know if there's anything else I can/should do

steam-1063730-1.log.zip

dmesg

SteamLinuxRuntime_soldier

Thanks :)

[carlosglez]

Replying to https://github.com/ValveSoftware/Proton/issues/5772#issuecomment-1241458923

Upgrading my Kernel from 5.10 LTS to 5.15 LTS resolved the issues with game crashing

[hakzsam]

Are you still able to reproduce issues with Mesa and up-to-date drivers? If so, can you explain how to reproduce? Thanks!

[Mungoid]

Not sure if it will help but disabling Steam overlay for NW seemed to fix the random crashes for me

[KernicDE]

Compatibility Report

Name of the game with compatibility issues: New World
Steam AppID of the game: 1063730

System Information

Distribution: Arch Linux
GPU: NVidia RTX 3080 FE
Driver/LLVM version: 515.76
Kernel version: 5.19.12-zen1-1-zen
Proton version: ProtonGE7-36
Display server/Destkop Environment: Wayland/Gnome
Launch options: gamemoderun mangohud DXVK_ASYNC=1 PROTON_ENABLE_NVAPI=1 %command%

I confirm:

[X] that I haven't found an existing compatibility report for this game. (Adding it to this issue)
[X] that I have checked whether there are updates for my system available.

Symptoms

When logging in while in Windsward or porting to Windsward, then the game crashes most of the time. According to top the game eats up the whole memory (the free 12Gb out of 16Gb), then goes to swap and eats there 7-8Gb, then crashes. Seems like a memory leak.
I assume, that Windsward is just the case, because it's the most populated city. First I wasn't able to login at all, as I just had 4Gb of swap. After reading here, I added another 32Gb of swap and this allows me to log in in 1 of 10 times. Steam Overlay is deactivated too.

Logging in or porting anywhere else instead of Windsward is working for me.

1. Log off in Windsward.
2. Start game.
3. Log into character.
4. See loading screen.
5. Crash back to desktop.

• I tried different Proton versions (stable, experimental, GE7-34 to GE7-36).
• I tried over several weeks, always with up-to-date system and drivers.
• I tried to repair the files.
• I removed the shader cache, no help (so starting without cache).
• I redownloaded the shader cache, no help.
• I tried with different and no Launch options.

[Apheloniush]

I have the same issue as above. Ported to Windsward and NW started crashing so my main character is locked. I actually fed it 48gb of swap and still no go. Replicated on Nobara Manjaro Ubuntu Endeavour and many many many proton versions official ones included I should mention that i can log on my second char outside Windsward no problem and play for few hours Attached a proton log as well

steam-1063730.log

[kamek-pf]

Not a proper fix as there's definitely some memory issues with this game, but setting up zram generator allows me to login/port to busy areas like Windsward. It would previously crash there, 9 times out of 10, and I haven't had a single crash since.

It does swap a lot though, and the loading screen lasts for about a minute, but it doesn't crash anymore. I haven't noticed performance issues once the loading completes.

My zram config is pretty basic and adds a 16 Gb swap file. /etc/systemd/zram-generator.conf :

[zram0]
zram-size = ram

[FBRZGGN]

Hello, I have the same issue as described by @eXeler0n above . I can confirm that the issue appears always during loading screens. To bypass it I created 16Gb of swap (I have 16Gb of RAM) and during the first loading screen NW used about 20Gb. As @kamek-pf said, I try to used zram-generator, but I can make it works. I created a question on serverfault to get help. But even without using zram, after the first loading screen, the game is perfectly playable.