Problem - Background clients say "Not responding" when left alone too long

[adfallon68]

Above detail should have all info. It seems background clients are locking up when left overnight. Not all of them, but 2-4 of them every night. It's happened for many months, since I set things up. I just never got around to trying to fix it. I don't use Isboxer or anything else.

 

[Maskoi]

Post your macroquest2.ini file please.

Are you running everything as admin?

 

[Redbot]

Have you tried on a different PC? I wonder if it could be an issue with the computer.

If you don't want to pay for isboxer, I recommend wineq2 - it's free.

http://www.lavishsoft.com/download/wineq2

 

[adfallon68]

Re: Background clients say "Not responding" when left alone too long

Will post ini shortly. Yes I've tried it on 5 different computers. It does the same thing on all 5. 3 Intel based, 2 AMD based. 4 Windows 7 1 windows 8. All running current patches / clients, etc. I know a long time ago it didn't used to do it. But it has been doing it for many months, through a number of kissassist revisions. .inis up soon.

- - - Updated - - -

Yes running everything as admin. I can post the other 4 computers as well, as it is happening on all 5 computers, I've tried all of them. Let me know if you want others.

Here's one my macroquest2.ini:

[MacroQuest]
MacroPath=.\Macros
LogPath=.\Logs
DebugSpewToFile=0
FilterSkills=0
FilterTarget=0
FilterMoney=0
FilterFood=0
FilterMacro=0
FilterEncumber=0
FilterDebug=0
FilterMQ=0
KeepKeys=1
LaxColor=0
AllErrorsDumpStack=1
AllErrorsFatal=0
HUDMode=UnderUI
MQ2LoadingMsg=0
ExactSearchCleanNames=0
TimeStampChat=1
BeepOnTells=0

[Aliases]
/a=/anonymous
/addfriend=/echo AddFriend
/addignore=/echo AddMobIgnore
/addpull=/echo AddMobPull
/afktoolson=/echo Reset AFKTools AFKToolsOn
/assistat=/echo Reset Melee AssistAt
/autofireon=/echo toggle AutoFireOn
/autorezon=/echo toggle AutoRezOn
/b=/bazaar
/ba=/bazaar
/buffson=/echo toggle BuffsOn
/c=/consider
/campfire=/echo Summon Campfire
/camphere=/echo toggle ReturnToCamp
/campradius=/echo Reset General CampRadius
/cha=/channel
/chase=/echo toggle ChaseAssist
/chasedistance=/echo Reset General ChaseDistance
/chaseoff=/echo Reset General ChaseAssist 0
/chaseon=/echo Reset General ChaseAssist 1
/d=/duel
/debug=/echo toggle Debug
/debugall=/echo DebugAll
/debugbuffs=/echo toggle DebugBuffs
/debugcombat=/echo toggle DebugCombat
/debugheal=/echo toggle DebugHeal
/debugmez=/echo toggle DebugMez
/debugpull=/echo toggle DebugPull
/depositstuff=/echo NinjadvLoot depositing items to guildbank
/dpsinterval=/echo Reset DPS DPSInterval
/dpson=/echo Reset DPS DPSOn
/dpsskip=/echo Reset DPS DPSSkip
/exp=/echo ${Me.PctExp}% experience...
/f=/feedback
/fa=/fastdrop
/g=/gsay
/gmlist=/who all gm
/gu=/guildsay
/healson=/echo Reset Heals HealsOn
/hp=/echo Current Health: ${Me.CurrentHPs} -- Max Health: ${Me.MaxHPs}
/key=/keys
/kisscheck=/echo KissCheck
/kissedit=/echo kissedit
/load=/loadspells
/lootdestroy=/echo LootIniItem Destroy ${Cursor.Name}
/lootignore=/echo LootIniItem Ignore ${Cursor.Name}
/lootkeep=/echo LootIniItem Keep ${Cursor.Name}
/looton=/echo toggle LootOn
/lootsell=/echo LootIniItem Sell ${Cursor.Name}
/m=/msg
/mana=/echo Current Mana: ${Me.CurrentMana} -- Max Mana: ${Me.MaxMana}
/maxradius=/echo Reset Pull MaxRadius
/maxzrange=/echo Reset Pull MaxZRange
/medcombat=/echo toggle MedCombat
/medstart=/echo Reset General MedStart
/meleedistance=/echo Reset Melee MeleeDistance
/meleeon=/echo toggle MeleeOn
/mercassistat=/echo Reset Merc MercAssistAt
/mezon=/echo Reset Mez MezOn
/newif=/if
/npc=/who npc
/peton=/echo toggle PetOn
/pettoyson=/echo toggle PetToysOn
/r=/reply
/rebuffon=/echo toggle RebuffOn
/sellstuff=/echo NinjadvLoot selling items to vendor
/setae=/echo Set AE
/setaggro=/echo Set Aggro
/setbuffs=/echo Set Buffs
/setburn=/echo Set Burn
/setcure=/echo Set Cure
/setdps=/echo Set DPS
/setheals=/echo Set Heals
/slotid=/echo ${SelectedItem.InvSlot}
/status=/echo toggle Show
/switch=/echo Switch Target
/t=/tell
/ta=/tap
/w=/who


