Innerspace Windowsnapper, Repeater, and a little extra sumptin sumptin

Heading to bed now, but have almost ironed out my multi.iss for having 3, 4 or 5 clients lined up the right of the screen and the Snap To window on the large left section. The only problem I have is setting the windowsize -viewable parameters. I can't get the syntax write to make the size (1920-nXsize)x1200...

Code:

function main(int clients) { while ${Sessions} < ${clients} - 1 waitframe variable int nSession nSession:Set["${Session.Right[-2]}"] variable int nXsize variable int nYsize variable int nXpos variable int nYpos variable int nVertSplit nVertSplit:Set["${Sessions}+1"] nXsize:Set["1920/${nVertSplit}"] nYsize:Set["1200/${nVertSplit}"] nXpos:Set["1920-${Xsize}"] nYpos:Set["(${nSession}-1)*${nYsize}"] run windowsnapper -pos ${nXpos},${nYpos} -size ${nXsize}x${nYsize} windowpos -viewable 0,0 windowsize -viewable ${nXpos}x1200

Thats what I've got... everything else works fine if I put a value in for windowsize -viewable but I can't get it to work with a variable parameter. As you can probably tell, I have never coded before :P

You just have a typo

Code:

nXpos:Set["1920-${Xsize}"]

should be

Code:

nXpos:Set["1920-${nXsize}"]

the variable is nXsize. :)

Also, ${clients} is equal to ${Sessions}+1 (it holds the number you gave originally, the number of clients that should be open at the time this code is run, by Zanthor's design). You can make the script work for any resolution by changing your hard-coded 1900 and 1200 values to ${Display.Width} and ${Display.Height}, and work on multiple monitors by adding ${Display.DesktopX} and ${Display.DesktopY} to the X,Y position -- so if you change your configuration later or if someone else wants to use the same script, they can.

So, here is my recommendation for you and people who want your exact layout:

Code:

function main(int clients) { while ${Sessions} < ${clients} - 1 waitframe variable int nSession nSession:Set["${Session.Right[-2]}"] variable int nXsize variable int nYsize variable int nXpos variable int nYpos variable int nVertSplit nVertSplit:Set["${clients}"] /* with less than 5 clients, the pip windows will be pretty big, so set this to 5 minimum */ if ${nVertSplit}<5 nVertSplit:Set["5"] nXsize:Set["${Display.Height}/${nVertSplit}"] nYsize:Set["${Display.Width}/${nVertSplit}"] nXpos:Set["(${Display.Height}-${nXsize})+${Display.DesktopX}"] nYpos:Set["(((${nSession}-1)*${nYsize})%${Display.Width})+${Display.DesktopY}"] run windowsnapper -pos ${nXpos},${nYpos} -size ${nXsize}x${nYsize} windowpos -viewable 0,0 windowsize -viewable ${nXpos}x${Display.Width} }

I will be putting up a script at some point today or this weekend that will calculate "correct" size though, as with this script you will notice some distortion in the smaller windows :)

I am all setup and instancing now. I am using zanthors setup with some very minor changes. If I want to run another team with a small variation on this team all I need to do is copy and rename the files to something else, edit the files to make sure the callouts are going to the same new files (wow.iss, multi.iss, different white list in "repeater list" etc.). This would basically be my way of profiling.

Running the 4 smaller windows and one large window improves the main performance alot. With my system specs below I was running around shat with crusader on and didn't lose follow. I was trying to use skinning/herbing in the Lbolt macro as Zanthor suggested but the pip is so damn fast I just line up, pip, herb,pip and wait the herb to finish and go.

I decided to use a focus based targeting for my macros to get my setup back up fast. I am too lazy right now to figure out the ftl and I am still soaking the repeater functions.

I utilized my xkeys pro for most of the battle functions. I 2 capped the right side keys to match my pip so I can pip in order down the keypad and it matches my screen, top to bottom. To go with this I wrote a focus macro on the same hotkey as the pip, so when I hit toon2 all the others focus that screen and the toon in focus clears out its focus. I have yet to have any keypresses stay on when I pip, so I haven't had a runaway from not lifting a key too late.

About the repeater functions. The DNP for keyboard and mouse work just fine as well as the white list. I tested out the mouse repeater on a trainer and it works well. I need to make my SetView script like Zanthors as the only issue I had was different zoom angles. Mouse repeater would be a very effective Aoe targeting solution.

