You can change it yourself by setting RequestedNumWorkerThreads = 1 in your UserSettings.txt file. That will prevent any multicore hand-offs and stop the 1s hitching.
No sense in having them go backwards, better to keep going forwards and they can refine and fix the hitching.
How do y'all know it's the performance enhancements that are causing the freezes? Those aren't the only changes introduced by Summerset, and it's hard to have an opinion about interim measures without knowing the precise cause of the problem.
How do y'all know it's the performance enhancements that are causing the freezes? Those aren't the only changes introduced by Summerset, and it's hard to have an opinion about interim measures without knowing the precise cause of the problem.
How do y'all know it's the performance enhancements that are causing the freezes? Those aren't the only changes introduced by Summerset, and it's hard to have an opinion about interim measures without knowing the precise cause of the problem.
I did not, until danno8 suggested changing the UserSettings.txt. I presume he has tested his solution. In that case it seems clear it is the multi-core enhancements causing this.
I will do some experiments. I run a really old, but top-shelf at the time, CPU (and it's overclocked). This CPU is really two dual-cores in a single package, with 2 separate level 3 caches. I will play around with processor affinity in Task Manager and see what that yields.
ZOS_AlexTardif wrote: »ramasurinenpreub18_ESO wrote: »The massive freezes feel like a thread collision related to player character model loading, where the main game thread passed off the loading to other cores, but they weren't ready with results when asked for them. The freezes happen most often and severely when approaching wayshrines, especially in Artaeum and Alinor, where a lot of people tend to go AFK.
I've been messing with the UserSettings.ini settings for multicore, restricting the number of threads a bit. The freezes are definitely coming from the "WorkerThreads" line, as setting it to 0 removes them entirely, but at the loss of a little fps in general, while setting them to 8 turns the entire game into a near constant slideshow. With the settings below I have managed to completely remove all the freezes and stutters, in Alinor and everywhere else. Framerate now seems to be about the same as pre-patch. Smooth as silk. Maybe give these a try until they get a proper fix in.
SET MaxCoresToUse.4 "8" (if you have a quad core hyperthreading cpu, if not use "4")
SET RequestedNumJobThreads "4"
SET RequestedNumWorkerThreads "1"
Also, setting GPUSmoothingFrames to "0" or "1" can be very helpful with general smoothness and microstutters, as well as input lag and responsiveness if you have a high end GPU. "0" is best if you can get away with it.
Cheers.
You're correct! The momentary freeze is indeed because of some processing that runs on a worker thread, so you may well see that issue occur less frequently (or not at all) by doing what you've stated, however the impact of reducing your worker thread count to 1 means that only a single thread is able to perform all of the background work that the game demands. This means you would have longer load times, slower in-game streaming, and potentially lower frame rate than you would have otherwise. This is because much of the work done for this patch was to offload main thread work to worker threads so that it wouldn't slow down your framerate. The new stutters are situations when the main thread finds itself waiting on something a worker thread is doing, which is not good, and didn't show up in our internal testing environment. We have a number of fixes for these situations on the way, so we recommend changing those settings back after we patch these fixes in to see if it improves your experience.
Since the last patch this problem is gone - at least I did not experience it anymore and these very frequent disconnects are gone as well - really nice to be able to concentrate on the game and not the issues it had.
You can change it yourself by setting RequestedNumWorkerThreads = 1 in your UserSettings.txt file. That will prevent any multicore hand-offs and stop the 1s hitching.
No sense in having them go backwards, better to keep going forwards and they can refine and fix the hitching.
Since the last patch this problem is gone - at least I did not experience it anymore and these very frequent disconnects are gone as well - really nice to be able to concentrate on the game and not the issues it had.
The funny thing with it is - ZOS stated that a fix for it wasn't part of this patch - so what has fixed it for me then?
You can change it yourself by setting RequestedNumWorkerThreads = 1 in your UserSettings.txt file. That will prevent any multicore hand-offs and stop the 1s hitching.
No sense in having them go backwards, better to keep going forwards and they can refine and fix the hitching.
Hey i checked my settings. And by default it’s set at -1.. shoud i set it to 1? What if i set it to 4? Also what about the requestnumjobthreads. Should i put the same number on that as well?
Thanks
Forget this. Stutters are back today. Seems to depend on the number of characters on the screen. Now trying changes to UserSettings.txt.I am experimentally limiting eso64.exe to Cores 1, 2 and 3 using the Set Affinity... option in Task Manager whenever I play now. I don't know if it is this or ZOS' hot fix already included some improvements, but stutters are quite rare and less severe now.