Jump to content

Recommended Posts

Posted

Had the issue with starting the homecoming launcher after performing Big Sur updates on my Mac mini M1, used your instructions for replacing the launcher.exe, was able to launch and move the launcher window, and start up COH and log in with my character, so it appears to work now.

 

Posted
5 hours ago, Number Six said:

and don't make any sense

 

Programming errors 101 :p

OG Server: Pinnacle  <||>  Current Primary Server: Torchbearer  ||  Also found on the others if desired  <||> Generally Inactive


Installing CoX:  Windows  ||  MacOS  ||  MacOS for M1  <||>  Migrating Data from an Older Installation


Clubs: Mid's Hero Designer  ||  PC Builders  ||  HC Wiki  ||  Jerk Hackers


Old Forums  <||>  Titan Network  <||>  Heroica! (by @Shenanigunner)

 

Posted (edited)

Stuck again. This time after the first force quit, it presents a wine message about updating the private folder. I force quit everything again and am going to try that fix again.

 

Weird, redid the fix and it works again. My characters are out of order, but I may not have the sorted file on this machine, so I'm not actually calling that a side effect.

Edited by WanderingAries

OG Server: Pinnacle  <||>  Current Primary Server: Torchbearer  ||  Also found on the others if desired  <||> Generally Inactive


Installing CoX:  Windows  ||  MacOS  ||  MacOS for M1  <||>  Migrating Data from an Older Installation


Clubs: Mid's Hero Designer  ||  PC Builders  ||  HC Wiki  ||  Jerk Hackers


Old Forums  <||>  Titan Network  <||>  Heroica! (by @Shenanigunner)

 

  • City Council
Posted

Apparently it wasn't the recent round of changes the caused this, but rather an overhaul of the packaging system done back in May that didn't go live until about 3 weeks ago. No issues on Windows or MacOS Intel, but something about the M1 emulation is causing it to deadlock.

 

Until I can pin down the exact cause, I've created a third launcher code branch. In addition to the release and test branches, there's now a macos branch that is pinned to an older version of the code before that change.

 

The file used by the Mac installer has been updated to point at this special branch, so if you're on an M1 mac and find that the launcher just hangs, you can either reinstall or use the procedure quoted below to replace the launcher exe with a version that works on that platform.

 

On 9/30/2021 at 11:43 PM, Number Six said:

@golias The log file shows you have build 4518, which is the one that is apparently causing wine to crash on MacOS.

 

If you don't want to reinstall in place, you can find your [CoH]/bin/win64/launcher.exe file and delete it, then replace it with this one: https://manifest.cohhc.gg/launcher/hcinstall-catalina.exe

(ignore the filename and rename it to launcher.exe).

 

Also delete [CoH]/settings/launcher/packages/launcher.json

 

That should force it to download 4520 and you can see if that works.

 

If it doesn't, what we may have to do for now is manually roll back to a previous launcher version and set it to not auto-update. That's a bit more involved process but if I can't figure out why it's suddenly misbehaving in wine we may have to go down that road.

Posted
5 hours ago, Number Six said:

Apparently it wasn't the recent round of changes the caused this, but rather an overhaul of the packaging system done back in May that didn't go live until about 3 weeks ago. No issues on Windows or MacOS Intel, but something about the M1 emulation is causing it to deadlock.

 

Until I can pin down the exact cause, I've created a third launcher code branch. In addition to the release and test branches, there's now a macos branch that is pinned to an older version of the code before that change.

 

The file used by the Mac installer has been updated to point at this special branch, so if you're on an M1 mac and find that the launcher just hangs, you can either reinstall or use the procedure quoted below to replace the launcher exe with a version that works on that platform.

 

 

I came back to say that the M1 'fix' is extremely temporary as it hangs yet again in today's test and I've done the above 3(?) times now. 

OG Server: Pinnacle  <||>  Current Primary Server: Torchbearer  ||  Also found on the others if desired  <||> Generally Inactive


Installing CoX:  Windows  ||  MacOS  ||  MacOS for M1  <||>  Migrating Data from an Older Installation


Clubs: Mid's Hero Designer  ||  PC Builders  ||  HC Wiki  ||  Jerk Hackers


Old Forums  <||>  Titan Network  <||>  Heroica! (by @Shenanigunner)

 

Posted

Unfortunately, mine is not working yet again today.  Tried replacing the launcher exe again, and here's what I get in the log:

