Instant crash on my Mac [Workaround]

Pity if you do not have Xcode and are stuck on Sierra for other reasons.

You should be able to install Xcode on Sierra. Am still running EL Capitan (10.11). I use Xcode for years (since release) and never had any problem to install it on any OS (didn't test on Sierra or High Sierra tho)

There is more intrusive way to limit core usage but i dont recommend if you dont have a deep knowledge of what you are doing (will not be reverted when restarting, have to do by your own).

The workaround detailed by @sphane solved it for me, and I don't have any performance or graphics degradation either.

Genius!

I read the patch notes for the update today. I'm no programmer at all, but in the performance section it did make mention that they made changes so that that game would finally make use of multiple core cpu's. I can't help but think either that, or the multithreading has something to do with this. Again, I'm no programmer, this is just a guess. Taking that into consideration, and a couple of other points they made on that topic. Decreasing the amount of cpu cores right now, temporarily, won't make any difference on the performance. tbh, my game seems to play smoother, and looks a bit better even.

You are right, it's the origin of the problem. I guess all of us have 2 CPU multi-core and obviously, ESO is confusing with more than 1 CPU on mac. Usually i downgrade my computer to run old program... but it's the first time i have to do to run a brand new one...

Having confirmation that ZOS is aware and working on a permanent fix would be great because multi cpu machines are becoming very commons...

I am running a late 2013 Mac Pro with 12 (2x6) cores. I can confirm that the Xcode-related recommendations from @sphane work on my machine also. To make this work for me, I cannot set my cores to 8. If you have 12 cores like I do, you must set it to 6, which effectively gets you to use only 1 CPU, which is the problem that has been identified. ZOS apparently has only coded for 1 CPU with multi cores (see above comments).

I am however, seeing minor performance degradation. I am running two high def monitors on my machine so perhaps that is too much on my rig for only 1 CPU. With both monitors active, my game FPS goes down a little bit and I get occasional cutouts on frames.

If you are new to the thread, I recommend you read all of @sphane's responses before you attempt to get into Xcode. I too couldn't locate the proper window to change my cores until I read a latter post by the @sphane. (thx sphane!).

I am running a late 2013 Mac Pro with 12 (2x6) cores. I can confirm that the Xcode-related recommendations from @sphane work on my machine also. To make this work for me, I cannot set my cores to 8. If you have 12 cores like I do, you must set it to 6, which effectively gets you to use only 1 CPU, which is the problem that has been identified. ZOS apparently has only coded for 1 CPU with multi cores (see above comments).

I am however, seeing minor performance degradation. I am running two high def monitors on my machine so perhaps that is too much on my rig for only 1 CPU. With both monitors active, my game FPS goes down a little bit and I get occasional cutouts on frames.

If you are new to the thread, I recommend you read all of @sphane's responses before you attempt to get into Xcode. I too couldn't locate the proper window to change my cores until I read a latter post by the @sphane. (thx sphane!).

I edited the initial post and the title with the final workaround suggested by @smacx250

I just tested gameplay using the solution from @smacx250. It works well also. In fact the performance degradation I saw with Xcode seems to be gone based on 5min of gameplay. I can play the game on one HIDef monitor and watch Rogue One streaming on Netflix on the other and both have decent FPS. Again, on my 2x6 core rig, I set my Maxcores.4 value to "6" to get it to work.

Thanks folks (@sphane and @smacx250) for your great solutions. Cant wait to see that fix. Cheers!

I just tested gameplay using the solution from @smacx250. It works well also. In fact the performance degradation I saw with Xcode seems to be gone based on 5min of gameplay. I can play the game on one HIDef monitor and watch Rogue One streaming on Netflix on the other and both have decent FPS. Again, on my 2x6 core rig, I set my Maxcores.4 value to "6" to get it to work.

Thanks folks (@sphane and @smacx250) for your great solutions. Cant wait to see that fix. Cheers!

However, I ticketed support and after a little back and forth, thy suggested changing the UserSettings.txt lines

from

SET RequestedNumJobThreads "0"
SET RequestedNumWorkerThreads "0"

to

SET RequestedNumJobThreads "1"
SET RequestedNumWorkerThreads "1".

They also supplied a "default" set of values for UserSettings.txt

The default values worked.

However, I went back to my original UserSettings.txt. It had

SET RequestedNumJobThreads "-1"
SET RequestedNumWorkerThreads "-1"

I changed these to 1 and restarted with perfect results. I then changed them to 0. Again, perfect.

MacPro 2013 OS 10.12.6

Hope this helps someone.

wow really?
Edit: my values were both at -1 when I opened up the Usertext.txt. I did change them both to 1, seems to be working. Will update soon after I'm in game for a few.
Update: I switched toons. and logged out and back in. Seems to be working fine. I'm not sure if I've seen any difference in performance or not.

After playing all evening, and one pledge. All I can say is both work arounds seem to have the same performance in general. I got some massive fps drops last night out of nowhere (using the 'cores used' work around, not the 'requestnumjobthread' one). Just an fyi.

I used the fix suggested by Tech support above (setting numeric values to "1"), and it did allow me to play the game for a while, albeit with pretty bad fps. However, I just experienced another crash with the same report as before. ZOS, please do let us know if a fix is incoming, as the suggested workaround is clearly not an ideal solution.

I'm using a combination of the user settings, and everything has been running fine. I got about 10% better fps using the xcode fix, but changing the settings file requires a lot less fiddling and is ESO specific.

Here's what I currently have it set to:

SET MaxCoresToUse.4 "8"
SET RequestedNumJobThreads "0"
SET RequestedNumWorkerThreads "0"

Thanks to everyone for discovering the cause and working through fixes!

here the same. I have a iMac Pro (Radeon Pro Vega 64) and the german support say to me "your videocard ist to slow! buy a better Videocard" !

I been change with xcode to only 8 Core and it's work.

I hope Bethesda fixing this Problem that we again use all cores can. Because with 8 cores now runs fan more often then before.

sry 4 my english!

The 'German' devs don't know wtf they are talking about. The pro Vega 64 is MORE than enough to handle this game. I'm on the baseline iMac Pro, mine has the 56 card and I get great fps. Well not right now, but typically.

Just hit the same damn problem after the last update. I know about the fix, I cannot find the Usertext.txt file. I don't understand what happened. I keep going into the docs folder, I can see the Live folder. The folders that are in it though, Are all empty. I'm sick of this. what the *** do I do?

Just hit the same damn problem after the last update. I know about the fix, I cannot find the Usertext.txt file. I don't understand what happened. I keep going into the docs folder, I can see the Live folder. The folders that are in it though, Are all empty. I'm sick of this. what the *** do I do?

Usual path is ~/Documents/Elder Scrolls Online/live/UserSettings.txt where ~/ stands for /Users/username/ where username is your login.

If you can't find the file here, are you making back-up with Time Machine ? If so, try to restore it.

If directory hierarchy ~/Documents/Elder Scrolls Online/live is empty, delete it. If launching the game can't create again the hierarchy and the user setting file before crashing, maybe you should try to use the first workaround with Xcode Instruments once to regenerate the user setting file.