Bug - Stalled behavior when window not in focus

[disasteroid]

tl;dr: KA 8.2.4 worked fine until I manually extracted the MQ2 compile after the udpate on the 17th. Now melee characters very rarely run the return to camp scripts, resulting in buggy behavior. However, this problem only occurs on characters that aren't currently selected or were the last selected EQ window.

So, as described in the ticket fields above, this issue began after updating with the new compile. I did have a bit of operator failure with respect to RGUpdate (I had EQBCS running, got the .tmp error, then simply extracted the ZIP contents rather than figure out what was going wrong) so this might be the culprit as it deleted my MQ2.ini when I did this. That said, what happens is that my two melee characters get a serious case of The Dumb while running KissAssist, in that after a pull they just kind of shuffle around unless their EQ client is currently selected or was the last one selected, e.g. I'm writing this in my browser and my puller is doing just fine on the other monitor, but the bard is shuffling around doing nothing. This problem is fixed immediately when I tab to that window.

For example, I have my puller (SK) window selected, bard is farting around doing its little strafe dance, SK brings a mob back to camp, bard continues farting around until their window is selected, at which point they immediately return to their camp location and KA starts triggering their appropriate scripts (meleetwist, assist, etc.). To test it, I found a secluded location and ran KA overnight with a different group member being the active window. In the morning I checked the logs and after about 10 hours of operation, the SK had pulled a total of 5 mobs, which may have actually just pathed into it. The bard/SK fart dance just keeps the character strafing back and forth (at least this is what I see from another screen). The movements are very jerky, and since the character very, very rarely returns to camp without direct supervision it often dies due to wandering mobs, never activating the "hey i pulled somethin let's kill it" scripts and so on.

 

[TreeHuginDruid]

Having a eqgame client session running in the background would have no effect on the functionality of your toons in regards to KA.

I'm not sure how to even approach this issue... without knowing/seeing any issues in the config files for the toons that are doing a "fart dance" and not assisting the puller.

Just out of curiosity.. why is bard in camp waiting to assist pulled mob by SK.... doesn't your bard pull a but load better than the SK???
Anyway.. post the CONTENT of sk's and bard's kissassist_ToonName.ini file (wrapped in code tag please.. easier to read)... without that as a base to start with.. there is no way I can address this phantom problem.

No promises on a resolution to this.... as far as code for KA change... because we have never experienced an issue with toon assisting because their client session was in the background.

Make sure your not using multiple FPS (Frames Per Second) limiters as well please.. example... using MQ2FPS.dll in conjunction with build in and activated FPS services of WinEQ2 (eqplaynice) or the FPS limiter built into EQ itself... or some other third party multi-session client program.

 

[geEQ]

You may want to reinstall using the RGUpdater. I think this post explains what to do when you muck up the install and end up with bad files.

http://www.redguides.com/community/showthread.php/25093-RedGuides-Updater-v1-2?p=203687&viewfull=1#post203687

 

[etherealmist]

The FPS thing TreeHuginDruid mentioned sounds like the issue here. Try disabling MQ2FPS and see if that fixes it. If it does, you know what plugin to you need to adjust :P (or use the in game fps limiter). When I download a fresh MQ2 compile and don't have any .ini settings set yet, I have the same (very similar?) issue that you're describing.

 

[TreeHuginDruid]

You may want to reinstall using the RGUpdater. I think this post explains what to do when you muck up the install and end up with bad files.

http://www.redguides.com/community/showthread.php/25093-RedGuides-Updater-v1-2?p=203687&viewfull=1#post203687

I don't even bother with RGupdater... sorry RedBot, i know its your baby... lol

I just extract the release folder from compile release zip... copy all .DLL files from release to my redguides mq2 folder to update the new DLL files...
Then do the same for ALL files in the release folder with exception of the INI files (dont wanna overwrite mine by accident).
Then i copy the entire macros folder under release to my MQ2 folder and update anything.

Essentially the exact thing can be done with options in RGupdater 1.3, but i like to do it manually.

The ONLY thing that might be off is KissAssist.. the compile version may not be the most current / updated posted version...

We are addressing problem tickets and updating the KA code accordingly when signifigant issues need to be resolved in KissAssist.
So you should always check to make sure you have most current KA downloaded from the KA download thread. (Check the date in first line of KA... we update the patch date in it... so if you seeing ka 8.2.4 06-21-2015.. your outdated already.. since updated one is/sais 06-24-2015 as internal patch date )... etc etc

 