2021-10-08 15:08:09    launcher: Starting (build wine-x64-final-4520)
2021-10-08 15:08:09    launcher: WINE detected
2021-10-08 15:08:09    launcher: Using basedir z:/Applications/coh/Launcher
2021-10-08 15:08:09    launcher: Previous startup was incomplete. Entering self-repair mode.
2021-10-08 15:08:09    bootstrap: Cached config loaded
2021-10-08 15:08:09    pstate: package hc_bin_live_win32:1.20210821.171731.4471 transitioned from unknown to installed
2021-10-08 15:08:09    pstate: package hc_bin_live_win64:1.20210821.172057.4471 transitioned from unknown to installed
2021-10-08 15:08:09    pstate: package hc_crashhandler_win32:1.20210418.152332.4240 transitioned from unknown to installed
2021-10-08 15:08:09    pstate: package hc_crashhandler_win64:1.20210418.152359.4240 transitioned from unknown to installed
2021-10-08 15:08:09    pstate: package hc_data_live:1.20210821.170656.4470 transitioned from unknown to installed
2021-10-08 15:08:09    bootstrap: Attempting to recover from failure
2021-10-08 15:08:09    bootstrap: Fetching config
2021-10-08 15:08:09    pstate: package i24_piggs:1.0.2400 transitioned from unknown to installed
2021-10-08 15:08:09    jsonobjdl: Trying url https://manifest.cohhc.gg/launcher/v1/bootstrap.json
2021-10-08 15:08:09    pstate: package hc_live:1.20210824.130347,1 transitioned from unknown to installed
2021-10-08 15:08:09    jsonobjdl: Successfully retrieved bootstrap-config bootstrap:0.7.16
2021-10-08 15:08:09    pmgr: Unregistered package launcher:1.4562
2021-10-08 15:08:09    bootstrap: Cached package not found
2021-10-08 15:08:09    bootstrap: Fetching bootstrap package
2021-10-08 15:08:09    jsonobjdl: Trying url https://manifest.cohhc.gg/launcher/v1/package/launcher.json
2021-10-08 15:08:09    jsonobjdl: Successfully retrieved package launcher:1.4562
2021-10-08 15:08:09    bootstrap: Downloaded package
2021-10-08 15:08:09    pmgr: Registered package launcher:1.4562
2021-10-08 15:08:09    pkgverify: Starting full verify of package launcher:1.4562
2021-10-08 15:08:09    pkgverify: Corrupt file: bin/win64/launcher.exe
2021-10-08 15:08:09    pkgverify: Corrupt file: bin/win64/crtcheck.exe
2021-10-08 15:08:09    pkgverify: Corrupt file: assets/launcher/launcher.pigg
2021-10-08 15:08:09    pkgverify: Corrupt file: bin/win32/launcher.exe
2021-10-08 15:08:09    pkgverify: Corrupt file: bin/win64/crthelper.dll
2021-10-08 15:08:09    pkgverify: Corrupt file: bin/win64/launchercli.exe
2021-10-08 15:08:09    pkgverify: Corrupt file: bin/win32/launchercli.exe
2021-10-08 15:08:09    pkgverify: Verify of package launcher:1.4562 failed
2021-10-08 15:08:09    pstate: package launcher:1.4562 transitioned from unknown to incomplete
2021-10-08 15:08:09    bootstrap: Package is not valid
2021-10-08 15:08:09    bootstrap: Installing package
2021-10-08 15:08:09    pkginstall: Beginning install of launcher:1.4562
 

  • City Council
Posted
10 hours ago, pjmoyer said:

Had to download the launcher again; trying to update for the halloween event and it's stuck at 0%. 😕

 

Before or after you redownloaded the launcher? If after can you pull your log file and verify it says build 4550? That's the macos-specific version that as far as I know should be working. @golias You'll also have to redownload it or use the steps I posted above to overwrite the exe; 4520 won't be able to update itself on M1 because of whatever unknown issue the Apple translation layer has.

  • Thanks 1
Posted
9 hours ago, Number Six said:

 

Before or after you redownloaded the launcher? If after can you pull your log file and verify it says build 4550? That's the macos-specific version that as far as I know should be working. @golias You'll also have to redownload it or use the steps I posted above to overwrite the exe; 4520 won't be able to update itself on M1 because of whatever unknown issue the Apple translation layer has.

That did the trick this time!  Many thanks once again!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...