Page 1 of 1

Screen Flickering

Posted: Wed Nov 24, 2010 2:37 pm
by medic
I box with dual monitors. When I select one box its smooth as silk but the non selected monitor is severely slow on updating. I search the forums with no luck. Anyone encountered this before?

Re: Screen Flickering

Posted: Wed Nov 24, 2010 4:51 pm
by bardrogue
Change your max background FPS in EQ advanced settings (under graphics tab) or configure mq2fps properly.

Edit: Also make sure both clients are not using the same cpu core (task manager > processes > eqgame.exe > set affinity). I noticed that if they both use the same core (seems to be randomly selected each time I launch) they run like shit in the background and foreground.

Re: Screen Flickering

Posted: Wed Nov 24, 2010 5:00 pm
by Deeprave
bardrogue wrote:Edit: Also make sure both clients are not using the same cpu core (task manager > processes > eqgame.exe > set affinity). I noticed that if they both use the same core (seems to be randomly selected each time I launch) they run like shit in the background and foreground.
Processor affinity is something that's actually handled by EQ itself, it isn't random.

By default it assigns each instance of eqgame.exe to a different core using a round-robin technique. You can override this by editing eqclient.ini and changing CPUAffinityX to be a core number 0 through <number_of_cores-1>. Obviously this has to be done prior starting up the game.

Re: Screen Flickering

Posted: Wed Nov 24, 2010 8:45 pm
by bardrogue
Deeprave wrote:
bardrogue wrote:Edit: Also make sure both clients are not using the same cpu core (task manager > processes > eqgame.exe > set affinity). I noticed that if they both use the same core (seems to be randomly selected each time I launch) they run like shit in the background and foreground.
Processor affinity is something that's actually handled by EQ itself, it isn't random.

By default it assigns each instance of eqgame.exe to a different core using a round-robin technique. You can override this by editing eqclient.ini and changing CPUAffinityX to be a core number 0 through <number_of_cores-1>. Obviously this has to be done prior starting up the game.
Good to know. It seemed random because they would occasionally get on the same core, and there are 6 cores to go through heh. I can get away with leaving them open all day (turning off luclin models solved all my crashes while zoning) so I just manually set my primary client to cores 0-3 and my secondary to 4-5 (I have a 6 core AMD cpu). Strangely, EQ has no problems when running on multiple cores even though some people still claim to have problems with it.