[Substitutions]
omg=Oh My God


[Plugins]
mq2advpath=1
mq2autoaccept=1
mq2autologin=1
mq2bzsrch=1
mq2cast=1
mq2chatwnd=1
mq2custombinds=1
mq2debuffs=1
mq2eqbc=1
mq2eqbugfix=1
mq2exchange=1
mq2hud=1
mq2itemdisplay=1
mq2labels=1
mq2map=1
mq2melee=1
mq2moveutils=1
mq2netbots=1
mq2nonagwindows=1
mq2posse=1
mq2rez=1
mq2spawnmaster=1
mq2spawns=1
mq2targets=1
mq2twist=1
mq2xptracker=1


[Key Binds]
RANGED_Nrm=clear
RANGED_Alt=clear
MQ2CHAT_Nrm=.
MQ2CSCHAT_Nrm=/
EQBC_Nrm=clear
MELEE_Nrm=clear
RANGE_Nrm=clear
STOP_BCK_Nrm=clear
STOP_BCK_Alt=Down
STOP_LFT_Nrm=clear
STOP_LFT_Alt=Left
STOP_RGT_Nrm=clear
STOP_RGT_Alt=Right
STOP_STRAFE_LFT_Nrm=Z
STOP_STRAFE_LFT_Alt=clear
STOP_STRAFE_RGT_Nrm=X
STOP_STRAFE_RGT_Alt=clear
MUTILS_FWD_Nrm=clear
MUTILS_BCK_Nrm=clear
MUTILS_LFT_Nrm=clear
MUTILS_RGT_Nrm=clear
MUTILS_STRAFE_LFT_Nrm=Z
MUTILS_STRAFE_RGT_Nrm=X
MUTILS_AUTORUN_Nrm=Num_Lock
MUTILS_FWD_Alt=Up
MUTILS_BCK_Alt=Down
MUTILS_LFT_Alt=Left
MUTILS_RGT_Alt=Right
MUTILS_STRAFE_LFT_Alt=clear
MUTILS_STRAFE_RGT_Alt=clear
MUTILS_AUTORUN_Alt=clear

[SWho Filter]
Holding=1


