CPU Affinity -- Clientcore changes to INI

What Metanis said. Affinty/Core is only consumed when the client starts up. After that, you could manually change the affinity from task manager and the game wouldnt care and the ini wouldnt change.

As far as my example goes, no one should be doing that, I was just highlighting the effect of setting the value is on the process affinity that you can verify from task manager.

Still doesn't answer the question

Nothing happens. The remaining client continues to run on core 12.

After all the confusion I corrected my initial post as a guide:

https://forums.daybreakgames.com/eq...lientcore-changes-to-ini.285260/#post-4163438

Let me know when something there is wrong.

My EQ was running slow and so I checked it. Mine has (cpuaffinity1=1) AND right after that line has (clientCore0=-1).

I changed the cpuaffinity to neg 1 and that did seem to speed things up a lot. Still not perfect but at least I'm not having to take a nap while zoning now. Any idea why I would have both though?

cpuaffinity got replaced by ClientCore, so it should not have any effect on changing the parameters there. You can delete the lines with cpuaffinity as they are obsolete.

Old eqclient.ini data. I nuked my eqclient.ini away a few months back and let it rebuild, a lot faster now.

K, thanks. I might try that if it slows down again.

I highly recommend leaving ClientCore# variables with the default value of -1. Any other value can have detrimental impact on performance:

[Defaults]
ClientCore0=-1
ClientCore1=-1

We're tracking this as a bug internally.

Our servers buff pile has lost half its population, I suggest a fix soon.