I'm not sure if this is the appropriate place to put suggestions for ISBoxer features or not, but I figured I could pop a few in here:
1) Right now launching a character set is an all or nothing thing. But sometimes you have 1 instance/character crash, or lock-up, or get stuck. And then you have to play with the launcher to get the right one signed back in, or log all out and re-launch them all. Being able to launch the entire character set, or specify to just launch one particular character of the set would be really nice. This also helps in situations with LOTRO when you get queued to log in to a server, as the launcher for the next character won't execute properly if the previous character's launcher is waiting in a queue.
2) It might be handy to be able to specify key-combos that would add/remove a character from an action target group (relay group). I find with my characters that if I'm running 4 Rune-Keepers, I can run all in all out damage mode, require 1 healer and sometimes 2 healers. Having binds setup for a subset of the group as healers would be nice to have a key that I could press that would add Rune-keeper (RK) #4 to the healer group and remove him from the damage group. And with another key add him back to the damage group and remove him from the healer group, etc.
That's it for now, but they're a couple of pretty big suggestions...
Thanks Lax, as always!
ISBoxer Suggestions
Moderators: Lavish Software Team, Moderators
Great! I look forward to checking them out.
I've gone back to a 1 computer situation for a short period of time, and chose that as a good opportunity to re-tool using ISBoxer rather than pure scripting as I had before.
Setup time was a lot shorter than I'd thought it would be, and it seems to be working really well for me. I'm not sure how well it will expand back out to my hybrid setup (1 character on 1 computer and 4 on the other), but we'll cross that bridge when we come to it.
I've gone back to a 1 computer situation for a short period of time, and chose that as a good opportunity to re-tool using ISBoxer rather than pure scripting as I had before.
Setup time was a lot shorter than I'd thought it would be, and it seems to be working really well for me. I'm not sure how well it will expand back out to my hybrid setup (1 character on 1 computer and 4 on the other), but we'll cross that bridge when we come to it.
Dynamic Action Target Grouping is working great. A few more ideas:
1) An "Export to Client Computer" (or "Export to Client Computer X" where X is a computer name) function would be handy for those of us running on multiple computers. What I found yesterday with the hang-ups was that the 2nd computer didn't care for having Actions bound to lighting of "M-key" lights on a G-15 keyboard. Having a check-box on the computer setup could allow us to check what functionality exists on what computer, and then with an export to that computer function, ISBoxer could strip any actions/keypresses that use that functionality.
2) When I setup my main system in the Computer list, and tried to setup Character Sets as launching on that computer (rather than just on "Current Computer"), they don't show up on the Character list. This makes it difficult to move configurations between the computers in my setup, since I have to change the character sets' allocation to the computer on the client computers.
3) I know that a lot of people use repeater for a homogenous group-setup, so repeating keystrokes to ALL instances is ideal. But for when I use my setup of 1 champ (as main on main PC) / 4 runekeepers (all on client PC), I'd actually prefer for the keystrokes to only be repeated to the 4 runekeepers and not to the main PC , or at least have the option to turn repeater on in this way. Maybe there's a way to do this already, but if not I think it'd be a nifty little addition.
1) An "Export to Client Computer" (or "Export to Client Computer X" where X is a computer name) function would be handy for those of us running on multiple computers. What I found yesterday with the hang-ups was that the 2nd computer didn't care for having Actions bound to lighting of "M-key" lights on a G-15 keyboard. Having a check-box on the computer setup could allow us to check what functionality exists on what computer, and then with an export to that computer function, ISBoxer could strip any actions/keypresses that use that functionality.
2) When I setup my main system in the Computer list, and tried to setup Character Sets as launching on that computer (rather than just on "Current Computer"), they don't show up on the Character list. This makes it difficult to move configurations between the computers in my setup, since I have to change the character sets' allocation to the computer on the client computers.
3) I know that a lot of people use repeater for a homogenous group-setup, so repeating keystrokes to ALL instances is ideal. But for when I use my setup of 1 champ (as main on main PC) / 4 runekeepers (all on client PC), I'd actually prefer for the keystrokes to only be repeated to the 4 runekeepers and not to the main PC , or at least have the option to turn repeater on in this way. Maybe there's a way to do this already, but if not I think it'd be a nifty little addition.
1. Interesting. ISBoxer can easily strip the lighting commands at load time rather than export time. I'll check on that bug (it shouldn't actually matter as far as IS is concerned, as IS should identify that there is no such keyboard and that it has nothing to pass the lighting command to -- if there *is* a G11/G15 on that computer but, say, a different version, let me know that too).
But, yes there are lots of features like exporting to another computer that would be very handy for multiple PC users, and I will get to those soon. I've been making sure that the actual in-game features have been getting the bulk of the attention first, and then things that have little or no effect on gameplay and can be lived without (like exporting to another PC) can be taken care of once the bulk of the gameplay feature set is completed. I'll get to that part soon.
2. I thought I fixed that bug. I'll check that bug again
3. I assume you're playing on the main PC and thus meaning you want the main PC to ignore the keystrokes while repeating them to the others? This actually falls in the "KVM mode" category, which is a planned feature for a near-future release (otherwise, selecting repeater target is technically implemented in Repeater, just not exposed except for with mouse repeat via repeater regions). I recently got everything necessary to do that built into IS, but needed to get the new IS window management out before worrying about this particular feature, and then I spent the last week working out all the kinks that popped up with various games (EQ1).
So yes, definitely planned very very soon, and will likely be exposed via a mapped key action with a target picker that doesn't allow self (i.e. no current window, and groups only including "other", identical to Send Next Click boxes or the repeater region target picker in the in-game gui), and an option (a separate checkbox) to block keystrokes and/or clicks from the active window.
But, yes there are lots of features like exporting to another computer that would be very handy for multiple PC users, and I will get to those soon. I've been making sure that the actual in-game features have been getting the bulk of the attention first, and then things that have little or no effect on gameplay and can be lived without (like exporting to another PC) can be taken care of once the bulk of the gameplay feature set is completed. I'll get to that part soon.
2. I thought I fixed that bug. I'll check that bug again
3. I assume you're playing on the main PC and thus meaning you want the main PC to ignore the keystrokes while repeating them to the others? This actually falls in the "KVM mode" category, which is a planned feature for a near-future release (otherwise, selecting repeater target is technically implemented in Repeater, just not exposed except for with mouse repeat via repeater regions). I recently got everything necessary to do that built into IS, but needed to get the new IS window management out before worrying about this particular feature, and then I spent the last week working out all the kinks that popped up with various games (EQ1).
So yes, definitely planned very very soon, and will likely be exposed via a mapped key action with a target picker that doesn't allow self (i.e. no current window, and groups only including "other", identical to Send Next Click boxes or the repeater region target picker in the in-game gui), and an option (a separate checkbox) to block keystrokes and/or clicks from the active window.
Sounds great!
Just a side note, these are of course just suggestions from me on how IS might make *my* life a bit easier, and give me a bit more power in my particular setup. I try to think about if it applies to other users in the same or similar setups and think about those scenarios before posting a suggestion purely for myself.
For the most part, I'm pretty well setup here. The dynamic action target group addition made a huge difference for me, and was the last major thing I was really wanting to get to good effectiveness.
I think the next thing that would give me better control would be to get an X-keys pad and integrate that in, rather than trying to shoe-horn in my Nostromo. Other than that, having the 3rd suggestion above (the one regarding selecting targets for repeater, and limiting the main system from getting those) is the only one that will affect me in gameplay right now, I think. The other ones just make it easier for me to tinker with the setup and get back and up and running quicker/easier.
Thanks, as always!
Just a side note, these are of course just suggestions from me on how IS might make *my* life a bit easier, and give me a bit more power in my particular setup. I try to think about if it applies to other users in the same or similar setups and think about those scenarios before posting a suggestion purely for myself.
For the most part, I'm pretty well setup here. The dynamic action target group addition made a huge difference for me, and was the last major thing I was really wanting to get to good effectiveness.
I think the next thing that would give me better control would be to get an X-keys pad and integrate that in, rather than trying to shoe-horn in my Nostromo. Other than that, having the 3rd suggestion above (the one regarding selecting targets for repeater, and limiting the main system from getting those) is the only one that will affect me in gameplay right now, I think. The other ones just make it easier for me to tinker with the setup and get back and up and running quicker/easier.
Thanks, as always!
Oh, one other suggestion. Currently when the updater runs, after it updates ISBoxer, it just stops.
With most auto-updating pieces of software, if you choose to update the software, it will launch the updated piece of software after the update for you. It'd be a nice thing to add. Obviously it's not that big of a deal, but just an added layer of polish to consider for the final product!
With most auto-updating pieces of software, if you choose to update the software, it will launch the updated piece of software after the update for you. It'd be a nice thing to add. Obviously it's not that big of a deal, but just an added layer of polish to consider for the final product!
Yes. There is a way in ISBoxer 31. 
It's not an obvious usage, so that is actually mentioned here:
http://www.lavishsoft.com/wiki/index.ph ... _Key_State
It's not an obvious usage, so that is actually mentioned here:
http://www.lavishsoft.com/wiki/index.ph ... _Key_State
I upgraded to ISBoxer build 31 last night and played around with it and the Multiple Computer Helper.
I added the Mapped Key State to my profile, but I didn't get into a situation to actually use it in game yet.
However, I had the "hang" I previously experienced and discussed with you on IRC. I traced the cause back to the "M-key light" actions in the key mappings again. I noticed a couple of interesting behaviors with regard to this setting:
1) For the key-maps it now has a "Computer" selection for the Key lighting. These all defaulted to "Current Computer" so I changed them to be set to my main computer. The setting stayed in the drop-box, but the "tree" structure that lists out what is going on in that Step did not update (It still read "M1 Light On->Current Computer").
2) When I exported to the other computer, and checked this, it seemed to be the same way as on the main computer.
I removed the actions from the step and did not get the "hang" on startup on the 2nd computer. I don't believe that I tried to run it with the script after I changed the "Current Computer" selection to the main PC selection, so I'm not sure if it's just a display bug for ISBoxer or if IS isn't reading the setting properly either. I'll have to give it a go tonight.
Other than that, it seems like the multiple computer setup is working great. I also verified that setting a computer name (instead of "Current Computer") shows the character set in the IS menu for launching, which I'd had an issue with before.
Finally, a suggestion: Would it be possible to have a check-box for ISBoxer to set it to *always* run the Multiple Computer Helper on startup? I know that some people won't want/need it to run everytime, but for us multiple-PC users, we have to start it on each and every PC for them to see each-other, so the more PCs the more of a hassle it is to do.
As always, I'm very pleased with the progress!
I added the Mapped Key State to my profile, but I didn't get into a situation to actually use it in game yet.
However, I had the "hang" I previously experienced and discussed with you on IRC. I traced the cause back to the "M-key light" actions in the key mappings again. I noticed a couple of interesting behaviors with regard to this setting:
1) For the key-maps it now has a "Computer" selection for the Key lighting. These all defaulted to "Current Computer" so I changed them to be set to my main computer. The setting stayed in the drop-box, but the "tree" structure that lists out what is going on in that Step did not update (It still read "M1 Light On->Current Computer").
2) When I exported to the other computer, and checked this, it seemed to be the same way as on the main computer.
I removed the actions from the step and did not get the "hang" on startup on the 2nd computer. I don't believe that I tried to run it with the script after I changed the "Current Computer" selection to the main PC selection, so I'm not sure if it's just a display bug for ISBoxer or if IS isn't reading the setting properly either. I'll have to give it a go tonight.
Other than that, it seems like the multiple computer setup is working great. I also verified that setting a computer name (instead of "Current Computer") shows the character set in the IS menu for launching, which I'd had an issue with before.
Finally, a suggestion: Would it be possible to have a check-box for ISBoxer to set it to *always* run the Multiple Computer Helper on startup? I know that some people won't want/need it to run everytime, but for us multiple-PC users, we have to start it on each and every PC for them to see each-other, so the more PCs the more of a hassle it is to do.
As always, I'm very pleased with the progress!
Just a quick bump since there have been a few ISBoxer build releases since I posted the above bug and it still remains a bug. I could be wrong in thinking that this is a relatively easy bug to fix, but I'm more guessing that it just got lost in the shuffle.
Anyway, to repeat the bug:
- Setup ISBoxer with 2 or more computers
- Setup a Key Map
- Add a key to that key map and 1 step
- Add a New Light Action to the Step
- Set the 'Target Computer' to anything BUT '<Current Computer>'
- Set up the rest of the light information ('M1' and 'On')
- Toggle the tree display for the Step (Click the '-' and then the '+' next to 'Step')
- Observer that it still says "M1 light 'On' -> <Current Computer>" for that action. Instead, the '<Current Computer>' portion should be whatever computer you set in 'Target Computer'.
Again, this seems to be merely a display bug for the ISBoxer software (as the .XML value is being written to the file). However, it seems that the parsing that goes on in Inner Space itself is ignoring this value, as it will "hang" on startup on the other computer not attached to a G-15 keyboard.
Anyway, to repeat the bug:
- Setup ISBoxer with 2 or more computers
- Setup a Key Map
- Add a key to that key map and 1 step
- Add a New Light Action to the Step
- Set the 'Target Computer' to anything BUT '<Current Computer>'
- Set up the rest of the light information ('M1' and 'On')
- Toggle the tree display for the Step (Click the '-' and then the '+' next to 'Step')
- Observer that it still says "M1 light 'On' -> <Current Computer>" for that action. Instead, the '<Current Computer>' portion should be whatever computer you set in 'Target Computer'.
Again, this seems to be merely a display bug for the ISBoxer software (as the .XML value is being written to the file). However, it seems that the parsing that goes on in Inner Space itself is ignoring this value, as it will "hang" on startup on the other computer not attached to a G-15 keyboard.
Yeah sorry, this issue went by the wayside as there was a handful of issues I absolutely needed to solve before my move and unfortunately this one didn't make that cut. I will definitely see what I can do about it when my computers are set up again (sometime this week). It may very well be simple to fix
That's cool. I know you're busy with the move and all, and this isn't a game-breaker. It's just an annoyance whenever I make adjustments to the profile, since I have to re-edit the client computer's profile after export to remove the light change actions.Lax wrote:Yeah sorry, this issue went by the wayside as there was a handful of issues I absolutely needed to solve before my move and unfortunately this one didn't make that cut. I will definitely see what I can do about it when my computers are set up again (sometime this week). It may very well be simple to fix
Hope the move went well, and your getting all settled and adjusted to the new place!