The key capturing is excellent. I save my account names and passwords on an xkeys stick and it fires the characters very fast. I overrode the DNP list and fired it a couple times and every character went to the other windows. I could not do that with other solutions as characters would get dropped everytime. I remapped my Xkeys pro to only use F1-F8 (sans F4) plus a variation of mod keys. Then the white list only has F1-F8 and ctrl,shft, alt and spacebar, all as single character entries. No issues passing any combo of keys that way.

This morning (early am) was the first time my crew set foot in an instance in several months. I am happy to play them again thanks in part to IS, Repeater and Windowsnapper.

Edit: For those curious about up/down key events, I am not specifying any at all. My spread out formation works exactly as it should.

WindowSnapper now has EzMode for those who were having a rough time setting it up the way they wanted. The WindowSnapper page describes the AutoLayout feature that was just added, which the defaults will work perfectly well for most people, maybe even Zanthor :P

EzMode instructions:
per session you want to go PiP, enter the following commands:

Code:

run windowsnapper autolayout

(yes, this can be set up to be automatically done per session as well)

I suspect Zanthor will be updating his multi.iss to use this so people won't have to edit the multi.iss for their resolution -- just if they want to change where the PiP screens will be located (e.g. autolayout top, instead of just autolayout)

Nice. Darn EZ-mode. Where were you when I needed you! ^^

Actually it wasn't that bad at all.

Edit: I just looked at the wiki page for Windowsnapper and it couldn't be any easier now. /cheers

My brain can't seem to wrap around this, so I would like some assistance.

I don't know what to put for my setup:
Two 1680x1050 20.1 in monitors, secondary to the left of the main, maximum of 4 wows. Main on main monitor, and 3 alts on the left like zanthor's seup.

Any help would be appreciated. (and the windows not distort)

Quote:

My brain can't seem to wrap around this, so I would like some assistance.

I don't know what to put for my setup:
Two 1680x1050 20.1 in monitors, secondary to the left of the main, maximum of 4 wows. Main on main monitor, and 3 alts on the left like zanthor's seup.

Any help would be appreciated. (and the windows not distort)

Zanthor's setup is already showing its age, and hes been busy so he hasnt gotten it updated I guess ;)

So here's what to do. If you're using Zanthor's multi.iss, replace it with this:

Code:

function main(int clients) { while ${Sessions} < ${clients} - 1 waitframe variable int nSession nSession:Set["${Session.Right[-2]}"] run autolayout 4 outer left /* Setup Hotkeys */ switch ${nSession} { case 1 globalbind is${nSession}_key "Ctrl+F1" "windowvisibility foreground;relay all press Ctrl+F1" proc 1 on 2 on 3 on 4 on break case 2 globalbind is${nSession}_key "Ctrl+F2" "windowvisibility foreground;relay all press Ctrl+F2" proc 1 on 2 on 3 on 4 on break case 3 globalbind is${nSession}_key "Ctrl+F3" "windowvisibility foreground;relay all press Ctrl+F3" proc 1 on 2 on 3 on 4 on break case 4 globalbind is${nSession}_key "Ctrl+F4" "windowvisibility foreground;relay all press Ctrl+F4" proc 1 on 2 on 3 on 4 on break case 5 globalbind is${nSession}_key "Ctrl+F5" "windowvisibility foreground;relay all press Ctrl+F5" proc 1 on 2 on 3 on 4 on break } /* Launch Repeater */ run repeater ui -load skins/wowskin/wowskin ui -load -skin WoWSkin repeater }

I ripped out his window positioning, and set it to use autolayout from the new WindowSnapper -- you will need to download the new version of that and probably want the new repeater (the ones in his zip are old).

You want space for 4 windows, so that's where the 4 comes in in the run autolayout line. Outer means it's going to be on the outside of your monitor instead of making room on the inside, and Left means you want them on the left of your main window.

If you're not using his setup that's fine, you just need to run that command in each session (whether it is automatic or not).

p.s. For those looking for PiP in EverQuest II or Lord of the Rings Online, an Inner Space update today makes them work. YMMV with EQ2 (by its design). LOTRO has a "feature" where it likes to reposition the window, so that's annoying when you set the main window size, but WindowSnapper and Repeater (and ClickBoxer, etc since that's built with the same things Repeater is built with, just with a GUI) work:
http://www.lavishsoft.com/wiki/image...RO_EQ2_WoW.jpg
LOTRO bottom left, EQ2 next to it, WoW main. WindowSnapper autolayout.

