Skip to content
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

Halo: The Master Chief Collection (976730) #2907

Open
1 task
trymeouteh opened this issue Jul 24, 2019 · 890 comments
Open
1 task

Halo: The Master Chief Collection (976730) #2907

trymeouteh opened this issue Jul 24, 2019 · 890 comments
Labels
Game compatibility - Unofficial Games not expected to work without issues Mesa drivers Possibly involves an issue with a Mesa video driver Regression Confirmed working on an older version of Proton XAudio2 Uses the XAudio2 subsystem

Comments

@trymeouteh
Copy link

Compatibility Report

  • Name of the game with compatibility issues: Halo: The Master Chief Collection
  • Steam AppID of the game: 976730

System Information

  • GPU:
  • Driver/LLVM version:
  • Kernel version:
  • Link to full system information report as Gist:
  • Proton version:

I confirm:

  • that I haven't found an existing compatibility report for this game.

Symptoms

Game will not launch

Reproduction

  1. Start Game
    2.Will not show Microsoft Login Prompt

Notes

I do not have this game but I got the details of this issue from this reddit post.

https://www.reddit.com/r/linux_gaming/comments/c6xh55/halo_reach_through_proton/

@warriormaster12
Copy link

I can also confirm that the issue is that Microsoft login prompt doesn show up.

@kisak-valve kisak-valve added the Game compatibility - Unofficial Games not expected to work without issues label Jul 24, 2019
@kisak-valve
Copy link
Member

Hello @warriormaster12, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

@flibitijibibo
Copy link
Contributor

flibitijibibo commented Aug 24, 2019

Dug into the latest Flighting build. Notes:

  • EAC binaries in the root folder
  • Appears to use UE4's Chromium support?!
  • Audio is FMOD-based EDIT: Still references XAudio2, fsbs are just l18n...
  • Movies appear to be Bink2 this time around (previously it was WMA)

The game boots but fails to prep Xbox Live, so not much has changed.

steam-1064280.log

@d10sfan
Copy link

d10sfan commented Aug 24, 2019

Also tried, goes to the menu screen but get error when trying to proceed further.

@elken
Copy link

elken commented Aug 24, 2019

+1 comments don't extend the discussion. Just use thumbs up.

I've tried adding win10 and dxvk to no avail, maybe dependant on some gfwl libs?

@trymeouteh
Copy link
Author

I do not have the beta but I heard this game is supported for Windows 7. Maybe try setting the wine config to Windows 7 to get the Xbox Live part to work?

@d10sfan
Copy link

d10sfan commented Aug 24, 2019

I do not have the beta but I heard this game is supported for Windows 7. Maybe try setting the wine config to Windows 7 to get the Xbox Live part to work?

It looks like the default is Windows 7 from what I saw in winecfg. I attempted to set to Windows 10 and got the same result.

Like you said, since the game is supposed to work under Windows 7, it seems it would have the necessary pieces to login to Xbox Live in the actual game, but not sure.

Maybe there's something wrong with the loading of CEF itself to show the login window. Are there any necessary manually installed libraries for the webview to work for other games/tools?

@flibitijibibo
Copy link
Contributor

CEF by design is pretty much 100% standalone, though lots of files get involved even in a minimal package. Where things get bad, in my experience, is the Chromium subprocesses. I have zero evidence that it’s relevant here.

@flibitijibibo
Copy link
Contributor

Apparently I’m insanely far behind on my MCC news. The core UI engine is actually UE4 now! So it’s UE4 at the base with each game’s original engine running on top. This is likely because Scaleform’s dead, so they had to move to something...

If there exists a UE4 CEF demo app, that might be a good thing to test with upstream Wine.

@d10sfan
Copy link

d10sfan commented Aug 24, 2019

It's possible they are using the ue4 web browser (https://docs.unrealengine.com/en-US/Engine/UMG/UserGuide/WidgetTypeReference/WebBrowser/index.html), unless they did their own implementation of the cef integration.

It could also be useful to try cef by itself. From what I remember these packages have example cef browsers that could be useful for determining compatibility: http://opensource.spotify.com/cefbuilds/index.html

I saw that a while back people were recommending using wine staging patches for cef to work properly in wine, not sure if that's still the case

@d10sfan
Copy link

d10sfan commented Aug 25, 2019

As an experiment, I took the Windows 64-bit sample app from cefbuilds and ran it on the following:

  • wine-4.13 - webview portion blank
  • Proton 4.11 - webview portion blank
  • Proton-GE 4.14 - webview loads, trying to go anywhere but google redirects back, may be limitation of sample app
  • Proton-tgk 4.12 - webview loads, trying to go anywhere but google redirects back, may be limitation of sample app

The last two proton forks look to provide the wine staging patches, with some of them probably helping with getting CEF to work. I tried MCC with Proton-GE 4.14, and got a different result, where pressing enter caused a "Fatal Error" popup to occur. I've attached the logs below, it may be getting a bit closer: steam-1064280.log

@craftycodie
Copy link

This issue is for Halo: The Master Chief Collection - INSIDER, app id 1064280 and should probably be updated to keep pre-release issues separate from release issues.

