Sea Of Thieves (1172620)

[mdiluz]

Compatibility Report

• Name of the game with compatibility issues: Sea Of Thieves
• Steam AppID of the game: 1172620

System Information

• GPU: RTX 2070 Super
• Driver/LLVM version: Nvidia 440.82
• Kernel version: 5.4.0-7629-generic
• Link to full system information report as Gist: https://gist.github.com/mdiluz/f93729686e9ffdf031226844e1d3a7de
• Proton version: proton-5.0-7

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.

steam-1172620.log

Symptoms

The game loads up to the main menu, but clicking Start Game tries to open the Xbox live sign-in window and then crashes
Update for tracking current issues:

1. Voice chat is non-functional
2. Requires Xbox Live login on each start up
3. First launch is very slow
4. Cloud rendering is incorrect

Reproduction

1. Launch the game
2. Press Start Game
3. Observe crash Play game and observe above issues

[mdiluz]

The crash stack is unsymbolicated but is inside libcef:

Backtrace:
=>0 0x00007f824b003b57 EntryPoint+0x7f81fe73b167() in libcef (0x0000000000000007)
  1 0x00007f824a41efae EntryPoint+0x7f81fdb565bd() in libcef (0x0000000000000007)
  2 0x00007f824b2962cf EntryPoint+0x7f81fe9cd8de() in libcef (0x0000000000000007)
  3 0x00007f824b295798 EntryPoint+0x7f81fe9ccda7() in libcef (0x0000000000000007)
  4 0x00007f82497cfe4d EntryPoint+0x7f81fcf0745c() in libcef (0x0000000000000007)
  5 0x00007f82497cf994 EntryPoint+0x7f81fcf06fa3() in libcef (0x000000000022d800)
  6 0x00007f830d95fa75 EditWndProcA+0xa54() in user32 (0x000000000022d8f8)
0x00007f824b003b57 EntryPoint+0x7f81fe73b167 in libcef: movq	(%rcx),%rax

[richardtatum]

I am also able to reproduce this error, however I was able to get further than @mdiluz using Proton-5.8-GE-2-MF.

I was successfully able to do the following:

• Launch the game
• Select Start Game
• Sign in with a Microsoft Account
• Link my Steam account to my Microsoft Account
• Game proceeds to load

The game will then crash at the 'Loading Journal' section.

Log: steam-1172620.log

[ga2mer]

Does not crashing on proton 5.0-7 with win7, after login stuck on "ship supplies" message (or something) and then gives this error

Game services are not available. Try later (Daffodilbeard)

Log - steam-1172620.log

[kisak-valve]

Hello @ga2mer, fixme:vulkan:X11DRV_vkCreateWin32SurfaceKHR Application requires child window rendering, which is not implemented yet! in the log points towards https://bugs.winehq.org/show_bug.cgi?id=45277.

[mdiluz]

Just in case it matters I've also confirmed I have the same issue with Proton 5.0-8 RC

[ga2mer]

Same with Proton-5.9-GE-1-MF (with Vulkan child window patch) and setting prefix to win7 (win10 crashed on default proton on xbox live auth and on journal with GE) it passed journal and stucks on daffodilbeard (screenshot in my above comment)
Log - steam-1172620.log
I think issue with creating http request:

fixme:wininet:query_global_option Stub for 105
fixme:wininet:InternetSetOptionW Option 77 STUB
fixme:winhttp:request_set_option unimplemented option 114

[l33tlinuxh4x0r]

Has anyone found a workaround or fix for Sea Of Thieves yet?

Also confirmed not working with proton or proton-ge on archlinux.

[muni-corn]

Would also love to know if anyone's got a workaround yet, but my bug report is a little different:

• I can start the game
• I can sign into Xbox Live
• The game will load up until "Loading supplies," and then error with Cyanbeard (Your connection to Xbox Live has been lost) even with a stable Internet connection. I can try again without the game crashing, but I'll come back around to Cyanbeard most of the time, and Daffodilbeard less than half the time.

I'll figure out how to get a debug log or something and report back here.

Edit: Here's the log

[Rogue-Factor]

I believe this is an issue that's been around since 2018-ish? Or at least has been apparent.

Child Window rendering dxvk bug:
https://bugs.winehq.org/show_bug.cgi?id=45277

Felix Hädicke seems to have committed a patch last year to address some of these issues.
felixhaedicke/wine@258a826