[Redbot]

RGUpdate is being overhauled very soon

 

[disasteroid]

Thanks for the tips! Currently in the process of fiddling with FPS settings (I had been using both MQ2FPS and WinEQ2 before this without issue, but might as well isolate), reinstalling .dll's and whatnot and will report back. Currently, the FPS fiddling hasn't produced a fix yet but I need to do a clean restart on MQ2 and will recheck with re-installed DLL files.

 

[Razkle]

can confirm this exact issue, seems to MOSTLY effect melee types acting crazy or crashing the client 2-3 times a day, only when not in focus (multiple clients) and I am running FPS, SO removing FPS and will test for 2 days.....

 

[disasteroid]

can confirm this exact issue, seems to MOSTLY effect melee types acting crazy or crashing the client 2-3 times a day, only when not in focus (multiple clients) and I am running FPS, SO removing FPS and will test for 2 days.....

I've unloaded MQ2FPS and am only limiting through WinEQ2. Running for some few hours now, behavior still present. It's like the character is lost until it receives focus--then it immediately returns to camp, and in the bard's case, starts singing the normal twist. So I've taken the next obvious step--turning off frame/render limits in WinEQ2--and the two in question did just fine until my router took a shit. Restarted all the clients, now it's back to same old bad behavior.

P.S. I also reinstalled the files from the June 18 compile earlier. You asked for KA ini's, here they are. (SK first, then bard. The SK is generally PullerTank, since I can only either have a reliable puller or a reliable tank if the bard is pulling.) The only down/holyshits they each have flagged are for dropping mod rods off their cursors.

