Master Stutter with input

Hey guys, I've checked around but i couldnt find anything on this.

I run a 4 box at the moment, 2 monitors first being primary and having one main character on it, and the second having the other 3. Everytime I press any key that broadcasts to the others it stutter lags. I have tried it a number of ways including putting them all in a 2x2 square on either monitor, all stacked, 3 hidden, nothing helped it work out. I played around on it and if the key is spammed my framrate drops DRASTICALLY, i mean if i keep spamming an input it will drop all the way down to the single digit framerates. Everything is on Low Settings ATM (definitely don't need them there) and I have run it with all of the different CPU setting to no avail as well. Im stumped...

Anyone have any ideas?

Thanks,
Nick

[bob]

First, share your profile - http://www.isboxer.com/forum/viewtopic.php?f=22&t=13
Second, provide a diagnostic - http://isboxer.com/wiki/Diagnostics (although you can get a diagnostic from a game launched under Inner Space, rather than outside of it).
Third, make sure you are using the No Master Slot, select No CPU's (this means leave it up to Windows to sort it out).

CPUStrategy.png (34.65 KiB) Viewed 8945 times

Fourth, check out http://www.isboxer.com/wiki/HOWTO:Tweak ... ottlenecks

Config: http://www.privatepaste.com/d007959533
Diagnostic: http://www.privatepaste.com/68aab9a227

Ive tried the no slot on master with no CPUs selected to let windows work it out. Still didnt work.

I checked out the bottle neck site a little while ago, before I posted. I didnt see anything that stood out.

Thanks for the quick reply!
Nick

EDIT: I might add that it is ONLY the master slot that is stuttering. The slaves seem just fine.

[bob]

There are several things to try.

First, Fix your mapped keys so they don't repeat themselves and run a shitload of things all at the same time.
e.g. when you press NUM2 it runs:
- 1. Do Mapped Key Assist Me in Non Combat
- 2. Num2 to all
- 3. Do Mapped Key Melee IWT in Combat

Melee IWT runs
- 1. Do Mapped Key Assist Me in Non Combat
- 2. ALT+T to all other.

A couple of repeats in there. If you really want your mapped keys to all run IWT, then instead of them calling Assist Me in non Combat (the first one), then get them to call "Interact With Target" in Non-Combat and drop the call to Melee IWT. This kind of makes more sense anyway, as you would usually want them to call IWT before you send them a command to do actual melee. Doing it afterwards is just weird.

It's worse when you press NUM1 because it also runs a second mapped key in the Always On key map, which does the same thing as the mapped key in Combat, so it gets the above twice, and all at the same time.

Second, Remove the App Compatibility from WOW

Code:

Application Compatibility flags under HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers:
0 C:\Program Files (x86)\World of Warcraft\Wow.exe: ~ WIN7RTM
0 C:\Program Files (x86)\World of Warcraft\Wow-64.exe: ~ RUNASADMIN


Third, Try uninstalling or shutting down various other pieces of software.
Personally I'd start with Avast, as AV is a common culprit (and requires uninstalling to fully test), then the overlay software. The list below is my hitlist

Code:

7. AvastSvc.exe - Process ID: 1188 (C:\Program Files\AVAST Software\Avast\AvastSvc.exe) [Admin:NO] [x86] [10.2.2214.845] [Avast Software s.r.o.] [avast! Service]
8. avastui.exe - Process ID: 4744 (C:\program files\AVAST Software\Avast\avastui.exe) [Admin:NO] [x86] [10.2.2214.866] [Avast Software s.r.o.] [avast! Antivirus]
9. avastui.exe - Process ID: 5228 (C:\program files\AVAST Software\Avast\avastui.exe) [Admin:NO] [x86] [10.2.2214.866] [Avast Software s.r.o.] [avast! Antivirus]
31. GameScannerService.exe - Process ID: 2556 (C:\Program Files (x86)\Razer\Razer Services\GSS\GameScannerService.exe) [Admin:NO] [x86] [1.0.6.2606] [GameScannerService]
39. RzOvlMon.exe - Process ID: 2696 (C:\Program Files (x86)\Razer\Core\64bit\rzovlmon.exe) [Admin:NO] [x64] [1.0.1.66] [Razer, Inc.] [Monitor Razer Overlay Driver Service]


Fourth, run wow in 32bit rather than 64. WOW will auto launch in 64bit if you let it, but you can set in the game profile http://www.isboxer.com/wiki/Game_Profile the "-noautolaunch64bit" parameter, or you can delete or rename wow-64.exe (although if you let WOW patch, it will reinstate this file so you have to keep up).

Finally, if it's still happening provide some more detail on your PC.

edit: Forgot to add, you might have an Addon which is causing the grief too. Disable them except for the ISBoxer addon.

having the same issues here i think.
But it seem i got a way to bypass it.for now.
Starting up battle.net launcher start up my main account and login.
then i start my multibox using innerspace and login all and dc my main with the new launched wow.
And no stutter there.

But i also found a few time when an alt account got dc or what so ever and i restart a single wow it also got the stutter illness. and i need to use the bnet launcher to login that char and load my multibox aggain to remove stutter from the alt client.

this is for now the only solution i have found to get it working.

tried al the master/nomaster /cpu/no cpu settings/ new keymaps/new folders/delete interface and wtf folders and what so ever.