Geroken777 wrote: »That's disappointing.
Looks like im going to go with the i7 7700K.

It uses all 4 of my physical cores on my i7. It does not use the other 4 virtual cores.
Also, the notion that ESO is "single threaded" is bollocks, i'm looking at 24 threads for eso64.exe right now and a quick look at "UserSettings.txt" will show you that there are several settings for threading in there that you can tweak.

JasonSilverSpring wrote: »I think one point some might be missing is that the one thread for ESO that is limiting will not only use the same core. It might hit the various cores at different times, but that limited thread will still CPU limit you. Hence the more powerful the single core performance the better it will run.
The near identical usage is because that limiting thread is utilizing a different core at different times.
rfennell_ESO wrote: »JasonSilverSpring wrote: »I think one point some might be missing is that the one thread for ESO that is limiting will not only use the same core. It might hit the various cores at different times, but that limited thread will still CPU limit you. Hence the more powerful the single core performance the better it will run.
The near identical usage is because that limiting thread is utilizing a different core at different times.
I think the thing that people aren't getting is that a lot of it is DirectX. DirectX 12 as per @Shadow-Fighter 's post should improve things for multicore operation quite a bit.
It's not really an ESO thing, DirectX12 will take some time to be implemented. Only a handful of newer games are supporting it right now, even though win10 supports it natively...
Of course, it's really up to ZOS with how far they go in implementing Directx12 (if and when they do).
JasonSilverSpring wrote: »rfennell_ESO wrote: »JasonSilverSpring wrote: »I think one point some might be missing is that the one thread for ESO that is limiting will not only use the same core. It might hit the various cores at different times, but that limited thread will still CPU limit you. Hence the more powerful the single core performance the better it will run.
The near identical usage is because that limiting thread is utilizing a different core at different times.
I think the thing that people aren't getting is that a lot of it is DirectX. DirectX 12 as per @Shadow-Fighter 's post should improve things for multicore operation quite a bit.
It's not really an ESO thing, DirectX12 will take some time to be implemented. Only a handful of newer games are supporting it right now, even though win10 supports it natively...
Of course, it's really up to ZOS with how far they go in implementing Directx12 (if and when they do).
That does make sense to me as the areas where it is CPU limited like in cities involves a large number of draw calls with everyone's outfits/skins/flashy mounts/pets. I use an add-on called Adaptive Settings which will dynamically reduce draw distance to help maintain a certain fps. Reducing draw distance will reduce this draw calls.
Unfortunately I doubt DX 12 will come for a while as they would need to update game engine to truly take advantage of it.
Dropping the 32 bit client early next year has already angered some and there were complaints when they dropped DX 9. They also have Mac's to support. Do Mac's support Vulkan?
Or you have developers who know that you can set the processor affinity for each thread individually, making that thread run exclusively on the core you specify.JasonSilverSpring wrote: »I think one point some might be missing is that the one thread for ESO that is limiting will not only use the same core. It might hit the various cores at different times, but that limited thread will still CPU limit you.