Having Issues with Gnome Sequencer and IS Boxer

[Outtie]

Was wondering if anyone has encountered this as well.
I recently installed Gnome Sequencer to clean up my bars and macros across the toons I box.
When I use GS as stand alone the GS macros work perfectly.
When I load IS Boxer and try the macro with Key Maps off it works perfectly.
But when I try it with Key Maps on the GS macros behaviour become erratic.
It wont cycle nicely through the macro and seems to skip steps that are active and available, often with a lot of delays in it trying to do any step at all.

Noticed a few users here are using both and appear to have it working so any suggestions would be amazing.

[mbox_bob]

Are you using mapped keys in ISBoxer to trigger the GS macros? ISboxer triggers it's own macros without issue, so there should be no reason why there are any issues triggering other non ISBoxer macros, and it does as it can trigger most peoples "roll yer own" macros.

So, leaves an interesting dilemma, in that there is something odd in the configuration of your macro, or there is something odd in your configuration of ISBoxer. The latter only really applies if you are trying to trigger your macro from an ISBoxer mapped key, or you happen to have double bound a hotkey for your in game macro to something that ISBoxer is sending for some other purpose.

In either case, it would be helpful to see your ISBoxer profile, and a macro definition or two.

http://www.isboxer.com/wiki/Configuration_Sharing

[Outtie]

This should be my IS Boxer profile http://pastebin.com/KV6Pt39e (never used pastebin before so I'm hoping this is done right)
This is an Elemental Shaman GS macro i use http://pastebin.com/wW36GWxS

Prior to using GS is just had a standard Key Map - Combat set of keys using F6-F12 which sends an assist and the key hit to each warcraft window.
I had F6 to F12 bound to an action bar in game and just cycle pressed those keys which contained either an in game macro or a spell.

The GS macro I use is really just a condensed version of what I had in the action bar.
For Eg
F6 = /castsequence reset=target/15 Flame Shock,a
F7 = Lava Burst
F8 = /castsequence reset=combat Lightning Bolt,Lightning Bolt,Lightning Bolt,Lightning Bolt,Earth Shock,Lightning Bolt,Lightning Bolt,Lightning Bolt,Earth Shock,Lightning Bolt,Flame Shock

So combining GS and IS Boxer I wanted to just spam F6 and have it cycle the GS macro on all windows.
As another angle of trouble shooting I tried this using Keyclone and it worked across all windows.
I also tries using a different Mapped Key in IS boxer to see if the key I was using was the issue but even with a different key the issue remained.

So it's probably something to do with my IS setup I'm going to guess.

[mbox_bob]

Well TBH, I know sweet FA about WoW and macros, but ISBoxer, I can help you with.

As you're not doing anything particularly fancy in ISBoxer or the macro from what I can tell, then I suggest you test your mapped key in ISBoxer without the Assist Me call in the mapped key. My suspicion is that your gnome sequencer macro is firing on every request, but because you are also getting your toons to retarget on every execution then sometimes they have a target, and sometimes they don't because it is in the middle of the process of updating (this is called Assist Delay http://isboxer.com/wiki/Assist_delay#Assist).

Ways to solve it would be:
1. Don't spam so hard.
2. Manage Assisting (targeting) and Combat separately
3. Use Stepped mapped keys in ISBoxer (tbf, this wont be quite as good as the way GS sets up the macro)

For the 3rd one, there are a few options to attempt to still have the Assist Me, but only have it execute the once at the beginning of your spam session, and then have it disable, and then reset to enabled once you stop spamming for a period of time. It might actually work not too bad doing that.

[Outtie]

I'll give that a go.
I was belting a target dummy with 3 warcrafts running so there wasn't any target switching.

I'll try deleting and redoing the F6-F12 mapped keys and see if that does anything.

Thanks for your time :)

[mbox_bob]

You might not be actually switching targets, but you are telling the [slave] game(s), to go find out what the other characters target is, and then update their targets to whatever the main has.

The slave game instances have no idea whether your mains target is still the same as it was 1 second ago, so they query the server (because they don't just talk amongst themselves locally). By the time they find out (receive data back from the server), they could check to see if it is the same as their existing target, or they could just update the target entity pointer. It shaves a few CPU cycles to just update it, and not bother checking if they are the same, so it does, but you will for a very short period, have no target (this period can be so small that the UI doesn't get an update + plus it is coded to not show the drop and reacquiring during a target pointer change).

And while that is all going on, your F6 keystroke is being processed, so sometimes it hits while your slaves have a target, and sometimes it does not because they are in the process of updating.

You don't need to delete all the mapped keys. Just select the F6 one, open up the steps and delete the first Action, which is "Do Assist Me in Non-Combat Key Map -> self".

[Outtie]

Will do, thanks again.

[Jabberie]

Have imported your sequence, it's working fine with the basic Assist+Broadcast keymap.
Been using GS with isboxer since it came out.

[Pazgaz]

Same here.
Been using GS (now GS-E) with isboxer for a long time.

[mbox_bob]

If that's the case, and it is working for you guys, then there must be some other issue, like strained H/W (FPS/CPU/etc), a different addon interfering, or some other software on the system.

Most of your character sets (8 out of 11) are using a Round Robin CPU strategy with 1 core. You should use the CPU Strategy Wizard and make sure you select the use all cores for all windows option (the last one on the drop down). This will improve performance for your character sets that are not set to use more than 1 core per game.

Disabling Addons I'll leave to you.

If we need to look further, then the diagnostic instructions are here... http://isboxer.com/wiki/Diagnostics

[Outtie]

Noticed something else today and what I'm hoping has fixed the issue albeit not convincingly.

Prior to installing GS I used to run a programmed mouse button that pressed F6-F12 in a step fashion while I held the button down.
When I installed GS cause I could put everything onto one action bar slot I changed this to just hit F6 over and over while I held the button down, delay of about 150ms between hits.
This is where I started having the performance issues.
For some reason switching back to the old F6-F12 spam corrected the performance issue, even though F6 was the only slot with a macro in it, why I don't fully know.
I then changed the mouse button to spam F6 four times (four was just a random test number) before delay and this seems to work for now too.

Seems messy and an unreliable fix and if it breaks again I'll report back here to let you know how I've gone.
As you suggested Bob, I'm thinking it might be hardware strain.

Thanks again for your time folks.

[Jabberie]

Noticed something else today and what I'm hoping has fixed the issue albeit not convincingly.

Prior to installing GS I used to run a programmed mouse button that pressed F6-F12 in a step fashion while I held the button down.
When I installed GS cause I could put everything onto one action bar slot I changed this to just hit F6 over and over while I held the button down, delay of about 150ms between hits.
This is where I started having the performance issues.
For some reason switching back to the old F6-F12 spam corrected the performance issue, even though F6 was the only slot with a macro in it, why I don't fully know.
I then changed the mouse button to spam F6 four times (four was just a random test number) before delay and this seems to work for now too.

Seems messy and an unreliable fix and if it breaks again I'll report back here to let you know how I've gone.
As you suggested Bob, I'm thinking it might be hardware strain.

Thanks again for your time folks.

I've mine on E with a 50ms repeater and isboxer set to up and down key. :)
I use All CPUs to all clients so they all have enough power to keep up I guess.

[Jabberie]

Same here.
Been using GS (now GS-E) with isboxer for a long time.

Thanks, did not know it went to E. I had seen the changes to the scripts but thought it was just for notation in the sequences file.

[Ughmahedhurtz]

Noticed something else today and what I'm hoping has fixed the issue albeit not convincingly.

Prior to installing GS I used to run a programmed mouse button that pressed F6-F12 in a step fashion while I held the button down.
When I installed GS cause I could put everything onto one action bar slot I changed this to just hit F6 over and over while I held the button down, delay of about 150ms between hits.
This is where I started having the performance issues.
For some reason switching back to the old F6-F12 spam corrected the performance issue, even though F6 was the only slot with a macro in it, why I don't fully know.
I then changed the mouse button to spam F6 four times (four was just a random test number) before delay and this seems to work for now too.

Seems messy and an unreliable fix and if it breaks again I'll report back here to let you know how I've gone.
As you suggested Bob, I'm thinking it might be hardware strain.

Thanks again for your time folks.

There is an input limit (max number of inputs/macro steps/keys) that can fire per second. It's pretty high but your device needs to be somewhat careful with how it spams keys. I know people use gamepads that do what you are talking about and they work, but if you get too many things going at once, things Get Wierd(tm).

[luxlunae]

yeah 50-150ms sounds wayyyy too fast for repeaters to be firing safely.

[Outtie]

yeah 50-150ms sounds wayyyy too fast for repeaters to be firing safely.

I've pushed the limits on this a few times using even no delay in between presses and with no delay my game just crashes out completely.
Adversely too long a delay and the macro or sequence you're trying to fire becomes less optimal.
In my initial problem I tried just tapping the key manually with probably a half second delay and it still 'broke'.
To be completely honest I am surprised that the fix, for lack of better wording, was to speed things up a little.

[MadMilitia]

It's just a timing issue with GS. It would help to see your GS macros though to know for sure.

For example if you have a lot of castsequences and they have timer resets in them they could be resetting before being hit again. The reset starts ticking internally in the wow macro from the first time GS evokes it. Even though on our side it looks like an action is happening every 1/5th a second it's actually only happening once a second if there are a lot of steps in GS happening.

The more steps in your macros the more often you want to press the key per second.

Edit: I see your GS rotation now. Looking at it.

Edit2: Ok, you've got too much going on in your main sequence. From what I can tell if your combat is resetting a lot your big rotation / malestrom stuff isn't popping asap. Rather, it's walled behind a lot of lightning bolts before anything happens.

That could be giving you the impression it isn't doing much.

Try this. I'm curious to see how it works.

Talents: 1,2,2,3,1,3,2


Sequences['ELE-ST'] = {PreMacro = [[
]],
'/cast Stormkeeper',
'/cast Fire Elemental',
'/castsequence [nochanneling] reset=target Flame Shock, Lightning Bolt, Lightning Bolt, Lightning Bolt',
'/castsequence [nochanneling] reset=target Lava Burst, Lava Burst, Lava Burst, Earth Shock',
'/castsequence [nochanneling] reset=target Lava Burst, Lava Burst, Lava Burst, Earth Shock',
'/castsequence [nochanneling] reset=target Lava Burst, Lava Burst, Lava Burst, Earth Shock',
PostMacro = [[
/startattack
/use [combat]13
]]
}

It emphasises lava burst like yours but I think it puts a little more emphasis on Earth Shock than yours does. Also keeps a constant Flame Shock rotation instead of once every target ( 15 means nothing if you hit the button again ).

[Outtie]

The GS Macro itself ran fine with a single instance of wow running and applied Flame Shock at the end of the big sequence, the '15' reset condition in the first sequence doesn't need to be in there to be honest, it was more as I was testing on a dummy and being lazy not re-targetting.

The Earth Shock getting full value out of Maelstrom charges is where mine does fall down a little normally going off between 60-90 Maelstrom and very rarely at 100.

The GS macro only 'appeared to not do much' as soon as I got IS Boxer involved and started sending to multiple wow instances, other than that it ran quite well.

Gave your GS macro a go, found it would re apply Flame Shock too often, in some cases Flame Shock still had 30 seconds left on it's duration. Tweaking might make this more efficient.
Side by side though with my macro they both seemed to do similar dps over a 5 min period with no cooldown use.

[MadMilitia]

The GS Macro itself ran fine with a single instance of wow running and applied Flame Shock at the end of the big sequence, the '15' reset condition in the first sequence doesn't need to be in there to be honest, it was more as I was testing on a dummy and being lazy not re-targetting.

The Earth Shock getting full value out of Maelstrom charges is where mine does fall down a little normally going off between 60-90 Maelstrom and very rarely at 100.

The GS macro only 'appeared to not do much' as soon as I got IS Boxer involved and started sending to multiple wow instances, other than that it ran quite well.

Gave your GS macro a go, found it would re apply Flame Shock too often, in some cases Flame Shock still had 30 seconds left on it's duration. Tweaking might make this more efficient.
Side by side though with my macro they both seemed to do similar dps over a 5 min period with no cooldown use.


Ok so the GS macro wasn't the problem. Maybe your key mapping is throttling it somehow? Mine are generally 1 to 1. One key press travels down to one evocation of the Masterkey which is a switch for DPS-ST or DPS-AE which respectively call the WoW named macro for their type. I'm not doing something like mentioned earlier with many steps in a mapped key.

[Ughmahedhurtz]

Putting the key on a "pressed or released" mapped key will double the firing rate versus not using IS.

[MadMilitia]

Putting the key on a "pressed or released" mapped key will double the firing rate versus not using IS.


Yeah that's a good point. Lots of ways this could be mapped in IS that could affect the firing rate.

[ffxireti]

Tried to PM, but won't seem to let me. I'm new to ISboxer and multiboxing in general. Spent the last few days learning Isboxer and ran into GSE. Would it be possible to see your profiles for Isboxer? I understand if your not willing to share. I figured I'd ask. This is towards Pazgaz and Jabberwock or MadMilitia if hes willing to share aswell.

[Pazgaz]

My isb profile is not really interesting since it's using the "pro" system which means there's nothing in isboxer besides virtual key maps that do nothing. I use gs-e and that's where all the macros are.
During WoD I played with gs macros + isb and used the macro keys on the g710+ to repeat the key presses every 50ms or so. worked fine... not sure if it was super optimized, but in tanaan things melted. :)

[ffxireti]

I would still like to get my hands on one of your profiles. Its alot easier for me reverse engineer a profile I know that works than going through countless post, threads and wiki pages trying to get ISboxer to work correctly with it. Are you using custom GS-E macros or something found on their site? Thanks for reply.

[MadMilitia]

I would still like to get my hands on one of your profiles. Its alot easier for me reverse engineer a profile I know that works than going through countless post, threads and wiki pages trying to get ISboxer to work correctly with it. Are you using custom GS-E macros or something found on their site? Thanks for reply.


My GS sequences are wildly out of date beyond MW, BM/MM and PROT. I haven't spent much time with others, besides the ele shaman ones I posted earlier.

I tried pasting my IS profile awhile back but pastebin has a 512kb limit on guest submissions =/. I need to make an account for that. I'm also working on an annoying configuration problem that I haven't gotten past yet. But I can explain it some I think this way.

1. Game Helpers > World of Warcraft is where you want all of your wow / GS macros. Live by this rule. It will make your time using ISBoxer much better.
2. The GS macros should all be called from these WoW macros you create.
3. Make new macro sets under Game Helpers > World of Warcraft that make sense to look at. Ex: DPS, Survival, Healing, etc.
4. Action target groups are essential for some things. Same rule applies here. You will want both roles ( ranged, tank, healer ) and classes and/or specializations. You can for example send a WoW macro from what I mentioned earlier to a subset of characters identified by an action target group.

Example of a macro in Game Helpers > World of Warcraft > Macro Sets > DPS ( won't exist you will need to create it ):

Right-click the new DPS Macroset and choose new Wow Macro > Name it DPS-ST ( single target ):



!if (character is in "Shaman" ) /click ELE-ST
!if (character is in "Warrior") /click PROT-ST
!if (character is in "Hunter") /click MM-ST
!if (character is in "Deathknight") /click BLOOD-ST


Keybind: ctrl + shift + 2

What you're looking at here is a combination of GS with action target groups. For every character using this named macro, their respective ATG (action target group) is used to identify which click of GS they get. When this is sent to the WoW client the appropriate macro is applied. Then whatever key combination you setup for the macro ( WoW named macros must always have a key combination if being used ) works to evoke the macro in game.

The next thing is simply setting up how you want the DPS-ST wow named macro called. You could create a DPS Masterkey ( named something along those lines ) in the combat keymap. Then have all your guys or some of your guys ( using ATGs ) use the WoW named macro. Create a new mapped key in combat and call it DPS Masterkey. Then in the step create a new action:

Right click Actions > Keystroke Actions > Named World of Warcraft Macro Action. Choose appropriate target and then select the DPS-ST macro from the WoW Macro Set: DPS and WoW Macro: DPS-ST.

Then it's just a matter of assigning a key you'll press to the DPS Masterkey. Try that out.

Oh and if you want my GS macros for MM, MW and PROT let me know. I also have a blood dk macro and an ele one posted a bit back and of course the BM macros.

[ffxireti]

I'll take a look at your GS macros. Thanks for explaing I'll give it a whirl see if I can get it to work. Also you could just dropbox or onedrive for profile if you wanted to. If you happen to upload it let me know I'll take a look and make sure I have everything configured correctly. Thanks for replying! Heck I'll send you my email address in PM incase you didn't want to do that.

[MadMilitia]

Profile still has issue. I won't have time to get to it for a bit as I've been busy with work.

Though these are the profiles you might want to try. Note: Some are still work in progress but I guess something is better than nothing!

PROT WAR - 2 macros



Sequences['PROT-ST'] = {StepFunction = [[
limit = limit or 1
if step == limit then
limit = limit % #macros + 1
step = 1
else
step = step % #macros + 1
end
]],
PreMacro = [[
/targetenemy [noharm][dead]
]],
'/cast [combat] Victory Rush',
'/castsequence reset=target Intercept, null',
'/castsequence [combat] Focused Rage, Shield Block, Shield Slam',
'/castsequence Shield Slam, Thunder Clap',
'/cast Revenge',
'/cast Devastate',
PostMacro = [[
/startattack
/cast [combat]13
/cast [combat] Battle Cry
]],
}




Sequences['PROT-SV'] = {
StepFunction = [[
limit = limit or 1
if step == limit then
limit = limit % #macros + 1
step = 1
else
step = step % #macros + 1
end
]],
PreMacro = [[
/targetenemy [noharm][dead]
]],
'/cast [combat] Victory Rush',
'/castsequence reset=target Intercept, null',
'/castsequence [combat] Shield Block, Shield Slam, Ignore Pain',
'/castsequence Shield Slam, Thunder Clap',
'/cast Revenge',
'/cast Devastate',
PostMacro = [[
/startattack
/cast [combat]13
/cast [combat] Last Stand
/cast [combat] Battle Cry
]],
}

BLOOD DK


Sequences['BLOOD-ST'] = {
StepFunction = [[
limit = limit or 1
if step == limit then
limit = limit % #macros + 1
step = 1
else
step = step % #macros + 1
end
]],
PreMacro = [[


]],
"/castsequence reset=target Death Grip, null",
"/castsequence reset=target Dark Command, null",
"/cast Death Strike",
"/cast Consumption",
"/castsequence reset=combat Marrowrend, Heart Strike, Heart Strike, Heart Strike",
"/cast [combat] Blood Boil",
PostMacro = [[
/cast [combat] Dancing Rune Weapon
/cast [combat] Vampiric Blood
]],
}



For Marksman I use Nano's lazy macros. See here: https://wowlazymacros.com/forums/topic/gs-e-mm-sidewinders-2/

[Outtie]

1740

I've attached the GS-E macros I've created over the last couple of days.
My friend and I have used these in our mythic dungeon groups with varying levels of success in relation to ilvl etc.
Class and Spec included.
Elemental Shaman ST and AOE
Frost Mage ST
Destruction Warlock ST
Discipline Priest ST (use as a damage dealer with passive atonement heals, quite fun until mana runs out)
Blood DK ST
Ret Pally ST and AOE
Guardian Druid ST
Brew Monk ST
Marks Hunter ST (this one blows stuff up)
Prot Warrior ST (get 1 piece of leech gear and you'll nearly never die)

These are designed to be spammed with about 100ms delay between hitting the key again.
Just extract the "Outtie Pack" into your addon folder and it should work from there.

Let me know how these go if you get around to using them.