Question - Performance is now complete crap!

[Razkle]

Lets be clear, I know I box a lot more toons then the average bear. But every person I talk to that runs even a full group of 6 is having this issue!

We are all running VANILLA MQ2... In the last few weeks it has been getting steadily worse on lag or stutter or whatever the fuck you want to call it.

Boxes I used to run 24 or 30 toons on now cannot handle more then 12 and will only be stable at 8. CPU usage is now borked and crashes are piling up. Toons are lagging out and not doing jack shit.

Now this is NOT a kiss problem, I know that, it does it to eoknuke too. We are all comparing notes and no one is running anything crazy, just the base mq2 with cpuload running.

So my question is.... Is this a MQ2 issue or did DBG do something that makes toons use a lot more system resources and now have crippled large box groups?

 

[Zeeeeeee]

today im seeing lagging hard when i alt tab more than usual

 

[nyghteyes]

If I camp my toons for any reason, I'm rebooting or that toon will no longer function in any normal way. I just assumed something was borked in my system I couldnt fix. Memory leak, or some cache not being flushed.

I don't use CPUload

Refreshing injections doesnt fix it
Unloading mq2 doesnt fix it.
Camping completely out and starting up a new exe, 60% of the time it works every time, but only when playing a few toons.

Only fix I have it is to reboot if running a group or 2

 

[Zeeeeeee]

also i didnt change anything and ranger stopped detecting shout of the corpsestalker as a buff

 

[william12]

any of you running windows 10 ? I've had boxes stop responding when zoning a lot in the last few weeks. But only if I run 3 groups on that computer.

 

[Razkle]

I am running both 7 and 10 and its doing it on both

 

[minniemmee24]

im having no issues at all running 6-12 accounts and im on win 10, except for the other day i got an off the wall error with mq, but all i had to do was a full reboot and it fixed it.

 

[Razkle]

when a reboot fixes it then it is a memory leak kinda thing, I am PRETTY sure this is all around one of the core MQ2 plugins but I could be wrong... now to track down which one....

 

[Kellon]

any of you running windows 10 ? I've had boxes stop responding when zoning a lot in the last few weeks. But only if I run 3 groups on that computer.

I had that problem when I recently switched to Windows 10 from Windows 7.

After trying everything else over the space of a couple of weeks I set eqgame.exe to Windows 7 compatibility mode and it hasn't happened since.

Probably unrelated to your issue but may be worth a shot.

 

[da Man]

3 groups here (low lag but some on win 7), 1 group on a lappy (the lappy lags like crap win 10)

 

[1everdude]

I run 1 group, haven't noticed any lag at all lately. When I get to my PC I can post which plugins I do and don't use, that might help you guys track down the issue.

 

[BrianGragg]

Something that I have noticed is that a random of my 5 sessions will dead lock for about a full second and recover. It random when it does it but it happens. May or may not be the one I'm physically playing. Not sure if it's related. Fairly new system running win 10.


Sent from my iPhone using Tapatalk

 

[Dretski]

I haven't had this happen lately. On the other hand, I've had this problem before where Windows 10 runs some system shit (with a million different solutions out of which none has worked for me) that uses up almost all the RAM, CPU and HDD time until you reboot. Check the Windows task manager for any clues please.

 

[jamie75]

i had a similar issue and tracked it down to Window's turing on windows defender by default. you need to go into the windows defender settings and exclude the MQ and EQ folders. Window's defender hates teh writes to teh EQ/MQ log files

 

[nyghteyes]

Something that I have noticed is that a random of my 5 sessions will dead lock for about a full second and recover. It random when it does it but it happens. May or may not be the one I'm physically playing. Not sure if it's related. Fairly new system running win 10.


Sent from my iPhone using Tapatalk

You sure thats not just some time in the first few minutes when MQ2IC is protecting you from DBG sniffing?


*****
Razkle, I'm sure you've tried it, but completely disable Windows Defenders service. Exclusions weren't enough for mine and struggled for a long time to figure out thats what was killing mine.

 

[toots]

Mine is completely disabled and I am having similar issues.

 

[dorimor]

are you log files fecking huge ?

 

[toots]