@flibitijibibo
Copy link
Contributor

There does appear to be a lot of OutputDebugString calls for HttpClient, with the addresses and functions lining up with this library here:

https://github.com/microsoft/libHttpClient

Kind of makes me wonder what the CEF part is all about if the Xbox Live sign-in is going through this instead.

@flibitijibibo flibitijibibo added the XAudio2 Uses the XAudio2 subsystem label Aug 26, 2019
@trymeouteh
Copy link
Author

https://www.protondb.com/app/976730

It will appear that this game uses EasyAntiCheat. I hope Anti Cheat can be worked around in the near future.

@Kylindrias
Copy link

steam-1064280.log

Here's another log. Same issue, Error signing into XBox Live. Sign in dialogue doesn't show. Also don't seem to hear any sound in the menus and during the logo animations.

@flibitijibibo
Copy link
Contributor

flibitijibibo commented Nov 13, 2019

Log from the Flight 3 build:

steam-1064280.log.zip

Audio seems fine here, as are all the videos now that they're on Bink2. The base engine appears to use standard UE4 audio through XAudio2, but Reach's audio is stored as FMOD Studio banks and the FMOD library is statically linked into the game DLL. Logging in still doesn't work, still seems to be HttpClient compatibility issues.

@solenum
Copy link

solenum commented Dec 3, 2019

Steam release, running the EAC-disabled version I get stuck at the xbox live login screen.

Log below.

steam-976730.log

@flibitijibibo
Copy link
Contributor

flibitijibibo commented Dec 3, 2019

Tried the release version with 4.11 with an updated bcrypt+winhttp, didn't get past login. Noticing that it hits a stub for WSALookupServiceBeginW.

steam-976730.log

@jerebare
Copy link

jerebare commented Dec 3, 2019

Stuck on connecting to xbox live.

KDE neon User Edition 5.17
5.0.0-37 kernel

steam-976730.log

@KeithSantamaria
Copy link

So I launched the game, got a dialog box: one with anti cheat and one without. When trying the without anti cheat option I have the same issue with the xbox live login.

Here is my steam log
steam-976730.log

@dennis1248
Copy link

dennis1248 commented Dec 3, 2019

Game launches but doesn't manage to get to the login, "Errors encountered while signing into Xbox Live"

Running the game without EAC: steam-976730.log

@mathew2214
Copy link

mathew2214 commented Dec 3, 2019

i have the same issue as everybody else it seems. gets to title screen, but cannot proceed because of an Xbox Live error.
steam-976730.log

i believe this is the error causing the xbox live issue.
ERROR:network_change_notifier_win.cc(156)] WSALookupServiceBegin failed with: 8

@NTMan
Copy link

NTMan commented Dec 3, 2019

The game is launching but couldn't signing into Xbox Live

steam-976730.log

Screenshot from 2019-12-04 00-16-04

@McMarius11
Copy link

i have the same error can't sign in
steam-976730.log

Manjaro
Nvidia

@ltodoto
Copy link

ltodoto commented Dec 3, 2019

Does the following line indicate an issue:
fixme:bcrypt:key_asymmetric_generate algorithm 11 not supported
?
Wine spews it each time I try to hit 'Retry'.
P. S. 11 corresponds to the ALG_ID_ECDSA_P256 enumeration value.

@mathew2214
Copy link

looks like an issue with wine's bcrypt and winhttp implementations.
is there a way to force Proton to use a newer version of wine instead of the default 4.11?
there have been a number of commits to wine that relate to bcrypt since 4.11.

@Guy1524
Copy link
Contributor

Guy1524 commented Dec 3, 2019

@mathew2214 It doesn't work on a recent wine staging with windows steam either, I'm taking a look at fixing this.

@Xeraster
Copy link

Xeraster commented Dec 3, 2019

This game is pretty broken even on Windows. As in I've been troubleshooting all day and can't get the damn thing to get past that sign in error even on an actual Windows 10 Pro installation.

It's ironic that at this rate, the Linux community might get it working in Linux before it's even functional for most people on Windows.

@leohearts
Copy link

For me I've mentioned that it's sending packet through my proxy . So I unset my http_proxy and https_proxy , reboot, then it works well.

@danilw
Copy link

danilw commented Jul 29, 2023

I can confirm - now Halo MCC with EAC/anticheat work out-of-box in PC Linux, OpenSuSe for me.
I installed and launched "HaloMCC with EAC enabled" from Steam - saw EAC loading, not crashing, and Multiplayer and everything in game working. I played multiplayer game, from start to end - everything works.

@rhabacker
Copy link

rhabacker commented Aug 8, 2023

I get a "fatal error" when running halo 4 on openSUSE Leap 15.4 regardless of MCC enabled or not. - see the logs

@kisak-valve
Copy link
Member

Hello @rhabacker, can you check how the game behaves without PROTON_USE_WINED3D=1. This runtime option is not considered supported.

@rhabacker
Copy link

Without this option it reports:
grafik

@kisak-valve
Copy link
Member

That hints that you do not have a usable Vulkan driver for DXVK to use. Please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

