Anyone having success running this with an FTL setup? I just created 5 DKs and am going to need to be able to broadcast my mouse. After using FTL setup on my shamans I'm pretty hooked on it.
Anyone having success running this with an FTL setup? I just created 5 DKs and am going to need to be able to broadcast my mouse. After using FTL setup on my shamans I'm pretty hooked on it.
There's multiple ways to do FTL with this setup, the best and easiest way being with KeyMapper. Basically you create a bunch of key mappings, tell it to apply FTL Modifiers, and they're automatically applied for you. Key mappings can send different keys to different windows, do round-robin, and so on -- pretty much anything you need them to do, and enabling FTL Modifiers is as easy as flipping a switch. Most people have tended to go focus-based, but I spent a few hours working with Slats (I dont know if he goes by Slats on the forums here or if that was just his IRC name) getting his FTL going. With his feedback I fixed some issues with using FTL modifiers in Repeater (note: fixed in latest release of Repeater, which isn't in Zanthor's distribution), but I'm pretty sure ultimately he's using KeyMapper for it.Quote:
Originally Posted by 'blast3r',index.php?page=Thread&postID=165361#post 165361
If you want to try it there is of course a free trial of Inner Space (just fill out the form and if what you entered makes sense, I usually approve it within a few hours), and I would be happy to walk you through getting set up, in IRC. Some people are afraid to ask for help but really it's the people who do ask for help that shape the future of the software and the process of setting it up. I'm making sure what I'm building can easily support every legitimate scenario people ask for help in setting up, so when it comes out, the ISBoxer Toolkit will be able to have things up and running painlessly within minutes.
Ditto for me. I just set the profiler software to start with windows then close it before I start gaming.Quote:
Originally Posted by 'zanthor',index.php?page=Thread&postID=164916#post 164916
I found out the hard way though. I had my bottom row of G Keys set for target and dps rotation when soloing. Sadly these keys also fired off 4 5 and 6 which had aimed shot and multishot bound. This would cause weird auto targeting and application of shots that were confusing the hell out of me. :D
I went ahead and created an account and applied for a trial version. I'm looking forward to trying this out. Thanks!Quote:
Originally Posted by 'Lax',index.php?page=Thread&postID=165371#post1653 71
I got the trial and installed Innerspace along with repeater and windowsnapper. The first thing I found is the wiki documentation on windowsnapper has no mention of dual monitors. When I first get the wow clients loaded it seems to only let me use the main screen. Anyways, wow authentication servers are down ATM so I guess I will try and figure some of this out on my own and then come find you guys in IRC later.
Well, depending on your system there's not much difference between 1 monitor and 2, so typically you won't have to do anything particularly special to use dual monitors with WindowSnapper. If you can drag windows to the other screen and not have the software rendering FPS hit, everything will work quite well (if not, you'll need some extra attention). If your secondary monitor is on the right side for example, you can either use AutoLayout (outer right) to line them up on the left edge of the right monitor (detailed in the AutoLayout section of the WindowSnapper page), or manually position the windows on that screen by adding the left monitor's width in pixels -- so for mine, I have 1680x1200, the upper left corner of the second monitor is 1680,0, upper right is 3360. The ISBoxer Toolkit makes WindowSnapper configuration easier by giving you an interface to click and drag things to where you like them on whichever monitor, but I'm still spending all my time getting it ready for general use ;)Quote:
Originally Posted by 'blast3r',index.php?page=Thread&postID=165631#post 165631
Ok, so I went over this post a little bit and did not see
anyone mention getting IS to look at other folders to get my other toons working
in their own folder. So I went on IRC and Zanthor showed me how to get the
Profile going in the game configuration tab. Now, it loads up 5 blank wow
screens "Blank meaning the username is gone" and all of the wow's are
still the main, and not "Main, slave, slave, slave, slave". I am
guessing there is a file or something that I need to edit to get IS to look at
those folder and make the wow screens have the right username set to the right
wow folder.
Can't believe I might can help with something here!Quote:
Originally Posted by 'Zerocool2024',index.php?page=Thread&postID=165729 #post165729
This file is called wow.iss. There is probably a better way to do this with using variables but I like to destroy good scripts that others make and make them just barely work. This will open 5 wow sessions each with the proper username. You have to copy the current config.wtf and paste 5 times then go in and change the username in each one. Name them config1.wtf, config2.wtf, etc.
If the line
isn't there just add it and save the config#.wtf file.Code:SET accountName "accountname"
edit: I have two folders. One for my main and one for my alts. I don't need to redirect the one on my main so there are only 4 config.wtf redirects in the script I use.
Code:function main(int clients)
{
open "dkmain" "dkmain profile"
/* Wait 2 seconds (wait takes tenths of seconds) */
wait 30
open "dkalt" "dkalt profile" -prestartup "fileredirect config.wtf config1.wtf"
/* Wait 2 seconds (wait takes tenths of seconds) */
wait 30
open "dkalt" "dkalt profile" -prestartup "fileredirect config.wtf config2.wtf"
/* Wait 2 seconds (wait takes tenths of seconds) */
wait 30
open "dkalt" "dkalt profile" -prestartup "fileredirect config.wtf config3.wtf"
/* Wait 2 seconds (wait takes tenths of seconds) */
wait 30
open "dkalt" "dkalt profile" -prestartup "fileredirect config.wtf config4.wtf"
/* Wait 2 seconds (wait takes tenths of seconds) */
wait 30
}
I'm trying to keybind some X-keys but I'm totally lost. I have the 58 key professional model. Could someone give me some examples on how to set X-keys up, preferably using keymapper. Wen I use the "bind -keylist" command I see a bunch of "Button 0, Button 1, Button 2, etc., (all the way up to like 142, which I don't get.. shouldn't it be 114 as that's the most the 58 X-kyes can program including the second layer.) I can't seem to get them to work in keymapper, however.
Also, I'm not able to get my G15 keys to work either. :( I read that you need to clear the keys, so I set my profilier to the default profile and unbound all the keys, however, they don't seem to work in the keymapper, either. Argh.
Any help is appreciated!
X-Keys apparently uses the same driver for different models, so your device may appear to Inner Space to have more buttons than it actually has. The Button 1, Button 2 and so on are very likely from your X-Keys device. The following script can help you determine which button on your device corresponds to which button in Inner Space:Quote:
Originally Posted by 'propagandalf',index.php?page=Thread&postID=165885 #post165885
Save as (e.g.) buttontest.iss in the Scripts folder of your IS install, and run it in the console in the main program (the one that opens when you select Console from the menu) via "run buttontest". When you are done, "endscript buttontest". While the script is running, any button you press, any D-Pad that moves and any Axis that moves will spit out some output in the console (while your X-Keys doesn't have a D-Pad or Axis, other sorts of controllers like gamepads, joysticks, etc can fire those events). You will want to (or should, at least) rename your X-Keys buttons so that they don't say Button 1, Button 2 and so on, if for no other reason than they're probably not in the order you'd expect. Open up InputDevices.XML in the IS folder (use notepad or another text editor) and find the Set for your X-Keys. If there are multiple sets, it might take some trial and error to figure out which one is the right one, but have it open while you press buttons for the buttontest script and label them in the XML as you go. Zanthor for example names his X1, X2, and so on, and that's probably a good convention to follow for X-keys devices. When you're done, close IS first (it may overwrite InputDevices.XML on exit), then save InputDevices.XML. When you launch IS again, it will begin using the new names, which you can again test with the buttontest script.Code:atom AxisMoved(string Axis, float Position)
{
echo Axis=${Axis} position=${Position}
}
atom ButtonMoved(string Button, bool Position)
{
echo Button=${Button} position=${Position}
}
atom DPadMoved(string DPad, float Position)
{
echo dpad=${DPad} Position=${Position}
}
function main()
{
Event[OnAxisMove]:AttachAtom[AxisMoved]
Event[OnDPadMove]:AttachAtom[DPadMoved]
Event[OnButtonMove]:AttachAtom[ButtonMoved]
while 1
{
waitframe
}
}
The G-keys do in fact work with KeyMapper, and I know this because I have a G15 and I use KeyMapper ;) If you are concerned that they may not work, you can test this again with the buttontest script. When you press G1, it should say something about the G1 button. Someone else had some trouble yesterday with it, but it turned out they correctly set the G-key as the HotKey, but they also put the G-key to send to "all other" in the mapping -- which is going to do nothing in the other windows because WoW doesn't recognize the G-keys. So make sure you're not doing something like that :)