[General]
KissAssistVer=8.2.4
Role=Tank
CampRadius=70
CampRadiusExceed=300
ReturnToCamp=1
ChaseAssist=0
ChaseDistance=25
MedOn=1
MedStart=15
MedCombat=0
LootOn=0
RezAcceptOn=1
AcceptInvitesOn=1
GroupWatchOn=2
EQBCOn=0
IRCOn=0
MiscGem=12
HoTTOn=0
CampfireOn=0
[SpellSet]
LoadSpellSet=0
SpellSetName=KissAssist
[Buffs]
BuffsOn=1
Buffs1=Drape of the Sepulcher
Buffs2=Sholothian Skin
Buffs3=Shroud of the Shadeborn
Buffs4=Worag's Covenant
Buffs5=Call of Shadow
Buffs6=NULL
Buffs7=Burdensome Pall
Buffs8=Archon Insignia Hoop
Buffs9=Sotor's Choker of Wrath
Buffs10=First Creation Harness
Buffs11=NULL
Buffs12=Jenrenee's Shoulder Guards
Buffs13=NULL
Buffs14=NULL
Buffs15=NULL
Buffs16=NULL
Buffs17=NULL
Buffs18=NULL
Buffs19=NULL
Buffs20=Pact of the Wolf Effect|Remove
RebuffOn=1
CheckBuffsTimer=30
[Melee]
AssistAt=97
MeleeOn=1
FaceMobOn=1
MeleeDistance=90
StickHow=front
AutoFireOn=0
[GoM]
GoMSHelp=Format - Spell|Target, MA Me or Mob, i.e. Rampaging Servant Rk. II|Mob
GoMSpell1=Dire Allegation
GoMSpell2=Korum's Bite
[AE]
AEOn=1
AERadius=50
AE1=Explosion of Hatred|2|Mob
AE2=Loathing|2|Mob
AE3=Explosion of Spite|2|Mob
AE4=Gorgon Mantle|2|Me
AE5=NULL
[DPS]
DPSOn=1
DPSSkip=10
DPSInterval=0
DPS1=Korum's Bite|99
DPS2=Vicious Bite of Chaos|100
DPS3=Spear of Sholoth|98
DPS4=Plague of Piqiorn|0
DPS5=Blood of Korum|100
DPS6=Encroaching Darkness|99|Weave
DPS7=Thought Leech|90|Weave
DPS8=Sholothian Skin|95
DPS9=Chattering Bones|93
DPS10=NULL
DPS11=NULL
DPS12=NULL
DPS13=NULL
DPS14=NULL
DPS15=NULL
[Aggro]
AggroOn=1
Aggro1=Terror of Desalin|100|<|Mob
Aggro2=Hate's Attraction|100|<|Mob
Aggro3=Provocation for Power|100|<|Mob
[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=1
Heals1=Touch of Urash|90|Tap
Heals2=Korum's Bite|95|Tap
Heals3=Dire Allegation|80|Tap
Heals4=Harmshield|30|Me
Heals5=Leech Touch|40|Tap
Heals6=Divine Companion Aura|50|Pet
Heals7=NULL
Heals8=NULL
XTarHeal=0
[Cures]
CuresOn=0
Cures1=NULL
Cures2=NULL
Cures3=NULL
[Pet]
PetOn=1
PetSpell=Minion of Sholoth
PetShrinkOn=1
PetShrinkSpell=Tiny Companion
PetBuffsOn=1
PetBuffs1=Gift of Urash
PetBuffs2=NULL
PetBuffs3=NULL
PetBuffs4=NULL
PetBuffs5=NULL
PetBuffs6=NULL
PetBuffs7=NULL
PetBuffs8=NULL
PetCombatOn=1
PetBreakMezSpell=NULL
PetRampPullWait=0
PetSuspend=1
PetToysGave=
[Burn]
BurnText=Decepticons Attack
BurnAllNamed=1
Burn1=Projection of Doom|Mob
Burn2=Second Spire|Me
Burn3=Unholy Aura Discipline|Me
Burn4=Chattering Bones|Mob
Burn5=Leechcurse Discipline|Me
Burn6=Scourge Skin|Me
Burn7=Visage of Death|Me
Burn8=NULL
Burn9=NULL
Burn10=NULL
Burn11=NULL
Burn12=NULL
Burn13=NULL
Burn14=NULL
Burn15=NULL
[Pull]
PullWith=Provocation for Power
MaxRadius=450
MaxZRange=800
PullWait=0
PullRoleToggle=0
ChainPull=0
ChainPullHP=90
ChainPullPause=30|2
[AFKTools]
AFKHelp=AFKGMAction=0 Off, 1 Pause Macro, 2 End Macro, 3 Unload MQ2, 4 Quit Game
AFKToolsOn=1
AFKGMAction=4
AFKPCRadius=400
CampOnDeath=1
ClickBacktoCamp=1
[Merc]
Help=To use: Turn off Auto Assist in Manage Mercenary Window
MercOn=0
MercAssistAt=96

[General]
KissAssistVer=8.2.4
Role=Assist
CampRadius=30
CampRadiusExceed=400
ReturnToCamp=1
ChaseAssist=0
ChaseDistance=25
MedOn=1
MedStart=20
MedCombat=0
LootOn=0
RezAcceptOn=1
AcceptInvitesOn=1
GroupWatchOn=2
EQBCOn=0
IRCOn=0
MiscGem=12
HoTTOn=0
CampfireOn=0
TwistOn=1
TwistMed=5
TwistWhat=1 2 3 4 2 5
[SpellSet]
LoadSpellSet=0
SpellSetName=KissAssist
[Buffs]
BuffsOn=1
Buffs1=Echo of Lunanyn|Aura
Buffs2=Sionachie's Crescendo
Buffs3=Ring of the Planar Explorer
Buffs4=Brazen Mask of Sentience
Buffs5=Gorta's Mantle
Buffs6=Cape of the Wailing Winds
Buffs7=Belt of the Faithful Servant
Buffs8=Decomposing Golem Brain
Buffs9=Selo's Sonata
Buffs10=NULL
Buffs11=NULL
Buffs12=NULL
Buffs13=NULL
Buffs14=NULL
Buffs15=NULL
Buffs16=NULL
Buffs17=NULL
Buffs18=NULL
Buffs19=NULL
Buffs20=NULL
RebuffOn=1
CheckBuffsTimer=20
[Melee]
AssistAt=95
MeleeOn=1
FaceMobOn=1
MeleeDistance=75
StickHow=behindonce
AutoFireOn=0
MeleeTwistOn=0
MeleeTwistWhat=1 2 3 4 2 5
[AE]
AEOn=0
AERadius=50
AE1=NULL
AE2=NULL
AE3=NULL
AE4=NULL
AE5=NULL
[DPS]
DPSOn=1
DPSSkip=20
DPSInterval=0
DPS1=Selo's Kick|98
DPS2=Lyrical Prankster|94
DPS3=Bladed Song|96
DPS4=Fierce Eye|95
DPS5=Quick Time|95
DPS6=Selo's Sonata|40
DPS7=NULL
DPS8=NULL
DPS9=NULL
DPS10=NULL
DPS11=NULL
DPS12=NULL
DPS13=NULL
DPS14=NULL
DPS15=NULL
[Aggro]
AggroOn=1
Aggro1=Fading Memories|80|>
Aggro2=NULL
Aggro3=NULL
[Pull]
PullTwistOn=1
PullWith=Boastful Bellow
MaxRadius=450
MaxZRange=300
PullWait=0
PullRoleToggle=0
ChainPull=1
ChainPullHP=70
ChainPullPause=30|2
[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=1
Heals1=Hymn of the Last Stand|20|Me
Heals2=Shield of Notes|60|Me
Heals3=NULL
Heals4=NULL
Heals5=NULL
XTarHeal=0
[Cures]
CuresOn=0
Cures1=NULL
Cures2=NULL
Cures3=NULL
[Mez]
MezOn=1
MezRadius=50
MezMinLevel=80
MezMaxLevel=110
MezStopHPs=80
MezSpell=Slumber of Kolain
MezAESpell=Wave of the Conductor|3
[Burn]
BurnText=Decepticons Attack
BurnAllNamed=1
Burn1=A Tune Stuck In Your Head|Me
Burn2=Quick Time|Me
Burn3=Funeral Dirge|Mob
Burn4=Cacophony|Mob
Burn5=Dance of Blades|Me
Burn6=Song of Stone|Mob
Burn7=Thousand Blades|Me
Burn8=Third Spire|Me
Burn9=NULL
Burn10=NULL
Burn11=NULL
Burn12=NULL
Burn13=NULL
Burn14=NULL
Burn15=NULL
[AFKTools]
AFKHelp=AFKGMAction=0 Off, 1 Pause Macro, 2 End Macro, 3 Unload MQ2, 4 Quit Game
AFKToolsOn=1
AFKGMAction=4
AFKPCRadius=400
CampOnDeath=1
ClickBacktoCamp=1
[Merc]
Help=To use: Turn off Auto Assist in Manage Mercenary Window
MercOn=0
MercAssistAt=92

 

[TreeHuginDruid]

(COUGH) ... set CPU afinnity ON in WinEQ2 settings.... if you have multiple processors.
Ensure this setting .. retest...reply back....

Also.. confirm you have FPS turned OF in EverQuest itself... as well as not running MQ2FPS.dll plugin... since you ARE using FPS in WinEQ2.

Nothing GLARING out at me as messed up setting in either of the toons ini files.....

Awaiting response.

 

[disasteroid]

• CPU affinity has been on (quad core, SK/bard are on different cores, the bard is on a core by itself).
• MQ2FPS is not listed as a loaded plugin, following the advice to test this out.
• EQ FPS is set to "unlimited" on the slider in options.

EDIT: Just a note in the interest of clarity, saying this is stalled behavior isn't really accurate, as through the constant jittery behavior I've seen the bard slide all the way around a zone wall--then, immediately after switching back to it, the character runs to their camphere position. And all the while they are singing songs and reapplying buffs (usually...).

 

[disasteroid]

Update: While I am still completely unsure as to why this issue started, I've finally had some free time to experiment and have solved the problem, albeit without understanding what caused it in the first place.

• With WinEQ2 not running and MQ2FPS not loaded, the characters behaved normally.
• With WinEQ2 running and MQ2FPS not loaded, the characters behaved erratically with EQPlayNice settings limiting background FPS/render at 10 FPS and 1/50 frames
• With WinEQ2 running and MQ2FPS loaded, the characters behaved erratically with EQPlayNice but NOT MQ2FPS settings limiting background FPS/render at 10 FPS and 1/50 frames
• With WinEQ2 running and MQ2FPS loaded, the characters behaved erratically with both EQPlayNice and MQ2FPS settings limiting background FPS/render at 10 FPS and 1/50 frames
• With WinEQ2 running and MQ2FPS loaded, the characters behaved erratically with EQPlayNice OFF and MQ2FPS settings limiting background FPS/render at 10 FPS and 1/50 frames*
• With WinEQ2 running and MQ2FPS loaded, the characters behaved normally with EQPlayNice OFF and MQ2FPS settings limiting background FPS/render at 50FPS and 1/1 frames
• With WinEQ2 running and MQ2FPS loaded, the characters behaved erratically with EQPlayNice OFF and MQ2FPS settings limiting background FPS/render at 10 FPS and 1/1 frames*
• With WinEQ2 running and MQ2FPS loaded, the characters behaved erratically with EQPlayNice OFF and MQ2FPS settings limiting background FPS/render at 50 FPS and 1/50 frames*

Methods: Each trial was conducted with 6 pulls. Trials were flagged as erratic if any of the following were true: 1) the characters failed to return to camp location after an NPC death; 2) the characters failed to execute the correct stick (front for the SK and behindonce for the bard); 3) the characters jitterbugged (back and forth strafed); 4) the characters failed to execute macro actions such as pulling, attacking or rebuffing. In all 36 trials that showed abnormal behavior, at least two of these conditions were met. Note that not all pulls were of the same mob nor of the same duration; since the trials were testing a sequence of events, however, this wasn't a factor as long as the fight lasted longer than 15-20 seconds. Those pulls that did not meet this criteria were not included.