[Captions]
MQCaptions=1
Update=35
Player1=${If[${NamingSpawn.Mark},${NamingSpawn.Mark} - ,]}${If[${NamingSpawn.Trader},Trader ,]}${If[${NamingSpawn.Invis},(${NamingSpawn.DisplayName}),${NamingSpawn.DisplayName}]}${If[${NamingSpawn.AFK}, AFK,]}${If[${NamingSpawn.Linkdead}, LD,]}${If[${NamingSpawn.LFG}, LFG,]}${If[${NamingSpawn.GroupLeader}, LDR,]}
Player2=${If[${NamingSpawn.Mark},${NamingSpawn.Mark} - ,]}${If[${NamingSpawn.Trader},Trader ,]}${If[${NamingSpawn.Invis},(${NamingSpawn.DisplayName}),${NamingSpawn.DisplayName}]}${If[${NamingSpawn.Surname.Length}, ${NamingSpawn.Surname},]}${If[${NamingSpawn.AFK}, AFK,]}${If[${NamingSpawn.Linkdead}, LD,]}${If[${NamingSpawn.LFG}, LFG,]}${If[${NamingSpawn.GroupLeader}, LDR,]}
Player3=${If[${NamingSpawn.Mark},${NamingSpawn.Mark} - ,]}${If[${NamingSpawn.Trader},Trader ,]}${If[${NamingSpawn.Invis},(${NamingSpawn.DisplayName}),${NamingSpawn.DisplayName}]}${If[${NamingSpawn.Surname.Length}, ${NamingSpawn.Surname},]}${If[${NamingSpawn.AFK}, AFK,]}${If[${NamingSpawn.Linkdead}, LD,]}${If[${NamingSpawn.LFG}, LFG,]}${If[${NamingSpawn.GroupLeader}, LDR,]}${If[${NamingSpawn.Guild.Length},\n<${If[${NamingSpawn.GuildStatus.NotEqual[member]},${NamingSpawn.GuildStatus} of ,]}${NamingSpawn.Guild}>,]}
Player4=${If[${NamingSpawn.Mark},${NamingSpawn.Mark} - ,]}${If[${NamingSpawn.Trader},Trader ,]}${If[${NamingSpawn.AARank},${NamingSpawn.AATitle} ,]}${If[${NamingSpawn.Invis},(${NamingSpawn.DisplayName}),${NamingSpawn.DisplayName}]}${If[${NamingSpawn.Surname.Length}, ${NamingSpawn.Surname},]}${If[${NamingSpawn.Suffix.Length}, ${NamingSpawn.Suffix},]}${If[${NamingSpawn.AFK}, AFK,]}${If[${NamingSpawn.Linkdead}, LD,]}${If[${NamingSpawn.LFG}, LFG,]}${If[${NamingSpawn.GroupLeader}, LDR,]}${If[${NamingSpawn.Guild.Length},\n<${If[${NamingSpawn.GuildStatus.NotEqual[member]},${NamingSpawn.GuildStatus} of ,]}${NamingSpawn.Guild}>,]}
NPC=${If[${NamingSpawn.Mark},${NamingSpawn.Mark} - ,]}${If[${NamingSpawn.Assist},>> ,]}${NamingSpawn.DisplayName}${If[${NamingSpawn.Assist}, - ${NamingSpawn.PctHPs}%<<,]}${If[${NamingSpawn.Surname.Length},\n(${NamingSpawn.Surname}),]}
Corpse=${NamingSpawn.DisplayName}'s corpse
Pet=${If[${NamingSpawn.Mark},${NamingSpawn.Mark} - ,]}${If[${NamingSpawn.Assist},>> ,]}${NamingSpawn.DisplayName}${If[${NamingSpawn.Assist}, - ${NamingSpawn.PctHPs}%<<,]}${If[${NamingSpawn.Master.Type.Equal[PC]},\n(${NamingSpawn.Master}),]}


[Caption Colors]
PC=OFF
PC-Color=ff00ff
PCCon=OFF
PCPVPTeam=OFF
PCRaid=OFF
PCRaid-Color=ff7f
PCClass=OFF
PCGroup=OFF
PCGroup-Color=ffff00
PCTrader=ON
PCTrader-Color=ff7f00
NPC=OFF
NPC-Color=ff0000
NPCCon=ON
NPCClass=OFF
NPCMerchant=ON
NPCMerchant-Color=ff7f00
NPCBanker=ON
NPCBanker-Color=c800ff
NPCAssist=ON
NPCAssist-Color=ffff00
NPCMark=ON
NPCMark-Color=ffff00
PetNPC=OFF
PetNPC-Color=ff0000
PetPC=OFF
PetPC-Color=ffff00
PetClass=OFF
PetClass-Color=ff0000
Corpse=OFF
Corpse-Color=ff0000
CorpseClass=OFF
CorpseClass-Color=ff0000

 

[adfallon68]

Trying to avoid having to run more programs to get Kissassist to work consistently. Does the macro not work right without 3rd party programs ?

 

[Maskoi]

What 3rd party programs?

My guess is these plugins are locking you up

mq2spawnmaster=1
mq2spawns=1
mq2targets=1