Cheers Lax. Got the window setup working nicely now both with Zanthor's setup and now with the autolayout. My only issue now is setting up proc affinitys because I seem to take a big fps hit when using IS compared to KC. I have setup the config for WoW default to be 45maxfps and 15maxfpsbk but I will start a session averaging 40fps and slowly edge down to 10fps. This is in EPL and strat with very few textures moving around. I am only running a dual core system, so with KC I run proc 1 on my main and proc 2 for the remaining 4. I can see the proc on commands in Zanthor's keybind setup, but this seems to be to share 4 cores across all 5 instances.

My only other query is if there is an automated way to have each session preload your different usernames.

Cheers

Updated my scripts to be compatable with the AutoLayout feature in windowsnapper.iss. This makes setup trivial.

And yea, I've been busy as hell at work, we are having our global IT meeting last week and this week, which means we spent a boatload of cash to fly our remote techs from Brasil and Australia into Iowa (Somehow I think most of us would rather have gone to Brasil or Australia!) and lots of long days with long meetings...

Quote:

Originally Posted by 'Noids99',index.php?page=Thread&postID=145951#post 145951

Cheers Lax. Got the window setup working nicely now both with Zanthor's setup and now with the autolayout. My only issue now is setting up proc affinitys because I seem to take a big fps hit when using IS compared to KC. I have setup the config for WoW default to be 45maxfps and 15maxfpsbk but I will start a session averaging 40fps and slowly edge down to 10fps. This is in EPL and strat with very few textures moving around. I am only running a dual core system, so with KC I run proc 1 on my main and proc 2 for the remaining 4. I can see the proc on commands in Zanthor's keybind setup, but this seems to be to share 4 cores across all 5 instances.

My only other query is if there is an automated way to have each session preload your different usernames.

Cheers

Well, the reason your FPS is lower is we're keeping your WoW resolution at the full screen size, and running 5 on a dual core is going to really tax your system as it is ;) With a quad you wouldn't likely see a hit, most people I'm talking to are pretty happy with the performance. As far as edging down toward 10fps, I'm not sure why you would see a constant decrease in FPS unless you're running out of RAM. If you were getting 10fps in Shatt you should be able to go to a random zone and get 45 still.

Anyway, you can change the proc commands, such that the one for case 1 says

Code:

proc 1 only

and the ones for case 2, case 3, case 4, and case 5 say

Code:

proc 2 only

And this will set up the affinity exactly as you have described.

As far as pre-loading different usernames, Inner Space has a command called FileRedirect that I have just begin showing people for use with using multiple config.wtf files, and selecting between them.

You can replace Zanthor's wow.iss with this, for example:

Code:

function main(int clients) { variable int Count for (Count:Set[1] ; ${Count}<=${clients} ; Count:Inc) { switch ${Count} { case 1 open "World of Warcraft" "World of Warcraft Default Profile" -startup "run multi ${clients}" -prestartup "FileRedirect config.wtf config-char1.wtf" break case 2 open "World of Warcraft" "World of Warcraft Default Profile" -startup "run multi ${clients}" -prestartup "FileRedirect config.wtf config-char2.wtf" break case 3 open "World of Warcraft" "World of Warcraft Default Profile" -startup "run multi ${clients}" -prestartup "FileRedirect config.wtf config-char3.wtf" break case 4 open "World of Warcraft" "World of Warcraft Default Profile" -startup "run multi ${clients}" -prestartup "FileRedirect config.wtf config-char4.wtf" break case 5 open "World of Warcraft" "World of Warcraft Default Profile" -startup "run multi ${clients}" -prestartup "FileRedirect config.wtf config-char5.wtf" break default open "World of Warcraft" "World of Warcraft Default Profile" -startup "run multi ${clients}" break } /* Wait 2 seconds (wait takes tenths of seconds) */ wait 20 } }

For sessions 1 through 5, this will redirect config.wtf to config-char#.wtf (e.g. config-char1.wtf through config-char5.wtf). You can change it to use whatever filename you like, so if you want it to use the name of your character or account, it can be config-noids.wtf, etc. Then, make a copy of config.wtf with each of those names, and either edit the saved account name in the WTF file, or just save the account name in game, and you're set :)