Fresh install of both windows and eq. All my logs are basically empty.

 

[Noobhaxor]

Something is going on and the only man that can really speak to it is eqmule. I'm betting its something in the base EQ code that is messing things up.

 

[eqmule]

feel free to enlighten me then cause I cant think of anything that would lag your eq sessions.
It troubles me that's for sure, but this is one of those tricky bugs, where it could be just about anything, mq2, windows, eq itself, huge logfiles, a bad plugin... whatever...
and some people say they have no lag at all, while others say they DO have lag...
Someone that gets a lockup and can reliably reproduce it needs to debug it using visual studio and try to pinpoint it.

 

[EQStreamz]

Memory leak in the game itself ... you jest LOL

 

[Noobhaxor]

feel free to enlighten me then cause I cant think of anything that would lag your eq sessions.
It troubles me that's for sure, but this is one of those tricky bugs, where it could be just about anything, mq2, windows, eq itself, huge logfiles, a bad plugin... whatever...
and some people say they have no lag at all, while others say they DO have lag...
Someone that gets a lockup and can reliably reproduce it needs to debug it using visual studio and try to pinpoint it.

Well shit, I was hoping you'd say that Daybreak screwed up the code and their is a memory leak or something. My lag is very sparatic but not game breaking. I'm sure it will be fine after a couple more updates.

On a side note: Chrome is taking up over 1GB of memory.. WTF talk about a piece of shit. I remember when it was lightweight and awesome. Something of the past it seems.

 

[Razkle]

feel free to enlighten me then cause I cant think of anything that would lag your eq sessions.
It troubles me that's for sure, but this is one of those tricky bugs, where it could be just about anything, mq2, windows, eq itself, huge logfiles, a bad plugin... whatever...
and some people say they have no lag at all, while others say they DO have lag...
Someone that gets a lockup and can reliably reproduce it needs to debug it using visual studio and try to pinpoint it.

In NO WAY SHAPE OR FORM am I saying this is EqMule's fault! at all! Dude you are amazing! All you do for this game is more then I can ever thank you for!

That being said, I cannot pinpoint an exact cause so far, but I can tell you some common factors for both windows 7 and 10...

I have 11 boxes running. on FRESH boot they are all perfect, although each client takes more system resources then ever before and it is NOT sharing processors very well. Maybe mq2cpuload? Anyway what it manifests itself as is stutter lag... the tank runs to fetch a mob and every 20 steps he pauses for 2 steps... then goes on... healers pause instead of casting a heal, and the longer you run kiss/mq2/eoknuke the worse it gets! After an hour or so just swapping windows from instance to instance you have to wait 2 seconds or more for the instance to come to the forefront of windows. It has never been like that. Now what is causing it I do not know. But my gut says 1 of the plugins is hosed. Something is taking a lot of resources like nav, sorry but I think its nav or eqbc...

 

[q8reflex]

Those with OR without LAG, please answer this:

- Are you running Nvidia or AMD graphics card? or any other.
- Is your card more than 2GB of memory?

EQ is on Directx 9.0c and its limited with graphics card memory usage/mapping (maybe max 2gb) <-- quote from a dev in EoK beta after complaining about lag. This of course might not be the cause, but thought giving you guys some feedback since this thing only appeared after two events:

- The major Windows10 xbox patch.
- Release of EoK.

 

[etherealmist]

Use MQ2FPS if you're not already. It'll change your boxing life.

 

[aspire2008]

I haven't noticed any lag so maybe its a plugin issue with the compile? I'm running Win10, wineq2 everything is on stick figures, I do not use mq2cpuload.

I'd suggest listing out you all's settings so at least a pattern or common denominator can be found.

Also, make sure that you've updated to the latest directx9, as Daybreak requires the latest version since about 2 months ago. Was stated in a patch notes iirr or a Jchan post iirr.

Lastly the common denominator could be the brand of video cards you use. AMD vs Nvidia as there maybe driver conflicts.

 

[Wolfborn]

Could it be that KISS is getting bloated?

 

[Warl0ck45]