since they all check spawns whenever something dies or respawns and you are running 3 of them. I am pretty sure this is what is locking you up.

 

[TreeHuginDruid]

You do not need any third party software to run MQ2 or the KissAssist macro.
I can not speak for RedBot but I assume he mentioned WinEQ2 because it is often used by multiboxers to multibox efficiently with minimul extra system resources.

Your configs are not throwing any red flags up that I can notice off the bat, but there mere fact it is happening on all systems points in the direction of something being off with your setup across the board.

The only way to effectively troubleshoot this issue is to isolate/identify/fix issue on one PC .. then see if resolution works for all pc's after.

So lets concentrate on only 1 PC ... the one with the lightest load on it..

On that PC... do the following:

1) Backup or save your RedGuides MacroQuest2\Macros directory structure to a separate area.
2) Backup or save your RedGuides MacroQuest2\SERVER_TOONNAME.ini files to a separate area.
3) DELETE THE ENTIRE RedGuides MacroQuest2 structure.
4) Do a fresh download of the compile ... and extract the content to where you will want your RedGuides MacroQuest2 install to go.
5) Copy your SERVER_TOONNAME.ini files and Macros directory structure back into this clean install.
6) DO NOT load any additional plugins other than what is in the default macroquest.ini file that is copied during the clean install. Let Kissassist macro load the required plugins it needs to run.
7) Run it as usual and let me know if there is any change in system lockup.

Also:
If you have powersaving options on for that computer... make sure it is not set to "turn off hard disk" or "put computer to sleep" after a specified time period... or set to go into hard disk shutdown mode in hybernation sleep mode.

I have had systems lock on me due to this. Its fine to have the monitor shut down during power save mode.. but never hard disk. Systems sometimes lock when attempting to "wake up" from hybernation/sleep mode when hard disks are set to turn off after time period.

What 3rd party programs?
My guess is these plugins are locking you up
mq2spawnmaster=1
mq2spawns=1
mq2targets=1
since they all check spawns whenever something dies or respawns and you are running 3 of them. I am pretty sure this is what is locking you up.

Aye ... I agree Maskoi .. that's why I want him to no load any plugins but required by KissAssist (which it will load anyway).

Post back with results please.

 

[adfallon68]

What 3rd party programs?

My guess is these plugins are locking you up

since they all check spawns whenever something dies or respawns and you are running 3 of them. I am pretty sure this is what is locking you up.

3rd party plug in reference was to using wineq. In understand it can be a useful tool, but I'm trying to 'keep it simple'.

I'll remove those 3 plugins on one PC since that's a pretty quick and easy check. If that doesn't fix it I'll go the next step as mentioned below by TreeHuginDruid. Thanks for the suggestions I hope this straightens it out !

-- Edit --

I just made the changes to the spawn plugins removed all 3. While there I checked my power settings and the HD was set to shut down after 20 minutes. I de-activated that as well. So I have 1 PC with all 3 spawn plugins removed, and the power settings adjusted. I changed a second PC to just remove the 3 plugins. In a couple days I should know if either one of those are fixed. If not I'll take it further and re-install Kissassist fresh. Though I don't think that will do it by itself since I had to do that a week ago when installing a new SSD in one PC and it still has that same problem. So it's probably the power settings or the 3 spawn plugins. Time will tell...

 

[TreeHuginDruid]

3rd party plug in reference was to using wineq. In understand it can be a useful tool, but I'm trying to 'keep it simple'.

I'll remove those 3 plugins on one PC since that's a pretty quick and easy check. If that doesn't fix it I'll go the next step as mentioned below by TreeHuginDruid. Thanks for the suggestions I hope this straightens it out !

-- Edit --

I just made the changes to the spawn plugins removed all 3. While there I checked my power settings and the HD was set to shut down after 20 minutes. I de-activated that as well. So I have 1 PC with all 3 spawn plugins removed, and the power settings adjusted. I changed a second PC to just remove the 3 plugins. In a couple days I should know if either one of those are fixed. If not I'll take it further and re-install Kissassist fresh. Though I don't think that will do it by itself since I had to do that a week ago when installing a new SSD in one PC and it still has that same problem. So it's probably the power settings or the 3 spawn plugins. Time will tell...