@rhabacker
Copy link

Thanks for your feedback - see Steam Diagnostics

@orowith2os
Copy link

@rhabacker your NVIDIA GPU doesn't have any support for Vulkan 1.3, which Proton 8 and newer requires. You can go back to Proton 7, which should still work for those with <= VK 1.2 capabilities, but eventually you'll need a new GPU, or a new system.

        "renderer" : "NVIDIA GeForce GTX 660",
          "version" : "470.199.02",
          "devices" : [
            {
              "name" : "NVIDIA GeForce GTX 660",
              "api-version" : "1.2.175",
              "vulkan-driver-id" : 4,
              "driver-name" : "NVIDIA",
              "driver-version" : "470.199.02",
              "vendor-id" : "0x10de",
              "device-id" : "0x11c0",
              "type" : "discrete-gpu"
            }
          ]

@rhabacker
Copy link

your NVIDIA GPU doesn't have any support for Vulkan 1.3, which Proton 8 and newer requires

Thanks for your support - would it be possible for Proton to make this lack of support more visible to the user? That would save a lot of effort to find out the cause.

you can go back to Proton 7

I will try this.

@rhabacker
Copy link

I will try this.

proton 7 works.

@orowith2os
Copy link

would it be possible for Proton to make this lack of support more visible to the user? That would save a lot of effort to find out the cause.

You just saw it :)

Steam could, and probably should tbh, check for GPU capabilities and issue a little warning that things might not work if that's the case. There's probably an issue tracking that somewhere.

@waspennator
Copy link

Apparently the latest update broke anti cheat support on Linux.

@SeongGino
Copy link

For any affected users; have they tried uninstalling the game, fully removing any residual MCC folders, and reinstalling? That's how I fixed it the past two times (it's the exact same error too...).

Regardless, this seems to have been a residual problem that I have no clue what's causing it, but may be MCC itself.

@molecula451
Copy link

MCC, works fine to me proton-8.0-3

@hdansin
Copy link

hdansin commented Sep 21, 2023

Throws a catalogue error for me, Proton Experimental and Proton 8.0.3 on Solus Linux. 343 Why?!

@waspennator
Copy link

https://twitter.com/halosupport/status/1704979565318418783?s=46&t=JYmA-3Ed5oIPTOE9SY6b1g

Devs seem to be aware or the anti cheat issues goin on.

@pongo1231
Copy link

The issue seems to have been resolved now, I can join multiplayer matches again.

@parkerlreed
Copy link

Yeah anti-cheat was addressed here (Just not in the notes)

https://steamdb.info/patchnotes/12093519/

@poperigby
Copy link

Is the co-op desyncing without ucrtbase.dll something that can be addressed in Proton? It's kind of a big deal.

@SeongGino
Copy link

SeongGino commented Dec 10, 2023

Perhaps it would require pre-installing a real vcrun2022 package as part of the prefix setup (which I thought Proton already did for many of its prefixes by default?). Just my own conjecture though.

In absence of this, Proton-GE fork can be used, which does have exactly this as a protonfix.

@poperigby
Copy link

I just tried with Proton GE, and it still had the issue. It only works if I follow these instructions from GlenMerlin ProtonDB:

mkdir /tmp/ucrtbase
cd /tmp/ucrtbase
wget https://download.microsoft.com/download/9/3/F/93FCF1E7-E6A4-478B-96E7-D4B285925B00/vc_redist.x64.exe
cabextract vc_redist.x64.exe
cabextract a10
chmod u+w "[/path/to/steamapps]/compatdata/976730/pfx/drive_c/windows/system32/ucrtbase.dll"
yes | cp ucrtbase.dll "[/path/to/steamapps]/compatdata/976730/pfx/drive_c/windows/system32"

@SeongGino
Copy link

SeongGino commented Dec 12, 2023

Replying to #2907 (comment)

Protonfixes only come into play with a clean prefix, btw. So you won't see any change if you made your prefix with upstream then change to GE.
Don't know how it wouldn't work otherwise, given it literally is installing visual C redists like what that text guide is basically describing in a longer-winded fashion.

(Or, not even that--just one command: protontricks 976730 vcrun2022)

@poperigby
Copy link

@SeongGino I deleted my prefix, switched to Proton GE 8.16. It still didn't work.

@kekkoudesu

This comment was marked as outdated.

@kekkoudesu

This comment was marked as outdated.

@kekkoudesu
Copy link

Halo: MCC still works on Arch Linux with glibc 2.39-1.

@mathew2214
Copy link

mathew2214 commented Mar 23, 2024

as of march 2024, coop campaign doesnt work. just constantly disconnects.
steam deck

@pongo1231
Copy link

This workaround is still necessary for coop to work properly (if the other person is using Windows at least, not sure if Linux + Linux combination works out of the box).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Game compatibility - Unofficial Games not expected to work without issues Mesa drivers Possibly involves an issue with a Mesa video driver Regression Confirmed working on an older version of Proton XAudio2 Uses the XAudio2 subsystem
Projects
None yet
Development

No branches or pull requests