Printable View
I've been dual-boxing on one com today, and i had the disconnect problem when i was running wow maximised, so i could only see one at a time.
But when i downsized my windows a little and was able to see one window at about 80% of the screen, and the other window behind it at the same time, i didnt have a single disconnect.
Dunno if its a coincidence, but maybe worth a try for people with the problem.
As I said in my previous posts, unfortunatly even with the clone window minimized I still had the disconnects. Still, it pretty much works now so I'm happy enough. Hopefully Blizzard will release the proper fix for next patch, or sooner!
Just thought you should know, I've experienced it again yesterday. When i had both windows maximised and therefore could see only one of them at a time, I had a DC on my clone window, meaning the one i wasnt playing.
But when i resized them a bit, so I was able to see both my windows at the same time, i didnt have any DC's for a 3 hour session of playing.
It's almost like windows forgets about my second wow window, when i cant see it.
Windows: "If a wow window cant be seen then should it exist? I think NOT!"
Anyway, I cant be the only person where that is the solution, so I hope it helps someone else.
This fixed it for me thanks a ton :wink:Quote:
Originally Posted by loonitoons
the bug seems to be fixed btw ;)
it seems so. /happy
I haven't seen this bug since the patch. Kept /follow on blimps/UC elevator/needles lifts/boats and haven't been d/c'ed at all since.
/cheer
modify your script to something like
[code:1]
; *******************
; *** WASD ***
; *******************
#IfWinActive, World of Warcraft
w::
ControlSend,,{w down}, ahk_id %idMain%
ControlSend,,{= down}, ahk_id %idClone%
ControlSend,,{w down}, ahk_id %idClone%
return
w up::
ControlSend,,{w up}, ahk_id %idMain%
ControlSend,,{= up}, ahk_id %idClone%
ControlSend,,{w up}, ahk_id %idClone%
return
a::
ControlSend,,{a down}, ahk_id %idMain%
ControlSend,,{= down}, ahk_id %idClone%
ControlSend,,{a down}, ahk_id %idClone%
return
a up::
ControlSend,,{a up}, ahk_id %idMain%
ControlSend,,{= up}, ahk_id %idClone%
ControlSend,,{a up}, ahk_id %idClone%
return
s::
ControlSend,,{s down}, ahk_id %idMain%
ControlSend,,{= down}, ahk_id %idClone%
ControlSend,,{s down}, ahk_id %idClone%
return
s up::
ControlSend,,{s up}, ahk_id %idMain%
ControlSend,,{= up}, ahk_id %idClone%
ControlSend,,{s up}, ahk_id %idClone%
return
d::
ControlSend,,{d down}, ahk_id %idMain%
ControlSend,,{= down}, ahk_id %idClone%
ControlSend,,{d down}, ahk_id %idClone%
return
d up::
ControlSend,,{d up}, ahk_id %idMain%
ControlSend,,{= up}, ahk_id %idClone%
ControlSend,,{d up}, ahk_id %idClone%
return [/code:1]
you don't want the ~ if you are explicitly sending the control to your main... ~ tells AHK to not block the key press to the current focus so you would end up with 2x w
btw what is the = being sent for? is this a straight copy of Sorn's script?
if so do you want a slightly improved version of the instance identification code? (not all my work)
@zaza
looks like a mod of Sorn's script ;) that is how I started too ;)
1. quick tip... #IfWinActive affects all subsequent lines of code in the script... you don't need it before every hotkey. I find getting rid of it all over the place makes the script much easier to read.
2. ~ is used to tell ahk not to block the keypress from the system... so if you have ~w:: which is also sending w to your main, then you will end up with 2x w... not too much impact while playing but a real pain when typing.
Indeed it is a mod of Sorn's script! :wink:
I would really like to see the improved version for sure, would be much appreciated.
As for the '=' it is sent because in Sorn's script you're told to bind '=' to a '/assist #main#' macro, which makes sure that thing's are always being cast on the correct targets.