Ok .. let us know.

 

[TreeHuginDruid]

Any update?

 

[snowshovel]

Scheduled maintenance tasks were causing this for me with Windows 8/Automatic maintenance, never used KA on Windows 7 so cant comment on that. But my game clients (4-6 of them) would freeze.

 

[TreeHuginDruid]

Scheduled maintenance tasks were causing this for me with Windows 8/Automatic maintenance, never used KA on Windows 7 so cant comment on that. But my game clients (4-6 of them) would freeze.

Your reply is not clarifying if your issue is resolved.. after removing the additional plugins as was suggested... and turning off the hard disk shut down as was suggested.
Backround tasks like scheduled system maintenance could certainly be a factor in it... but you did not specify if changing that value resolved anything.

 

[adfallon68]

Re: Background clients say "Not responding" when left alone too long

So far I have modified any sleep mode / hard disk timeout time settings as listed above. I have removed all 3 of the spawn plugins as mentioned above. It is still doing the same thing as I originally listed. I did set up 1 PC and load mmobugs MQ in a new directory, then load isboxer, and that computer runs no problems at all. The only thing I haven't done yet is do a complete re-install from scratch of redguides as mentioned.

I've turned a few guildies on to kissassist in the last couple months, and I'm getting feedback from one of them that he started having the same issue when he went to 6 toons on his box crew. He was fine with 4 accounts, but when he upped to 6 he's having the same lockups I am.

To be honest this is becoming enough work and hassle I'm leaning toward just scrapping it and going with mmobugs, since I have several friends that use it and don't have the issue I'm having whatsoever.

I'm starting to feel like I'm a paying subscriber that is having to pay to troubleshoot something that doesn't work in a 6 man box crew setup without 3rd party programs.

Are there other users that run a 6 man crew, without any WinEQ, ISBoxer, or anything other than just Kissassist and the MQ that comes with it, runs their crews overnight / up to 24 hours without any lockups ?

Also I do reboot my PC once every day. I never expect (because I can't trust it) it to run for more than 24 hours without problems.

- - - Updated - - -

Your reply is not clarifying if your issue is resolved.. after removing the additional plugins as was suggested... and turning off the hard disk shut down as was suggested.
Backround tasks like scheduled system maintenance could certainly be a factor in it... but you did not specify if changing that value resolved anything.

Sorry I just saw this. My issue is not resolved. I removed additional plugins. I turned off hard disk shutdown, a couple did have it set to power down after 20 minutes I believe. There are no background tasks running whatsoever (system maintenance or otherwise). This happens on 5 different computers in our house, no matter which one I run it on I get the same results. But as I mentioned at this point, based on feedback / comments I've seen (this thread and others) I'm wondering if people are currently using KISSASSIST with 6 EQ clients, with no WinEQ / ISBoxer / any other 3rd party application, and running for 24 hours without lockups of some / all EQ clients ?

Do those that actually make / support the macro use it in this manner at all ? Or are they running ISBoxer / WinEQ / something else as well ?

And if so I'm wondering what the hardware / setup is. I believe my systems should be sufficient to do this without complications. Their config includes:

3 have Core i7 processors 3630QM 2.4GHz, 16GB RAM, GTX 660M 2GB video (2 win7, 1 win8.1)

1 has AMD Phenom II X6 1035T 2.6GHz processor, 16GB RAM, GTX 660 2GB video (win7)

1 has AMD FX-6300 3.5GHz processor, 16GB RAM, GTX 660 2GB video (win7)

Every one has a minimum Win7 Windows Experience Index score of 7.0 or higher. 1 is Windows 8.1 which doesn't have Win Exp Index, but has the same specs as others that do.

As I type out the hardware specs it occurs to me they all have SSDs. They are various models, but they all work flawlessly for anything. Is there potentially some complication using an SSD with KISS ? I ask if there is with KISS since I started trying out other macros and have 0 problem running any other one. Currently I can run one called e3 flawlessly, or a couple from mmobugs without the lockups listed above.

 

[Maskoi]

Kiss 8 gets released tomorrow. We streamlined a lot of code. Lets see if Kiss 8 fixes the issue. If not we have to look harder at what is locking you up.