I have recently seen the "stutter" on a box or two. The entire session froze for a moment, then proceeded, froze, then proceeded, ect ect. It was like the session was on background and only getting access to the CPU every few moments.

"/unload"'ed MQ from that session, the stutter went away. Refreshed MQ injection, back to killin.

This is on a group I got parked in DH on the static mobs leveling some lowbies. They are up some 16 hours of the day. My main PC is powered up and running MQ until forced to reboot by win10. (run out of scheduled restart options =P)

This is on a Nvidia card set up, I7 960 CPU 4core hyperthreaded. I usually see about 160m-ish of RAM used per session, 1-3% CPU utilization. I run anywhere between 5 and 15 sessions. This is using MQ from the source site, and these plugins

[Plugins]
mq2advpath=1
mq2autodestroy=0
mq2autogroup=1
mq2autologin=1
mq2autosize=1
mq2bzsrch=1
mq2cast=1
mq2chatevents=1
mq2chatwnd=1
mq2clip=0
mq2cecho=1
mq2cursor=1
mq2custombinds=1
mq2debuff=1
mq2eqbc=1
mq2eqbugfix=1
mq2exchange=1
mq2fps=1
mq2hud=1
MQ2Ic=1
mq2itemdisplay=1
mq2labels=1
mq2map=1
mq2melee=1
mq2moveutils=1
mq2netbots=0
mq2netheal=0
mq2nonag=1
mq2relaytells=0
mq2rez=1
mq2spawnmaster=1
mq2task=0
mq2twist=1
mq2winpath=0
mq2gmcheck=0
mq2dpsadv=0
mq2xptracker=1
mq2linkdb=0
mq2medley=0

Just tossing in info incase it sparks ideas =)

 

[Razkle]

Could it be that KISS is getting bloated?

NOT kiss, its with all... kiss, eoknuke, autocleric... all...
so no tis not kiss, kiss is awesomeness incarnate!

- - - Updated - - -

I have recently seen the "stutter" on a box or two. The entire session froze for a moment, then proceeded, froze, then proceeded, ect ect. It was like the session was on background and only getting access to the CPU every few moments.

"/unload"'ed MQ from that session, the stutter went away. Refreshed MQ injection, back to killin.

This is on a group I got parked in DH on the static mobs leveling some lowbies. They are up some 16 hours of the day. My main PC is powered up and running MQ until forced to reboot by win10. (run out of scheduled restart options =P)

This is on a Nvidia card set up, I7 960 CPU 4core hyperthreaded. I usually see about 160m-ish of RAM used per session, 1-3% CPU utilization. I run anywhere between 5 and 15 sessions. This is using MQ from the source site, and these plugins

[Plugins]
mq2advpath=1
mq2autodestroy=0
mq2autogroup=1
mq2autologin=1
mq2autosize=1
mq2bzsrch=1
mq2cast=1
mq2chatevents=1
mq2chatwnd=1
mq2clip=0
mq2cecho=1
mq2cursor=1
mq2custombinds=1
mq2debuff=1
mq2eqbc=1
mq2eqbugfix=1
mq2exchange=1
mq2fps=1
mq2hud=1
MQ2Ic=1
mq2itemdisplay=1
mq2labels=1
mq2map=1
mq2melee=1
mq2moveutils=1
mq2netbots=0
mq2netheal=0
mq2nonag=1
mq2relaytells=0
mq2rez=1
mq2spawnmaster=1
mq2task=0
mq2twist=1
mq2winpath=0
mq2gmcheck=0
mq2dpsadv=0
mq2xptracker=1
mq2linkdb=0
mq2medley=0

Just tossing in info incase it sparks ideas =)

ahh will try an unload/refresh

 

[Bami]

Use MQ2FPS if you're not already. It'll change your boxing life.

I read that if you use this with isobox that you'll actually get negative performance (because the FPS functions of each interfere with eac hother)? I'll try to mess around but I use isobox so I've previously stayed away

 

[Razkle]