But even with this patch from Felix Hädicke, it seems that someone needs to figure out "Option 114" for "winhttp:request_set_option" in order to progress any further.

WinHttpRequest-Option Reference

Might be speaking out of my buttocks by this, but did anyone try using native winhttp instead of builtin? I don't own the game on steam yet so I've yet to try.

wininet=builtin winihttp=native

EDITED: My bad, forgot to put options for wine/protontricks.

[l33tlinuxh4x0r]

I can't get the game to run at all with the settings from the above comment. I will play around a bit more.
EDIT: update, only default settings get the game to boot reguarding wininet and winhttp.

[ga2mer]

Looks like game wants websocket in winhttp, i returned true with 114 request_set_option and it's crashed on
wine: Call from 0x7bc8c9bc to unimplemented function WINHTTP.dll.WinHttpWebSocketCompleteUpgrade, aborting

[Toxblh]

I can start game
And also login to xbox live
But can't to connect to server with Proton 4.11-13
And can't to login to xbox live with Proton 5.0-7

Kernel: 5.6.15-1-MANJARO
GeForce RTX 2080Ti / NVIDIA 440.82

[Trelaire]

I can link my account now, perhaps because I install protontricks (but I don't use it for launch) and launch it with 4.11, it works now withon proton 5.0 or 4.11, I wasn't able to link account before.
But can't connect to serveur like above. "the sea of thieves services are temporaly unavailable. Please try again (Daffodibeard)."

[l33tlinuxh4x0r]

For what it is worth people saying that proton 4.11 is working better than 5.0 it is because proton 4.11 defaulted to windows 7 and proton 5.0 defaults to windows 10. It was posted earlier in this bug that windows 7 works better... I don't believe that there is any other reason why the older proton would be any better. Hope that this helps.

EDIT: Also has anyone tried installing "windows dlls/components" in proton tricks?

[Trelaire]

I agree, for me it's working also with 5.0 (but same error "Daffodibeard").
I read somewhere that's Daffodibeard error can be caused by ipv4 (or ipv6 ?..) settings.
I try to desactivate ipv6, but it doesn't change anything.

EDIT : there it is ùy sources :
"I found that it was my router security settings were to high and was denying sot. I don't know why it's this way, no problem with any other game. Basically went into its IP ex:192.168.0.2. login and change ip4 settings to low. It fixed my problem instantly. Hope this helps any some way."
https://www.seaofthieves.com/forum/topic/38392/daffodil-beard/4

[l33tlinuxh4x0r]

I tried DMZ earlier but it didn't help. I have not disabled ipv6 yet though.

[Trelaire]

I try with a manual IP connection, but that's still don't work

[muni-corn]

Update from me: After installing some dlls and components as suggested by @l33tlinuxh4x0r , SoT is now crashing on Proton 5: steam-1172620-after-dll-components.log

Downgrading to Proton 4.11-13, I started getting Cyanbeard again, as before: steam-1172620-proton-4_11-13.log

[l33tlinuxh4x0r]

Update from me: After installing some dlls and components as suggested by @l33tlinuxh4x0r , SoT is now crashing on Proton 5: steam-1172620-after-dll-components.log

Downgrading to Proton 4.11-13, I started getting Cyanbeard again, as before: steam-1172620-proton-4_11-13.log

I can confirm that adding wininet and winhttp causes issues described above.

[hopethisgettingfixedfast]

Hi,
used Proton version 4.11-13 ... now 5.0-7 the only problem i have is :
DaffodilBeard
Something has happened on our side that we're working to fix. Please check the status of the game at seaofthieves.com for more information.
:(, same problem like you.

[Trelaire]

I tried to use protontricks and here is what happened :
I use this terminal command : "protontricks [game ID] winecfg" with proton 4.11 and proton 5.0.
When winecfg is on "windows 10" (or 8.1 8.0), it launch and crash on the Xbox link pop up.
When winecfg is on "windows 7" (or 2008 R2) it launch and we have the DaffodilBeard error.

Perhaps people who have pop up crashes have their proton's winecfg on windows 10 and the DoffodilBeard's other window 7 ?

I don't know if that will help...

[sysofd]

System information:
Wine build: wine-5.9 (Staging)
Platform: x86_64
Version: Windows 10
Host system: Linux
Host version: 5.6.14-300.fc32.x86_64

I comfirmed this problem, plz fix it =)

[DeanonQQ]

Same problem. Please fix it. I believe you can do it!

[ga2mer]

😉

winhttp dll | source/patch for wine
(drop winhttp.dll in ~/.steam/root/compatibilitytools.d/Proton-5.9-GE-1-MF/dist/lib64/wine/ (backup old))
also set win7 on prefix (via protontricks), it avoid crash on xbox login
Builded on GE proton(5.9 probably), I don’t know how it will work with other versions and whether it works at all, but I'm in the gameplay

Issue - websockets, I wrote bad code for implement few methods (upgrade and send) and looks like it's working

[l33tlinuxh4x0r]

😉

Any details on how you got it working???

[muni-corn]

@l33tlinuxh4x0r Looks like they posted an edit. Exciting! I'll try this solution out once I get time.

[Zorrototo]

OK so previous game update broke the game on Proton, current game update unbroke the game on Proton.

[kisak-valve]

Sea of Thieves

Issue transferred from #7810.
@Iancooles posted on 2024-06-03T17:51:09:

Compatibility Report

• Name of the game with compatibility issues: Sea of Thieves
• Steam AppID of the game: 1172620

System Information

• GPU: AMD Radeon RX 7900 XT
• Video driver version: Mesa 24.1.0-arch1.1
• Kernel version: 6.9.3-1-cachyos-bore-lto
• Link to full system information report as Gist: https://gist.github.com/Iancooles/241e9796e95feda0ddae522fb0997163
• Proton version: 9.0-1

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.

Symptoms

In the last month when I start the game, it asks me to sign in even though I already have my Xbox account linked. However, when the sign in window opens up, its completely black with no way to input anything. This has prevented me from playing the game for a while now with no workarounds to be seen.

Reproduction

1. Download the game on a Linux based operating system and then run it.
2. When the at the title screen, click "Start Game"
3. A black window pops up that won't let you sign in.
4. Congratulations, the game you paid for doesn't let you play anymore.

steam-1172620.log

[Zorrototo]

Delete your prefix, make sure in Steam Settings you have selected Proton 9 as a version, check in the game Properties in Steam if you have a custom version of Proton selected, and disable it if so (to use the version set in Steam Settings; no customization).

It should recreate a fresh Proton prefix when you'll start the game, in which you will have to login.

[Iancooles]

Thanks for the advice. Unfortunately, this didn't work. I'm still getting the same issue.

[simifor]

@Iancooles I tried the game with a clean prefix with both proton 9 and the release candidate for 9.0.2 and the sign-in loaded both times. The login window is initially black, but it shows properly after a few seconds.

[Iancooles]

This hasn't worked for me as I've left it open for minutes on end, and each time the login window doesn't change from its black color. I don't know what I'm doing wrong.

[Patola]

I've got the same issue as @Iancooles. Also RX7900XTX but in arch, tried proton experimental and proton 9.0-1 to no avail (removing the prefix between attempts). Steam Runtime System Info System Information

Funny thing is, the black window seems to have a text entry field, when I hovered the cursor over some areas it changes to a text input cursor, and below them there are clickable sections.

[Zorrototo]

Proton log?
Tried to start with no Launch Options if applicable?
Tried X11 instead of Wayland if applicable?

[Patola]

Proton log? Tried to start with no Launch Options if applicable? Tried X11 instead of Wayland if applicable?

Yeah, you were right. Removing the launch parameters didn't help, but switching to X11 (icewm) and launching the game allowed me to log in. Once I've logged in, I exited the game and went back to KDE 6 Plasma and started it again and it worked with me logged in.

I suspect that next time my login cookie for this game expires, maybe using gamescope can help.

[kisak-valve]

Hello @Iancooles, @Patola, can you both note what version of xwayland you're using?

I suspect it's 24.1.0 and you've encountered a regression that might be fixed with https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1564.

[Patola]

xorg-xwayland 24.1.0-1 with wayland 1.23.0-1

[simifor]

@Patola @Iancooles Testing on a wayland session I was able to reproduce the black sign in window, it 's the same issue mentioned by kisak, and having compiled xorg-xwayland with the mentioned merge request I can confirm that it lets it load normally, so the issue should be solved when there's a release with the merge request.

[DiarrheaMcgee]

about 60% of the time when i open the game it crashes with

There is a missing or corrupt data file that is required for the game to run.
For more information blah blah blah
...
Data file:
../../../Athena/Content/Paks/Core_something.pak
Referencer: N/A
Error code: P06

and when it does open successfully it crashes after around 30 minutes

i just reinstalled the game and got the md5 sum from all the pak files then started the game

it crashed with the same error and when i checked the current hash of all the pak files including the one it says is corrupted it was the same as the hash after installing it

[Zorrototo]

https://support.seaofthieves.com/articles/360016232274-Troubleshooting-error-There-is-a-missing-or-corrupt-data-file-that-is-required-for-the-game-to-run

[DiarrheaMcgee]

why would it be corrupted after a reinstall

[Zorrototo]

The file is not corrupt.

Many things to explore regarding the link, and potential issues on the system.
Also you gave no information at all about your system and setup of the game in Steam.
Recreate the prefix on latest Proton 9 (no experimental, the plain basic Proton 9).

Issue is on your end.

[DiarrheaMcgee]

proton 9
6.8.12-gentoo
i suppose i could be unlucky and its on my end but this has persisted accross a couple of reinstalls across distros
and its happening on another computer using artix and another computer somewhere else using void

[Lifeismana]

@DiarrheaMcgee What's the filesystem you installed sea of thieves on? I had that happen when sea of thieves was on a btrfs partition (with compression enabled) moving the game to an ext4 partition fixed that

[DiarrheaMcgee]

im using zfs but since steam zfs support broke for some reason i have it on a separate ssd using xfs
the artix one is using xfs
and the other one is using ext4 or xfs (i forgot which one but its probably ext4)

[DiarrheaMcgee]

should i just delete all the pak files and let steam redownload them

[ChrisLane]

The workaround that I found on ProtonDB for the Microsoft login window issues was to launch with PROTON_USE_WINED3D=1 %command%.

This fixed the window not being visible on Sway and completely black on Game scope such that I was able to login and then remove the flag to actually play.
I'll try the xorg-xwayland patch too.

[Zorrototo]

This Launch Option is to disable Vulkan and use OpenGL to run the game.

[rudolf-enum]

I am experiencing the same issue consistently just like @DiarrheaMcgee .

I am running Alpine Linux. Artix and Void share one thing with Alpine: They don't use systemd. Could this be the underlying issue somehow? This is so far the only game I'm experiencing issues with.

Edit: I would also like to note that I have had this exact install of the game running before, that is, before I installed Alpine over Debian. But aside from the distro, everything is the same, as the disk(s) with the game have gone untouched.

[rudolf-enum]

I managed to figure it out! Sea of Thieves doesn't run for very long on non-systemd distributions because systemd overwrites the default limit of 4096 file descriptors, and Sea of Thieves/Athena/Content/Paks/ alone is 2134 files as of the time of writing this.

So the solution was as follows, 524288 being the recommended/minimum amount for ESYNC:

# echo "myusername hard nofile 524288" >> /etc/security/limits.conf
# reboot

I guess it would be great if Proton could have a warning. There has been a FR in the past #1970 but has been dismissed due to the fact that systemd always has "fixed" the issue. My naive solution would be that Proton could simply run ulimit -Hn and check if the output is atleast 524288 and logging out a WARN if not.

[Zorrototo]

I guess such warnings could be added to Proton, but is that really Proton's issue to make sure your system can open enough files to run your applications? Especially if this is a requirement of some features of Proton?

//EDIT: anyway, this will not be added as it is the default for systemd now to have higher value.

I was going through closing old issues that won't be acted on. Systemd raised the default limit and we haven't seen users running into this issue in a long time. If you're still encountering a low limit, you should raise the issue with your distribution.

[rudolf-enum]

(oops, sent the comment too early)

If systemd is considered the only platform for Proton, then so be it. People could also theoretically lower the value themselves for whichever reason though. Or systemd could lower it in the future arbitrarily. Or a distribution could change the value within their build of systemd.

But to answer your question:

is that really Proton's issue to make sure your system can open enough files to run your applications? Especially if this is a requirement of some features of Proton?

I would say that you've answered the question: It's a requirement of some of its features, so therefore it should at least give out a warning.

[Zorrototo]

For the sake of agruing, I would say if SystemD is expected (originally Proton was worked on on Ubuntu if I recall correctly, and now Arch, two SystemD based distros), then there is no issue. Only if you use a distro without SystemD would this warning be relevant and from my understanding, SystemD based distro is an implicit requirement.

From what I know about Steam and Proton development, just move on, nothing will be done about that issue as it would probably considered a non issue.