Question - Kiss response speed

[pythag1]

Hello
Running Kiss on various characters but the response time to the characters running kiss seems delayed I have most things turned off and the main character does not run a macro and is played manually, each character running Kiss is simply /mac kissassist - with the main character targeted which is a beastlord.

[CODE title="My kiss"][General]
KissAssistVer=12.002
Role=Assist
CampRadius=30
CampRadiusExceed=400
ReturnToCamp=0
ChaseAssist=1
ChaseDistance=25
MedOn=1
MedStart=20
MedStop=100
MedCombat=0
LootOn=0
RezAcceptOn=1|90
AcceptInvitesOn=1
GroupWatchOn=1
GroupWatchCheck=FALSE
CorpseRecoveryOn=0
EQBCOn=0
DanNetOn=0
DanNetDelay=20
IRCOn=0
CampfireOn=0
CharInfo=Beastlord|13|GOLD
DefaultUI=TRUE
DPSMeter=0
ScatterOn=0
LOSBeforeCombat=0
UseSpawnMaster=0
XTSlot=1
[SpellS]
MiscGem=8
MiscGemLW=0
MiscGemRemem=1
LoadSpellSet=2
SpellSetName=KissAssist
CastingInterruptOn=1
CheckStuckGem=1
Gem1=Spirit of Sharik
Gem2=Minor Healing
Gem3=NULL
Gem4=NULL
Gem5=NULL
Gem6=NULL
Gem7=NULL
Gem8=NULL
[Buffs]
BuffsOn=0
BuffsSize=20
Buffs1=NULL
Buffs2=NULL
Buffs3=NULL
Buffs4=NULL
Buffs5=NULL
Buffs6=NULL
Buffs7=NULL
Buffs8=NULL
Buffs9=NULL
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=10
PowerSource=NULL
[Melee]
AssistAt=98
MeleeOn=1
FaceMobOn=1
MeleeDistance=300
StickHow=snaproll
AutoFireOn=0
UseMQ2Melee=0
TargetSwitchingOn=0
PetTauntOverride=0
[GoM]
GoMSHelp=Format - Spell|Target, MA Me or Mob, i.e. Rampaging Servant Rk. II|Mob
GoMSize=3
GoMSpell1=NULL
GoMSpell2=NULL
GoMSpell3=NULL
[AE]
AEOn=0
AESize=10
AERadius=50
AE1=NULL
AE2=NULL
AE3=NULL
AE4=NULL
AE5=NULL
AE6=NULL
AE7=NULL
AE8=NULL
AE9=NULL
AE10=NULL
[DPS]
DPSOn=0
DPSSize=20
DPSSkip=20
DPSInterval=2
DPS1=NULL
DPS2=NULL
DPS3=NULL
DPS4=NULL
DPS5=NULL
DPS6=NULL
DPS7=NULL
DPS8=NULL
DPS9=NULL
DPS10=NULL
DPS11=NULL
DPS12=NULL
DPS13=NULL
DPS14=NULL
DPS15=NULL
DPS16=NULL
DPS17=NULL
DPS18=NULL
DPS19=NULL
DPS20=NULL
DebuffAllOn=0
[Aggro]
AggroOn=0
AggroSize=5
Aggro1=NULL
Aggro2=NULL
Aggro3=NULL
Aggro4=NULL
Aggro5=NULL
[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=1
HealInterval=0
AutoRezOn=0
HealsSize=5
Heals1=Minor Healing|30
Heals2=NULL
Heals3=NULL
Heals4=NULL
Heals5=NULL
XTarHeal=0
XTarHealList=Xtar slots here Example: 5|6|7
HealGroupPetsOn=0
RezMeLast=0
[Cures]
CuresOn=0
CuresSize=5
Cures1=NULL
Cures2=NULL
Cures3=NULL
Cures4=NULL
Cures5=NULL
[Pet]
PetOn=1
PetSpell=Spirit of Sharik
PetFocus=NULL
PetShrinkOn=0
PetShrinkSpell=Tiny Companion
PetBuffsOn=0
PetBuffsSize=8
PetBuffs1=NULL
PetBuffs2=NULL
PetBuffs3=NULL
PetBuffs4=NULL
PetBuffs5=NULL
PetBuffs6=NULL
PetBuffs7=NULL
PetBuffs8=NULL
PetCombatOn=1
PetAssistAt=98
PetAttackDistance=300
PetToysSize=6
PetBreakMezSpell=NULL
PetRampPullWait=0
PetSuspend=0
MoveWhenHit=0
PetHoldOn=0
PetForceHealOnMed=0
PetToysGave=
[Merc]
Help=To use: Turn off Auto Assist in Manage Mercenary Window
MercOn=0
MercAssistAt=92
[Burn]
BurnAllNamed=0
UseTribute=0
BurnSize=15
Burn1=NULL
Burn2=NULL
Burn3=NULL
Burn4=NULL
Burn5=NULL
Burn6=NULL
Burn7=NULL
Burn8=NULL
Burn9=NULL
Burn10=NULL
Burn11=NULL
Burn12=NULL
Burn13=NULL
Burn14=NULL
Burn15=NULL
[Pull]
PullWith=Melee
PullMeleeStick=0
MaxRadius=350
MaxZRange=50
UseWayPointZ=0
PullWait=5
PullRadiusToUse=90
PullRoleToggle=0
ChainPull=0
ChainPullHP=90
PullPause=30|2
PullLevel=0|0
PullArcWidth=0
PullOnReturn=0
[PullAdvanced]
PullLocsOn=0
[AFKTools]
AFKHelp=AFKGMAction=0 Off, 1 Pause Macro, 2 End Macro, 3 Unload MQ2, 4 Quit Game
AFKToolsOn=1
AFKGMAction=1
AFKPCRadius=500
CampOnDeath=0
ClickBacktoCamp=0
[KConditions]
ConOn=0
CondSize=5
Cond1=TRUE
Cond2=TRUE
Cond3=TRUE
Cond4=TRUE
Cond5=TRUE

[/CODE]

 

[Algar]

You may wish to check out MQs frame limiter if you have not done so (I can't speak to specific KA ini issues but it is often a fix when accounts have varying responsiveness levels).

https://www.redguides.com/community/threads/mqnext-framelimiter-demo.78448/

 

[ChatWithThisName]

It's important that you understand that frame limiter built into EQ actually slows down processing of information and frame limiter of MQ just doesn't draw the frames except every X interval.
You still want the one on EQ options to be set to background FPS/Foreground FPS to like 60, and then adjust whatever you want on the MQ frame limiter.
Having your EQ background FPS too low is 95% of the time the reason that characters act crazy in the background and EQ likes to have it at "minimal" which means as few frames as it can, but theirs is tied to processing of game information, which will make most character movement fail to react fast or correctly, keypresses to fail, characters to be laggy in general during movement in the background etc.

Another thing is if you're using Logs in EQ to parse DPS or something with an external program reading the log file, or just happen to have them on, you should back them up if you care to keep the information and restart the files every now and then. The bigger the file, the more info it needs to access, and the slower it goes. It can cause large spikes of lag when the log is written to. Alternately you can disable it all together. /log is the command, I'm not sure if it accept /log off, or if it's just a toggle.

Finally, kiss is a macro written with /delays in it. So there is some level of expected delay between actions or reactions because of the way the code is processed and waits for things. So if the above he been followed and addressed and there has not been a noticeable change, then it's possible that it's just the program going through the loop and it needs to get back to the part in the code that says to do what-ever it is you're expecting it to do.

 

[Granditos]

It's important that you understand that frame limiter built into EQ actually slows down processing of information and frame limiter of EQ just doesn't draw the frames except every X interval.
You still want the one on EQ options to be set to background FPS/Foreground FPS to like 60, and then adjust whatever you want on the MQ frame limiter.
Having your EQ background FPS too low is 95% of the time the reason that characters act crazy in the background and EQ likes to have it at "minimal" which means as few frames as it can, but theirs is tied to processing of game information, which will make most character movement fail to react fast or correctly, keypresses to fail, characters to be laggy in general during movement in the background etc.

Another thing is if you're using Logs in EQ to parse DPS or something with an external program reading the log file, or just happen to have them on, you should back them up if you care to keep the information and restart the files every now and then. The bigger the file, the more info it needs to access, and the slower it goes. It can cause large spikes of lag when the log is written to. Alternately you can disable it all together. /log is the command, I'm not sure if it accept /log off, or if it's just a toggle.

Finally, kiss is a macro written with /delays in it. So there is some level of expected delay between actions or reactions because of the way the code is processed and waits for things. So if the above he been followed and addressed and there has not been a noticeable change, then it's possible that it's just the program going through the loop and it needs to get back to the part in the code that says to do what-ever it is you're expecting it to do.

Oh man! 4 years and never new anything about min FPS in eq options. Everything is working SOOO much quicker. Must of missed that in initial set up notes.

THANK YOU

Edit: Placebo effect on me. The new frame limiter (circa 2021) doesn't need to adjust min background settings.

 

[Sic]

Oh man! 4 years and never new anything about min FPS in eq options. Everything is working SOOO much quicker. Must of missed that in initial set up notes.

THANK YOU

Framelimiter being used bypasses eq's in-game limiter.

If you're not using mq framelimiter you will want at least 30 for min background fps (like if you for some reason, are rawdogging eq without MQ)