Maintenance for the week of February 9:
• NA megaservers for maintenance – February 9, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• EU megaservers for maintenance – February 9, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
• NA megaservers for maintenance – February 9, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• EU megaservers for maintenance – February 9, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
El Capitan - Host_Auth_Fail
Dinamic
Soul Shriven
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.
I'm on Beta 5 of El Capitan for Mac OS X.
0
-
DinamicSoul ShrivenKeep 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.0
-
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.0 -
jackmaninovSoul ShrivenI 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.Edited by jackmaninov on August 22, 2015 9:07AM0
-
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
-- ESO -- Lead Mac Programmer...0 -
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.
0 -
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.1 -
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.0 -
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.0 -
@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
0 -
KhajitFurTrader✭✭✭✭✭
✭✭
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.forestpest wrote: »
This message has been appearing since developer beta 7 just as a side note
1 -
Pomaikai✭✭✭✭✭
✭Unless of course it's the cause of the memory leak. <---(Disclaimer: Complete guess made by someone without a clue.)0 -
KhajitFurTrader✭✭✭✭✭
✭✭
Well, as the logged error comes from the Launcher app, not from the client binary, this possibility is ruled out.Unless of course it's the cause of the memory leak. <---(Disclaimer: Complete guess made by someone without a clue.)
0 -
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?
0 -
KhajitFurTrader✭✭✭✭✭
✭✭
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).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?
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.0 -
This appears to be resolved now. Running 10.11.1 and latest ESO update today. Launcher works and App;location launches with no problems.
Frank0