[Plugins]
mq2aaspend=1
mq2advpath=1
mq2afnuke=0
mq2autoaccept=1
mq2autocamp=0
mq2autoforage=0
mq2autologin=1
mq2autosize=0
mq2autoskills=0
mq2bagwindow=0
mq2bandolier=0
mq2bardswap=0
mq2bot=0
mq2bucles=0
mq2bufftool=0
mq2bzsrch=1
mq2camera=0
mq2cast=1
mq2charnotes=0
mq2chat=0
mq2chatwnd=1
mq2combat=0
mq2cpuload=1
mq2cursor=0
mq2custombinds=1
mq2customsound=0
mq2debuffs=1
mq2dps=0
mq2dpsadv=1
mq2eqbc=1
mq2eqbugfix=1
mq2eqim=0
mq2events=1
mq2exchange=1
mq2feedme=0
mq2fps=1
mq2gearscore=0
mq2gmail=0
mq2gmcheck=0
mq2headshot=0
mq2heals=0
mq2hud=1
mq2hudmove=0
mq2ic=1
mq2irc=0
mq2itemdisplay=1
mq2labels=1
mq2linkdb=0
mq2log=0
mq2manpage=0
mq2map=1
mq2medley=0
mq2melee=1
mq2missing=0
mq2moveutils=1
mq2nav=0
mq2netbots=0
mq2netheal=0
mq2nonagwindows=1
mq2notepad=0
mq2otd=0
mq2paranoid=0
mq2plattracker=0
mq2posse=1
mq2pvpalert=0
mq2radar=0
mq2raidutils=0
mq2randomstuff=0
mq2relaytells=0
mq2reward=0
mq2rez=1
mq2search=0
mq2slave=0
mq2spawnmaster=1
mq2spawns=0
mq2spellhotkeys=0
mq2spellsearch=0
mq2targets=0
mq2timestamp=0
mq2tooltip=0
mq2tracking=0
mq2tributemanager=0
mq2twist=0
mq2vendors=0
mq2viewport=0
mq2winxp=0
mq2xptracker=1

 

[creator]

I thought i seen that DB was messing with coding or something to that effect? but what ever it is yes things are fubar'ed atm....

 

[toots]

Any chance you remember where you saw that?

 

[creator]

No but i am looking to see if i can find it.

- - - Updated - - -

Not sure if this could be causing us issues or not but here is the write up i was talking about. https://www.everquest.com/news/eq-letter-from-holly-december-2016

 

[toots]

We are going to be able to remove a couple of contingencies to help lighten the load. Optimizing and improving client and server performance is a priority for us and always will be.

 

[hellfyre]

I'm usually between 6 to 10 boxes on one machine windows 7 and don't really see any noticeable lag while using eqbc but I do not use nav

 

[toots]

[Plugins]
mq2aaspend=1
mq2advpath=1
mq2autoaccept=1
mq2autologin=1
mq2bufftool=1
mq2bzsrch=1
mq2cast=1
mq2chatwnd=1
mq2cpuload=1
mq2custombinds=1
mq2debuffs=1
mq2dpsadv=1
mq2eqbc=1
mq2eqbugfix=1
mq2events=1
mq2exchange=1
mq2hud=1
mq2ic=1
mq2ifs=1
mq2itemdisplay=1
mq2labels=1
mq2log=0
mq2map=1
mq2melee=0
mq2moveutils=1
mq2nav=1
mq2nonagwindows=1
mq2posse=1
mq2rez=1
mq2viewport=1
MQ2Twist=1

 

[joojoobee]

I find a slowdown reproducibly when I character camps to the character screen, and then I log back in. From that relog in... Strangeness ensues. First, AdvNav doesn't work. Then I can't click buttons "randomly" on the screen. It doesn't "lock up" but it also doesn't respond. Inevitably, in about 5-10 minutes it will crash to the "do you want us to send details to Daybreak or Debug" grey popup. Next time I log in I will make it happen and I will hit debug. Of course, now it won't happen i am sure on queue.

As with others, the only way to fix it is to log the character out completely to desktop and relog in with AutoLogin.

JJB

 

[toots]

Does re-logging fix it for good? Or just for a few hours?

 

[Razkle]

ok so worked on and asked a ton of questions and we have it down to either MQ2SpawnMaster or Mq2CpuLoad.... after some checking MQ2CpuLoad is the common denominator and is prolly the culprit!