DAoC dual-boxing

[PyrostasisTDK]

upgraded the program, and still having the issue... just noticed its not just main client but both clients are turning, also changed sendwinmf to SendWinBackgroundDAOC still same issue.

Changed the hot key for mouse look to left mouse button, still turning.

SOOOLVED!

Ok had an idea, maybe its cause both clients had mouse look on? Killed mouse look on second client, and problems solved. I am also running both clients off the same DAOC directory... so might be the issue.

Problem seems to be when BOTH clients have mouse look as the same key, it does rotations, might be due to same dir.

[PyrostasisTDK]

new issue. Anytime a command is sent to an alt account in motion (assist) it breaks stick. Going to copy daoc to a separate directory and see if that fixes it.

[PyrostasisTDK]

Ok two different installs, sending assist while on the move still breaks stick as does any key (timer buffs etc). It doesnt break on second pc, so I believe it has something to do with the focus change, apparently thats breaking stick some how.

Also tried setting the affinity to split on the cores of my dual core, same issue.

[Ryjara]

Hi there I also started using the HotKeyNet program. It's very nice and seems to work really well.

I also play Dark Age of Camelot and have 5 machines. I use Synergy to link the screens. My plan was to have 2 clerics on my main machine, which works great with HotKeyNet, as I can get them to heal and assist my targets with the hotkeys.

I have 2 scouts on another machine, but when I mouse over to that computer (with Synergy), pressing the hotkey doesn't work. I have to physically press the hotkey on the keyboard for the 2nd machine.

I got around this issue by using the Server/Client and then it was okay. The only thing is now is to do a repeat/loop of the command I want them to. >.<

I tried using AutoHotKey to make a loop, but it doesn't make the keypress to activate the HKN key.

Otherwise great work on the program so far :thumbup:

[Freddie]

SOOOLVED!

Ok had an idea, maybe its cause both clients had mouse look on? Killed mouse look on second client, and problems solved..

I'm glad you discovered this, but I'd call it a work-around, not a solution. But let's put this aside for now and focus on the new problem, because the two things sound like they could be related (both seem to involve movement commands that should not be arriving).

new issue. Anytime a command is sent to an alt account in motion (assist) it breaks stick. Going to copy daoc to a separate directory and see if that fixes it.

Is the foreground toon driving when this happens? If so, this is probably an example of the need to adjust the timing for SendWinMF and SendWinBackgroundDAOC.

Here's how we can diagnose the problem: Drive on autorun (default key is numlock I think) instead of holding a key down. Now, while you are not pressing any other key, press the hotkey. Does the toon still lose /stick?

[PyrostasisTDK]

Nice catch, no it only loses stick when Im walking forward with W pressed and hit assist key.

To clarify. Driving with Main, stuck with Secondclient. Holding down W and moving towards a target Main has targeted. Hit assist key, Secondclient stops moving and assists.

Driving with main, stuck with secondclient. Using autorun no key pressed and moving towards a target main has targeted. Hit assistkey, secondclient stays stuck and assists.

[Freddie]

Hi there I also started using the HotKeyNet program. It's very nice and seems to work really well.

Glad to hear it. Thanks a lot.

I have 2 scouts on another machine, but when I mouse over to that computer (with Synergy), pressing the hotkey doesn't work. I have to physically press the hotkey on the keyboard for the 2nd machine.

I just made a new build for you (number 55) that may solve the problem. If not, please let me know.

I got around this issue by using the Server/Client and then it was okay.

I'm sorry, I don't understand this. Does "server/client" refer to Synergy or HotkeyNet? With HotkeyNet, every machine can do the same things regardless of whether they are clients or servers.

The only thing is now is to do a repeat/loop of the command I want them to. >.<

Is this something you're planning to do with Synergy, or are you saying you'd like to see it added to HotkeyNet? As far as HotkeyNet goes, I don't have any immediate plans to add this sort of thing.

I tried using AutoHotKey to make a loop, but it doesn't make the keypress to activate the HKN key.

This may work with build 55. (If it does, I'll be amazed that you can stack three programs like this on top of each other and get something useful out of them. )

Otherwise great work on the program so far :thumbup:

Thanks a lot.

[PyrostasisTDK]

Ok fred Im a bit confused, I assume my testing proved something about the timing, but Im not sure what or how to fix, can you elaborate?>

[Freddie]

Ok fred Im a bit confused, I assume my testing proved something about the timing, but Im not sure what or how to fix, can you elaborate?>

Give me a minute, I'm in the middle of writing a novel for you.

P.S. I liked the first version better.

[Freddie]

[quote='PyrostasisTDK',index.php?page=Thread&postID =32901#post32901]Nice catch, no it only loses stick when Im walking forward with W pressed and hit assist key.[/quote]
Thanks. Let me explain what's happening and what I'm doing about it. (By the way, your description was terrific. Absolutely clear.)

The toon's stick is breaking because his copy of DAOC thinks the person who's playing him hit the "go forward" key on his keyboard. Why does DAOC think that? Because the keypresses you're generating by holding down the W key, which are supposed to go only to the foreground window, are "leaking" into the background window.

Why are they leaking? Because HotkeyNet is doing unnatural things with keystrokes in an effort to manipulate DAOC into accepting keystrokes while its in the background, which is something it was deliberately designed not to do. It's not surprising that this doesn't work perfectly.

What can I do to stop the leaking? Well, for the past week I've had two ideas about this. One idea was to insert some delays in the SendWinMF code. The second idea was to add a buffer for keyboard keystrokes so they don't get sent until after HotkeyNet's unnatural tricks are finished. I decided to implement these ideas one at a time so we can test them and see how well they work.

I started implementing the first idea (the delays) last week. I've changed the implementation of them several times now. In the current build (55) you adjust them with this command:

[url='http://www.hotkeynet.com/ref/setfocusdelay.html']<SetFocusDelay 0 15>[/url]

If you make the second number lower, you'll get less leakage. Unfortunately, there's a tradeoff. As the second number gets lower, the desirable keystrokes (the ones from the macro) are also less likely to get through.

In other words, as you make that number lower, the W's are less likely to get through to the background window, but the keystrokes in the word "/assist" are also less likely to get through.

The question I've been waiting for the testers to answer is: Can you make that second number low enough that leakage stops 100%, but the desirable keystrokes stlil get through?

As soon as I've received a few answers to this question from testers, I'll move on to the second part of the solution, the keystroke buffer, which will (I hope) make these functions work even better.