Conclusions: Limiting either FPS and frame aliasing causes issues related to MQ2MoveUtils. These issues manifest in "jittery" behavior from using both /stick and /moveto commands. Furthermore, while using /moveto I believe the character cannot find it's specified location and this causes the jittery behavior--setting a higher mdist may provide an alternate solution to these two issues. Additionally, the conditions in trial 3 have been those I've used since I started using WinEQ2, which is to say that I played for over a month without issue with both MQ2FPS and WinEQ2 limiting FPS to 10 and renders to 1 in 50 frames.

Feel free to mark this issue as resolved, but if at some point in the future anyone can shed some light on why this is actually happening I'd love to know. I'd like to be able to set all my characters back to 10 FPS and 1/50 frames as having to manually change them each time I load EQ is a pain in the ass.

- - - Updated - - -

Well the problem is still present. For whatever reason the bard is running mostly fine, it still doesn't perform 100%, but the SK can't pull for shit if it's not the current or last EQ window selected. I can have that window selected, watch her run out to pull, switch to another window and watch as the SK simply strafes back and forth. I'm guessing it goes on forever, but she usually dies before then.

 

[Maskoi]

#1 MQ2FPS can not be loaded with EQPlaynice, They cnflict. They always have.
#2 Did you try it without wineq2?
#3 some people have issues with mq2moveutils and wineq2

