Diablo 3, assumed bug.

[Mahther]

I'm not sure if this is a bug or just user error, but it does work about 10% of the time.

I made a couple simple key maps. These are intended for window and inventory management, picking up items, and re-stacking my characters. The first time I loaded it, it worked perfectly. After several attempts to see if I had done something wrong, Click1 would work but not Click2. Once, Click2 worked but not Click1. After many attempts, they both worked again, and stopped working again the next attempt. This leads me to believe it has to be a bug, maybe not even with isboxer since I'm using VMware for the second account.

Character sets: Diablo1, Diablo2
Characters: Diablo1, Diablo2
Key Maps: Click1, Click2

Isboxer toolkit profile: http://www.privatepaste.com/a6a7a6956d
HijackThis log: http://www.privatepaste.com/9d68161094

I just did some testing and am not able to duplicate the issue you mentioned, however I also do not have access to D3 accts, so I tested using another game. I also reviewed your profile and it looks like it should be functional. There is one thing I would like to mention. You do not need to create a new Key Map for every mapped key you create. In other words, you could have made a Key Map called Clicks, and within it created two Mapped Keys, one for click1, and the other for click2. You can think of the Key Maps as folders, and the Mapped Keys as Files. It's just a way to group similar actions together so you can include them in the character sets you like.

[lax]

1. I mentioned this in the Chat Room and you said you've got Repeater on the whole time anyway, but if Repeater was off you would need a Sync Cursor Action prior to sending Mouse1, in order to put the cursor in the same location in the other window.

2. Something you might not notice... your Hotkey may or may not work depending on the state of Num Lock. If Num Lock is on, your keyboard is sending 1, whereas if Num Lock is off it's End. If you happen to use the Num Lock key, you can easily get confused and see your hotkeys working some of the time but not others.

That's all that comes to mind at the moment

[Mahther]

Thanks for the tip Xeniaz. It's been so long since I used it in wow that I forgot everything.

I'll check the numlock thing lax. Currently installing VirtualBox to try and rule out the possibility that it was VMware so it'll be a bit but I'll post my results when it's done.

[Mahther]

Well, I found out that innerspace doesn't work with VirtualBox. Switched back to VMware and implemented Xeniaz's tip and the bug remains as expected. Went back to keymaps to mess with it some more and when I clicked the new one I made it would vanish and I would sometimes get the error below. I'm guessing I have a corrupt isboxer install, might be the cause of the bug too.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
at System.Windows.Forms.Control.DefWndProc(Message& m)
at System.Windows.Forms.TreeView.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5448 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
ISBoxer Toolkit
Assembly Version: 40.1.221.1
Win32 Version: 40.1.0221.1
CodeBase: file:///C:/Program%20Files%20(x86)/InnerSpace/ISBoxer%20Toolkit.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5453 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
vcyi7agk
Assembly Version: 40.1.221.1
Win32 Version: 2.0.50727.5453 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
r-ecwy3c
Assembly Version: 40.1.221.1
Win32 Version: 2.0.50727.5453 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
sxzptzf8
Assembly Version: 40.1.221.1
Win32 Version: 2.0.50727.5453 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------

[lax]

Don't click on your Mapped Keys in the top left pane. You edit an entire Key Map by selecting it in the top left pane, then edit a Mapped Key by selecting it in the bottom left pane.

Sometimes selecting a Mapped Key in the top left pane causes the exception you have pasted. Not a big deal, just click off the error and don't select it in the top left pane. It's there in the top left pane so that you can drag it somewhere to copy it or reference it

[Mahther]

lol, ok. I ended up scrapping everything and starting from scratch and still having the problem. There's nothing else I know how do. One more bug I wanted to tell you about tho. When I select mouse repeat enabled as a startup default under repeater profiles, the cursors go haywire after logging in. Pretty sure it's because it's trying to repeat both screens to each other.

[lax]

Yes, make sure to only enable mouse repeat FROM one of the PCs at a time