New World: Aeternum (1063730)

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:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.
• 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...
• 💥 back to desktop
  • ⚠️ 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 🤷

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).

Review the linked system gist, Proton logs, and both reproduction scenarios, starting with the compressed log rather than the truncated head. Compare the reported behavior across Proton 7.0-1 and GE-Proton7-14; the issue does not name a source file or test, and done would require a confirmed cause and reproducible resolution.