Emulated mouse glitch

Well you got my money heh. I just bought a 1 year license to your tools. Really good work you have been doing. Look forward to multiboxing in D3 now.

Time to go set up more b.net accounts so I can run my other copies heh.

Yep looks like most of the issues are fixed -- no more issues with fullscreen/windowed and cursor disappearances

Still a problem when your main window is a different resolution than the others though -- not sending the repeated cursor to the proper position in their respective windows. Same thing with VideoFX and passthrough.

If I devide the screen evenly like Yelgis did, there's no problem since all the windows maintain the same resolution and aspect ratio.

[lax]

Still a problem when your main window is a different resolution than the others though -- not sending the repeated cursor to the proper position in their respective windows. Same thing with VideoFX and passthrough.

Check it out with IS dev build 5592.

Still a problem when your main window is a different resolution than the others though -- not sending the repeated cursor to the proper position in their respective windows. Same thing with VideoFX and passthrough.

Check it out with IS dev build 5592.

Checked and confirmed!!!! You have no idea how excited this makes me!!! Not to mention opens up a world of new options of in-game resyncing macros!!

Well done again! Can't give you enough props!

[lax]

Fantastic, thanks for confirming.

Glad to make everyone happy

[Mahther]

I know I'm a bit late but I wasn't able to box for a while. The cursor is working perfectly now for me as well. Thanks so much lax!

wow, im a super noob with isboxer..I seem to be having a problem with the mouse, I would click on a monster for a kill and my other char would just run off, Maybe its my settings or configuration..can anyone share their diablo 3 config? Im trying to box just 2 chars just to get the feel of it.

That means your characters weren't synced.

I just did a play through with a set of Barbs and it was pretty hard to keep them synced. Normally, I would just hold Shift and spam Cleave to clear trash. Big mobs got Clobbered with Bash "Clobber" rune. I made sure the chars were synced then would right click and hold on abig mob so the melee would lock on. That seemed to work.

Ranged classes are much easier cause once you sync all you really need to do is hold shift and spam your ranged attacks. You aren't as likely to get out of sync that way. Make sure all your characters have the same runspeed as well.

I haven't looked into ways to sync outside of manually doing it by running into corners or selecting each instance as needed and moving a single char at a time. So far with a ranged toon it is easy enough, but I will have to figure out something more robust for melee teams.

Unfortunately it seems like build 5596 has broken the cursor sync and scaled positions again.

Having the same issue I did before -- all of the slave windows' cursors and clicks are once again off-target.
Nothing about my configuration has changed between builds. The only way to get accurate repeating is to once again used a stacked config.

In addition, there seems to be a new issue that has not come up before:

If you tab or hotkey into one of your slave windows making it the active window, the cursor is now off-target even in fullscreen, FS windowed, or windowed modes within each slave game itself. In other words the cursor inside each scaled slave is off-target whether or not repeater is on.

EDIT for Clarification:
The (fake) emulated mouse cursor is appearing in the correct relative spot within each slave, but the actual position of the cursor is different from the fake cursor itself


I'll admit I only searched briefly, but I couldn't find a way to revert back to the older build. Is there an archive for older IS builds?

[lax]

Build 5597 (up as development build now) reverts the change that I believe broke this for you. Let me know.

I don't keep an archive of development builds, just builds that get pushed live. (I'd link the archive for you but it needs to be fixed since the lavishsoft.com site revamp.) A stable build (with Diablo 3 fully working) will be pushed in the next few days