Your character runs into walls or off into illogical directions

    If you are using WinEQ, you should disable true movement. (/stick set wineq on)
    If you are not using WinEQ, you may have stucklogic disabled or your stucklogic settings need to be configured properly.

Your character spins in circles while jumping up and down

    You are likely using wineq2 while trying to use true movement. set wineq support on
    Otherwise, your framerate is really, really bad and you need to adjust your stucklogic settings by a very large amount 

wineq

    By default, MoveUtils uses actual keypresses to control movement (regardless of heading settings)
    WinEQ2 has a bug where background sessions can have their alt keys and certain mouse buttons held down, causing movement to run in weird directions

 

[disasteroid]

#1 MQ2FPS can not be loaded with EQPlaynice, They cnflict. They always have.
#2 Did you try it without wineq2?
#3 some people have issues with mq2moveutils and wineq2

Your character runs into walls or off into illogical directions

    If you are using WinEQ, you should disable true movement. (/stick set wineq on)
    If you are not using WinEQ, you may have stucklogic disabled or your stucklogic settings need to be configured properly.

Your character spins in circles while jumping up and down

    You are likely using wineq2 while trying to use true movement. set wineq support on
    Otherwise, your framerate is really, really bad and you need to adjust your stucklogic settings by a very large amount 

wineq

    By default, MoveUtils uses actual keypresses to control movement (regardless of heading settings)
    WinEQ2 has a bug where background sessions can have their alt keys and certain mouse buttons held down, causing movement to run in weird directions

ha ha ha

here's the punchline: WinEQ=off

here's the joke: i accidentally overrate my INIs when I manually updated the compile

 

[Maskoi]

Is it working now?

 

[disasteroid]

Yuuuuuuuuuuuup! Thanks man!