Skip to content

Elden Ring: EAC fails to load, gives Launch Error: "Unexpected Error: #1" #7452

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ConHuevosGuey opened this issue Jan 28, 2024 · 1 comment

Comments

@ConHuevosGuey
Copy link

Compatibility Report

  • Name of the game with compatibility issues: Elden Ring
  • Steam AppID of the game:

System Information

  • Distrobution: Slackware 15.0
  • GPU: Nvidia RTX 3090ti
  • Video driver version: Nvidia 545.29.06
  • Kernel version: 6.1.66
  • Proton version: Proton Experimental (Tried all available versions as well)

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.

Symptoms

When launching the game the EAC popup occurs, attempts to load then has the title "Launch Error" with "Unexpected Error: #1" and the game must exit.

Reproduction

Launch the game.

Comments

I can find no other error logs as to why EAC keeps faiiling when loading. If I use the flatpak version of steam, the game loads fine and EAC loads correctly and I can play online using Steam's flatpak version. The game ran perfectly fine, including loading EAC when glibc 2.33 was installed. However after updating glibc I continued to keep getting error #1 on the EAC loading banner. I've confirmed with others that the game does indeed work with my current version of glibc (2.38), however they are Arch and Nobara distrobutions.

I'm unsure what the cause of this issue as I cannot find any information on error #1 or how to further troubleshoot it. Nothing appears to fail in the logs and it simply seems to be the EAC module failing to load correctly for some reason.

@kisak-valve
Copy link
Member

Hello @ConHuevosGuey, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to #5613 (comment).

@kisak-valve kisak-valve closed this as not planned Won't fix, can't repro, duplicate, stale Jan 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants