Anyone else have this same problem?

[saltyclappers]

It seems that when I press unequip and then tab immediately afterwards it re-equips my weapon. It only seems to happen if I press them extremely close together... if I slow it down a little it seems to work fine. So, during a fight ill try to unequip, tab, and then drop a spell... but, it re-equips my weapon and causes me to fizzle. Annoying as hell... messes up the timer sometimes too.

When it does do the reequip I get the "Finished 2 queued actions in... " system message on the bottom corner. I have my equip/unequip go through Razor (Arm/Disarm Left Hand), if I try setting it up in UO the problem is even worse... you have to unequip and wait even longer to tab.

Ive tried this on 3 different computers and the problem is the same each time. Is the only solution to make certain the buttons are pressed with more of a delay. Or, is there some setting that should be changed? Or is the Arm/Disarm in Razor not recommended for equip/unequip?

Any ideas?

[uofuntime]

It seems that when I press unequip and then tab immediately afterwards it re-equips my weapon. It only seems to happen if I press them extremely close together... if I slow it down a little it seems to work fine. So, during a fight ill try to unequip, tab, and then drop a spell... but, it re-equips my weapon and causes me to fizzle. Annoying as hell... messes up the timer sometimes too.

When it does do the reequip I get the "Finished 2 queued actions in... " system message on the bottom corner. I have my equip/unequip go through Razor (Arm/Disarm Left Hand), if I try setting it up in UO the problem is even worse... you have to unequip and wait even longer to tab.

Ive tried this on 3 different computers and the problem is the same each time. Is the only solution to make certain the buttons are pressed with more of a delay. Or, is there some setting that should be changed? Or is the Arm/Disarm in Razor not recommended for equip/unequip?

Any ideas?

Hmm I think I have an idea of your problem... and I think it's fixable. You have to uncheck "auto-queue object delay actions" in razor or something. Or lower it. I could be totally off.