Question - Kissassist Issue

[thx07781]

Hey all,

I am having a problem with Kissassist crashing on zoning. The wierd part about this is it only happens on 2 out of 3 of my computers. I currently run 3 computer. My main computer which runs 4 toons has no problem, it's my other 2 computers that have the issue. The issue at hand is whenever I zone I get an echo in the MQ window-

[MQ2]JustZoned
[MQ2]JustZoned
The current macro has ended.
/varset failed, variable 'JustZoned' not found
/varset failed, variable 'JustZoned' not found

This is on my cleric's computer. Now on my Bard's computer I get the same message but only once-

[MQ2]JustZoned
The current macro has ended.
/varset failed, variable 'JustZoned' not found


I will admit that I have had this problem for awhile, roughly a month or so and I have just been lazy to report it. I have tried to debug the issue myself but frankily I am stumped.
Any ideas? Also is there any other info you need?

Thanks

 

[Maskoi]

how slow are the other 2 computers?

 

[dencelle]

i've notice the "/varset failed, variable 'JustZoned' not found" warning happening a lot on my comp but only when i'm running 5-6 instances of eq at the same time (4gig ddr3 ram with a AMD E1-1200 processor) if i'm only running 3 instances of eq though its fine... so my suspision has always been lag (the true root of all evil!) and noticed also my labtop (significantly slower computer and probably shouldn't be running eq at all on it but wth why not....) has the same issue if running 2 or more instances... yet again... i root down to lag... and as much as i REALLY want to blame maskoi (like everything else i blame him for)... its just your computer from what i can tell thx07781... my best suggestion... ignore the errors...

 

[Maskoi]

Around line 2873ish find the line below

        /delay 10s ${Me.ID}

and change it to

        /delay 60s ${Me.ID}

See if that works

 

[dencelle]

thats not the issue.... the issue is the computer its self... its deleting all the variables, sending the "ended macro" thing then stopping the macro... sometimes on slower computers it will overlap and cause the macro to send lines after the variables have already been deleted... this causes those errors to send..