El Capitan - Host_Auth_Fail

Dinamic

I've scrolled through numerous threads but am unable to find a concrete answer. Is there anyway around this error that I'm receiving?

I'm on Beta 5 of El Capitan for Mac OS X.

Dinamic

Keep in mind.. In reading other posts, I see that users can actually play the game.. I can't even download the game. This comes up when running the Install File.

KhajitFurTrader

@Dinamic,

please refer to this post for an attempted workaround. An official response can be found in this thread.

You can download/update and then copy your up-to date ESO installation over from your regular machine, i.e. the one with the non-beta OS version. Then use the eso.app application in

/Applications/ZeniMax Online/The Elder Scrolls Online/game_mac/pubplayerclient

to start the game.

jackmaninov

I can confirm this launcher issue has been resolved in El Capitan developer preview 7, and most likely in public beta 5. However, I get a crash immediately on launching the game.

forestpest

has anyone tried it in developer beta 8?

chris.dillman

Possible 10.11 fix to make ESO run.

1. Run the launcher and patch like normal.
2. Close the launcher.
3. Run the eso client from the Terminal.app with...

CI_ENABLE_CL_CPU=0 /PathToEsoClientBinary

Example on the terminal you would enter the line below and hit return.

CI_ENABLE_CL_CPU=0 /Applications/ESO/Launcher.app/game_mac/pubplayerclient/eso.app/Contents/MacOS/eso

forestpest

chris.dillman wrote: »

Possible 10.11 fix to make ESO run.

1. Run the launcher and patch like normal.
2. Close the launcher.
3. Run the eso client from the Terminal.app with...

CI_ENABLE_CL_CPU=0 /PathToEsoClientBinary

Example on the terminal you would enter the line below and hit return.

CI_ENABLE_CL_CPU=0 /Applications/ESO/Launcher.app/game_mac/pubplayerclient/eso.app/Contents/MacOS/eso

I can confirm this works running el capitan developer beta 8

attached my system info minus serial # and an in-game screenshot. This works.

KhajitFurTrader

chris.dillman wrote: »

CI_ENABLE_CL_CPU=0 /Applications/ESO/Launcher.app/game_mac/pubplayerclient/eso.app/Contents/MacOS/eso

I think the path to the client binary has changed some time ago, it doesn't reside in the Launcher anymore.

I found mine in

/Applications/ZeniMax\ Online/The\ Elder\ Scrolls\ Online\ EU/game_mac/pubplayerclient/eso.app/Contents/MacOS/eso

Scratch the "\ EU" part for the US version.

forestpest

Launcher works with the same trick if you need to update the client

forestpest

Going to try gm seed in a few hours

forestpest

Finally found time to test El Capitan GM. Still needs that parameters but works fine

agegarton

KhajitFurTrader wrote: »

chris.dillman wrote: »

CI_ENABLE_CL_CPU=0 /Applications/ESO/Launcher.app/game_mac/pubplayerclient/eso.app/Contents/MacOS/eso

I think the path to the client binary has changed some time ago, it doesn't reside in the Launcher anymore.

I found mine in

/Applications/ZeniMax\ Online/The\ Elder\ Scrolls\ Online\ EU/game_mac/pubplayerclient/eso.app/Contents/MacOS/eso

Scratch the "\ EU" part for the US version.

Thanks - that works great.

agegarton

@ZOS might be worth noting this from El Capitan (Mac OS X 10.11 GM build) :-


ep 18 08:41:15 AwesomiumProcess[1406] <Error>: The function ‘CGFontSetShouldUseMulticache’ is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance.


This is the feedback message from Terminal having run ESO using the method described above. Hope this helps.

forestpest

agegarton wrote: »

@ZOS might be worth noting this from El Capitan (Mac OS X 10.11 GM build) :-


ep 18 08:41:15 AwesomiumProcess[1406] <Error>: The function ‘CGFontSetShouldUseMulticache’ is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance.


This is the feedback message from Terminal having run ESO using the method described above. Hope this helps.

This message has been appearing since developer beta 7 just as a side note

KhajitFurTrader

forestpest wrote: »

This message has been appearing since developer beta 7 just as a side note

Actually, it's much older than that. It's been logged since Mavericks, and as long as this particular API call isn't being actually deprecated, it'll have little to no impact to the Launcher's functioning.

Pomaikai

Unless of course it's the cause of the memory leak. <---(Disclaimer: Complete guess made by someone without a clue.)

KhajitFurTrader

Pomaikai wrote: »

Unless of course it's the cause of the memory leak. <---(Disclaimer: Complete guess made by someone without a clue.)

Well, as the logged error comes from the Launcher app, not from the client binary, this possibility is ruled out.

Pomaikai

There are two types of crashes that I'm experiencing. One is trapped by Zeni's crash reporting tool, and the other slams me straight back to desktop with Apple's crash reporting tool. Are they the same crash caused by the same issue, or are there two separate problems at work here?

KhajitFurTrader

Pomaikai wrote: »

There are two types of crashes that I'm experiencing. One is trapped by Zeni's crash reporting tool, and the other slams me straight back to desktop with Apple's crash reporting tool. Are they the same crash caused by the same issue, or are there two separate problems at work here?

A "crash" is nothing else but a handled software exception. Whether this exception is caught by the application's internal exception handler (ZOS CrashReporter), or by the OS, almost doesn't matter, because the original cause for the exception's occurrence is the same in both cases. The difference is that ZOS's CrashReporter sends information to ZOS directly; exceptions caught by OS X get sent to Apple (which might or might not be forwarded to developers).

As for why sometimes one or the other shows up: if the client's binary doesn't have enough resources left for the internal handler to run, the process gets forcefully terminated, and the exception is then handled by the OS.

Pomaikai

Thanks for the excellent explanation!

j.frank.nicholsb14_ESO

This appears to be resolved now. Running 10.11.1 and latest ESO update today. Launcher works and App;location launches with no problems.

Frank