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
Comments
I can also confirm that the issue is that Microsoft login prompt doesn show up. |
Hello @warriormaster12, please add |
Dug into the latest Flighting build. Notes:
The game boots but fails to prep Xbox Live, so not much has changed. |
Also tried, goes to the menu screen but get error when trying to proceed further. |
+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? |
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? |
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. |
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. |
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 |
As an experiment, I took the Windows 64-bit sample app from cefbuilds and ran it on the following:
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 |
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. |
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. |
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. |
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. |
Log from the Flight 3 build: 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. |
Steam release, running the EAC-disabled version I get stuck at the xbox live login screen. Log below. |
Tried the release version with 4.11 with an updated bcrypt+winhttp, didn't get past login. Noticing that it hits a stub for |
Stuck on connecting to xbox live. KDE neon User Edition 5.17 |
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 |
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 |
i have the same issue as everybody else it seems. gets to title screen, but cannot proceed because of an Xbox Live error. i believe this is the error causing the xbox live issue. |
The game is launching but couldn't signing into Xbox Live |
i have the same error can't sign in Manjaro |
Does the following line indicate an issue: |
looks like an issue with wine's bcrypt and winhttp implementations. |
@mathew2214 It doesn't work on a recent wine staging with windows steam either, I'm taking a look at fixing this. |
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. |
The log indicates mesa 22.1.7 is in use, making that detail irrelevant to the previous comment. |
okay, so if i launch a game with |
My game is working even with the anti cheat option now after latest experimental update |
noticed in the log file, a line that goes |
@coreybruce Are you able to play the online multiplayer matchmaking? |
Sadly no but at least we can run the game with the anti cheat option and doesn't stop the game for launching like it use to when that game update broke it. |
Proton experimental works again, no more launching to a fatal error. Not sure what changed in a week in experimental |
A little birdie told me that EAC successfully loads but the game crashes for other reasons. Is this true? Is it a Proton bug? |
It launches with the EAC option but EAC still doesn't work on the online servers also the game should be running fine without issues.
|
Finally some confirmation |
Might be worth uninstalling through steam, totally wiping the game folder
to clear any remnants and then reinstalling, unless you've already tried
that?
…On Sun, 17 Apr 2022, 15:53 Sethox, ***@***.***> wrote:
I seem to be able to launch it with EAC disabled, and not deleting
anything. May have been an update today or something, as this is the first
time I've installed MCC on this laptop.
I did a full prefix wipe and game reinstall couple days ago. Running with
the EAC disabled option works as before. Tried a few missions of Reach and
Halo 2, which played through flawlessly. Maybe there are some remnants in
older prefixes that prevent the game from working altogether after the last
major update?
I just tried this with a new prefix. Still doesn't work for me.
*MCC-Win64-Shipping.exe* doesn't start unless I make the
*easyanticheat_x64.so* file absent (rename or delete). So you guys are
either lucky or you do something different than me?
—
Reply to this email directly, view it on GitHub
<#2907 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFROOTKS4GWYGMNWIGRLOHDVFQQWBANCNFSM4IGTWRCA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Completely unable to join other linux users in any gamemode. Anyone have any idea what is causing this? it has been an issue for the last year or so |
EDIT: Resolved my issue. YouTuber recommended Verify Integrity to rerun the Install Scripts. It downloaded 183 files during the process. Restarting showed it worked immediately. ~~Crashes at launch: Full PROTON_LOG file attached. Snippet where crashes (plus header):~~ ~~
|
EAC support has unfortunately still not been completely enabled in the new update. Still getting the EAC Hash Catalogue error popup on startup which prevents joining multiplayer games. |
On top of the EAC issue, the game doesn't seem to be working for me now, though it's like a game of whack-a-mole. I'll try out in a Fedora environment (am in Arch currently) to see if I can get any other results. Maybe it's just the game loading everything into RAM taking a while. |
Have you verified your game? Mines running great on Manjaro which is a Arch based system |
@coreybruce Multiple times, but I'll try it again and see if it's potentially a Proton thing. Will report back in ~10 hours (a lil mimir) |
You might want to try deleting your prefix as well, especially if it has been carried over between multiple proton versions. I've seen a few scattered reports of it not working for some people, and trying various things to sort it out, like this person for whom mods didn't work. |
Alright |
Okay, even tho my game is working I might do that |
After the most recent large update, the game no longer launches for me under any circumstance on Debian Unstable. Deleting the EAC library and the like doesn't even fix it. The game immediately dies on launch with no hints on why. |
Damn it, I shouldn't of deleted the comdat folder for Halo, now my games is stuck on the splash screen even if you pick the no EAC mod mode EDIT: |
Gonna note that, on the latest update, renaming the easyanticheat folder (like before) is the simplest fix to get into the game. Deleting the compatdata folder did work before, though. |
Halo Master Chief collections locks up at the splash screen after clicking play unless you use -Running with |
The game has been crashing for me randomly for a while now, I find it tends to be after a while of playing a game. A small window will show up with a UE-related error. Has anybody gotten this? I'm going to be toying around with it for a while to try to get some logs. |
Might be a WINE/mesa bug rather than halo. |
Note for those people with crash issues together with a potential system lockup. The latest game update have introduced a memory leak (At least for HALO: CE) unrelated to proton. Another issue i found while testing the above is that there might be a issue when you enable precache while using dxvk where it will get stuck on pop up splah screen. Disabling Shader Pre-Caching solved it for me. |
Halo MCE Memory Hole Issue transferred from #6445. I was playing "The Truth and Reconciliation" campaign for the "Sniper School" playlist. (This is the part early in the game where you rescue Captain Keyes.) I noticed frequent stuttering and hanging, and so I opened up the System Monitor... the game was taking several gigabytes of RAM. I kept playing through, and it kept taking more and more RAM, and would freeze up every so often... I was not able to make it through, because I hit Escape during one of these slow-downs to try and fiddle with the settings and although my cursor moved around the menu it wouldn't let me resume the game. I tried Proton-GE as well and had very similar results though I was able to finish that campaign (possibly because I learned my lesson and did not try to fiddle with settings). By the end of the campaign, it had taken over 30 GB of RAM. I doubt this is how it should be - I have 64 GB of RAM but most people don't. I had the settings on the highest level, but still, that's a lot of RAM. APU: AMD Ryzen 7 5700G with Radeon graphics |
I can confirm memory leak in Halo CE, maybe other Halo act the same. Also fix for achievements from #2907 (comment) does not work anymore. So overall - Achievements not working, Multiplayer not working, EAC not working. 3 years since release already... |
Compatibility Report
System Information
I confirm:
Symptoms
Game will not launch
Reproduction
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/
The text was updated successfully, but these errors were encountered: