Maintenance for the week of December 16:
• PC/Mac: No maintenance – December 16
• NA megaservers for patch maintenance – December 17, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• EU megaservers for patch maintenance – December 17, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
• PC/Mac: No maintenance – December 16
• NA megaservers for patch maintenance – December 17, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• EU megaservers for patch maintenance – December 17, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
The issues on the North American megaservers have been resolved at this time. If you continue to experience difficulties at login, please restart your client. Thank you for your patience!
RequestedNum_____Threads Values?
Consumed
Soul Shriven
Hello! I've been running ESO in Wine on Linux since the beta. It has a problem with random crashes in the current dev version. However, this can be solved by adding the following into UserSettings.txt:
SET RequestedNumJobThreads 0
SET RequestedNumWorkerThreads 0
These were changed from the default -1 values. This works like a charm, and I haven't had an out-of-the-blue crash since. While it currently works, I do have an issue that makes the game stutter while it is loading new stuff (terrain? characters?). So, I'm of a mind to tweak my UserSettings.txt so that I get minimal or no crashes and as little stutter as possible. Therefore, I'd like to know a little more about these two settings.
The default value is -1. I assume this means "as many as needed." Is that correct? Additionally, my observation of stutter when the value is 0 leads me to believe that no threads are spawned for the loading of new "stuff", which leads the main thread to hang for short, repeated amounts of time. Is this also correct?
Also, is this the only two possible values that can be used for this setting? I've looked all kinds of places and the only values I've seen are 0 and -1, but if it were changed to something like 4, would that spawn up to 4 threads for loading?
Also, a little clarification as to what these settings actually do would also be nice. I noticed the setting RequestNumThreads was split into these two settings. What's the difference between "Job" and "Worker" threads? Do "worker" threads get spawned from "job" threads, or what?
Any help understanding these settings would be helpful and may also help future users. Thanks in advance!
Edited by Consumed on September 12, 2014 8:13PM SET RequestedNumJobThreads 0
SET RequestedNumWorkerThreads 0
These were changed from the default -1 values. This works like a charm, and I haven't had an out-of-the-blue crash since. While it currently works, I do have an issue that makes the game stutter while it is loading new stuff (terrain? characters?). So, I'm of a mind to tweak my UserSettings.txt so that I get minimal or no crashes and as little stutter as possible. Therefore, I'd like to know a little more about these two settings.
The default value is -1. I assume this means "as many as needed." Is that correct? Additionally, my observation of stutter when the value is 0 leads me to believe that no threads are spawned for the loading of new "stuff", which leads the main thread to hang for short, repeated amounts of time. Is this also correct?
Also, is this the only two possible values that can be used for this setting? I've looked all kinds of places and the only values I've seen are 0 and -1, but if it were changed to something like 4, would that spawn up to 4 threads for loading?
Also, a little clarification as to what these settings actually do would also be nice. I noticed the setting RequestNumThreads was split into these two settings. What's the difference between "Job" and "Worker" threads? Do "worker" threads get spawned from "job" threads, or what?
Any help understanding these settings would be helpful and may also help future users. Thanks in advance!
0
-
lasse.ylineneb17_ESOSoul ShrivenHi,
I have had same kind of issue with the game freezing when it loads new texture, then could continue normally. My RequestedNum setting is at 0 as well, but wasn't at the beginning (so for me the bug happened even while it was at -1, I have also tried small positive values without receiving improvement).
What helped was to tune this setting down:
SET GPUSmoothingFrames "4"
This mostly eliminated the freezing problem. Note that if you drop it too low you may encounter kicks to lobby or other weird stuff.
You may also want to tune MIP_LOAD_SKIP_LEVELS setting. I have also tuned the network buffers higher. So they may also help you on the issue.0