any idea of best usage practice of that new feature for WinEQ boxers when yuo usually (like me) have one client with full graphical options / max resolution and 4 clients with low graphical settings / min resolution ?- Multi-core CPU Support: If you have a Multi-core CPU you no longer have to manually set their processor affinity! EverQuest will automatically assign itself to an available core. If you run multiple copies of the client, each new copy running will assign itself to the next available core. Those interested in customizing which core or cores EverQuest clients run on, check the forums.
new EQ expansion
Moderators: Lavish Software Team, Moderators
new EQ expansion
The default (on) is the recommended value. To my knowledge, EQ isn't optimized for multiple cores, so you probably won't gain much if anything from disabling the feature. More importantly, it's possible that the framerate limiting features of EQPlayNice, potentially the client's limiter feature as well, will malfunction without the feature on -- it could result in lower than desired framerates.
But, your mileage will vary, so in the end, you can just test it on and test it off, and see if you notice a difference. If one seems to perform better, then that's your answer.
But, your mileage will vary, so in the end, you can just test it on and test it off, and see if you notice a difference. If one seems to perform better, then that's your answer.
Ok I'm told that's from the EQ patch notes, I was originally thinking you were talking about the WinEQ feature that rotates cores for EQ sessions.
That makes the answer as follows:
1. The feature they just added to EQ has been available and in use by WinEQ for a very long time.
2. The feature they just added to EQ could potentially assign a different core than WinEQ is assigning. There may be a WinEQ update to fix that.
3. When using WinEQ after said update, the WinEQ feature will override the EQ feature when enabled. When disabled (with or without any WinEQ update), the EQ feature will perform as intended.
That makes the answer as follows:
1. The feature they just added to EQ has been available and in use by WinEQ for a very long time.
2. The feature they just added to EQ could potentially assign a different core than WinEQ is assigning. There may be a WinEQ update to fix that.
3. When using WinEQ after said update, the WinEQ feature will override the EQ feature when enabled. When disabled (with or without any WinEQ update), the EQ feature will perform as intended.