[ QUOTE ]
2. As a touch typist, Ive moved all my movement keys to the right by one key (WER,SDF in place of QWE, ASD) to allow using my primary fingers in a normal home-key position.
[/ QUOTE ]
Hallelujah, I'm not the only one! Sorry, not adding much to the discussion. 
Please try MA arc ID 351455, "Shard Stories: Scavenger's Hunt." Originally created for the Dr. Aeon contest, it explores the wild potential of one of the City's most concept-rich but content-poor settings: the Shadow Shard.
Gnarly,
Great stuff. 2.3 fixed the issues I saw between 1.1 and 2.1 (someone else posted all the issues before I got to it, though).
There's still one kinda major thing though.
If flying in a direction, and I hit a power (I'm a blaster, so an attack power, usually), I will sometimes plummet from the air down to the MOB I'm attacking. Needless to say, this can be a little hairy. It usually happens if I press the power just before I've let up on the direction key or just as I let up on the direction key.
Next time I'm in game I'll try to come up with a test case to reproduce the behavior, but if you try it from what I described, it shouldn't be too hard to make it happen.
Regardless, thanks for your effort - I love the binds. It's totally changed how I play!
[ QUOTE ]
As for as the game crashes, somebody else had that problem with binds... not just mine, but with all the bind_loading. Despite it seeming silly to me, apparently the game sends all changed binds to the server. Only one other person has experienced this who posted, so you're the second. Don't know what to say, or if I can help.
[/ QUOTE ]
Well, I found that if I just reload my default binds from a file instead of using the in-game reset to default, the game doesn't crash. Also if I use the in-game reset, then load from file, then load your binds, it doesn't crash! Something weird going on, but clearly not the fault of your bind set. I'll test this a bit more then report it as a bug. Thanks anyway!
[ QUOTE ]
So, I hope 2.2 helps the bind-killer problem with sprint remaining on when on the ground. It did for me.
[/ QUOTE ]
Fixed here. 
I hope you won't get bored of me saying this, but these binds are awesome. Synabyss, Blue Volt, Wasabi Joe, Ahzurdan, and anyone else involved - thank you all. These binds have dramatically improved the game for me.
[ QUOTE ]
If flying in a direction, and I hit a power (I'm a blaster, so an attack power, usually), I will sometimes plummet from the air down to the MOB I'm attacking. Needless to say, this can be a little hairy. It usually happens if I press the power just before I've let up on the direction key or just as I let up on the direction key.
[/ QUOTE ]
Pretty sure there is no way around this. I am willing to bet this happens when you go from a standstill, hit a direction button, then immediately hit another power. In that case the bind is turning off hover and queuing fly to turn on. Then by hitting the power so soon, you cause fly to be thrown out before it goes off and instead queue the power you hit, which ends up going off.. while you plummet to the ground because fly got thrown out.
With all binds of this nature involving "automagically" turning on powers for you, you have to be careful and rather deliberate in your button pushing or this will happen. You can prevent the different bound keys from interfering with each other in this way (as pretty much all the work on these bind sets has been doing lately), but throw unknown power activations in the mix and there's no way around it except to avoid the situation.
[ QUOTE ]
Pretty sure there is no way around this. I am willing to bet this happens when you go from a standstill, hit a direction button, then immediately hit another power. In that case the bind is turning off hover and queuing fly to turn on. Then by hitting the power so soon, you cause fly to be thrown out before it goes off and instead queue the power you hit, which ends up going off.. while you plummet to the ground because fly got thrown out.
[/ QUOTE ]
Yeah, I was afraid this was the kind of thing that was happening given how queued power preemption works. Too bad the macro language doesn't let you make sets of operations atomic, even if it would mean rejecting new actions until the transaction set completes. I would imagine, though, that this is outside the scope of what Cryptic intended the macro/bind capability for.
Still, this is only a minor annoyance compared to the convenience these binds impart upon the game.
Jigga What?
I am using Gnarly's, they appear to work fine, but every time I press a re-bound key in 'Speed on Demand Mode' the system reports keybind errors... but the key still works as it should.
In fact on loading the bind files I get the following error...
bind takes 2 arsgs, you gave 1
binds a ky to a command - 'bind k ++forward' will set k to toggle runningforward.
bind <string> <string>
bind "+up"
Pressing Ctrl R (to go into Speed on Demand Movement) works, I get the /tell and the mode works, but I get the following error
bind "+zoomin$$-zoomin$$up l$$down o$$forward o$$backward o$$left o$$right o$$bind_load_file c:\cohbinds\R\R_txt
That is the correct path and the file exists and has data in it.
Then, any rebound key in Speed on Demand Movement mode works as they should, but all throw up similar error msgs to the one above (with different file names, of course).
I tried re-loading in my saved keybinds file, or resetting keybinds in Options, and a combination of both, and then re-loading Snarlys, but I still get the same errors.
Even tried different toons, same issues.
Ahz, I've been using your latest binds, and I'm still having the same issue with it, in that when I activate superspeed by moving, I still end up in sprint mode when I stop.
Gnarley, I've been testing out your binds, and I've been getting the same errors as the above posters have mentioned but I haven't been moving in superspeed at all. Perhaps I'm not using your binds correctly, I haven't had a full chance to really play around and see what's wrong.
Hey there.
Didn't disappear Gnarly I have been testing your binds but the latest I had was 1.2 which gave me some problems and I had to do a complete reset because I was in TFs all week. I see version 2.3 is up so I will reload and test with them today.
Edit: Played for quite a while with my superspeedster with no problems so far. Everything worked great and very smooth. it does take some getting used to when setting powers to queue up, and I did finally have to reset my move keys )using your interface program) to wasd. As much as I like the concept of esdf, years of training my fingers different have proved impossible to overcome
Just as an aside, I use the arrow keys for moverment also, especially turnleft and turnright. I have found that this combines very well with Speed On Demand, giving me an option for more precise movement than superspeed will allow me. I also added strafeleft and straferight commands to numpap 4 and numpad6 respectively for quick access.
I will try version 2.3 on my blaster tonight (he has flight).
Edit AGAIN: Also, to clarify, I do get the responses in the text window as indicated above by other posters when using Speed on Demand. Here's a sample:
[ QUOTE ]
Usage:
bind takes 2 args, you gave 1.
binds a key to a command - 'bind k ++forward' will set k to toggle runningforward.
bind <string> <string>
bind "+zoomin$$-zoomin$$up 1$$down 0$$forward 1$$backward 0$$left 0$$right 0$$bind_load_file C:\CoH\R\R_e.txt"
Now readying Super Speed instead of Sprint.
Now readying Sprint instead of Super Speed.
Now readying Super Speed instead of Sprint.
Usage:
bind takes 2 args, you gave 1.
binds a key to a command - 'bind k ++forward' will set k to toggle runningforward.
bind <string> <string>
bind "+zoomin$$-zoomin$$up 1$$down 0$$forward 0$$backward 0$$left 0$$right 0$$bind_load_file C:\CoH\R\R_.txt"
Shutting off Super Speed.
Usage:
bind takes 2 args, you gave 1.
binds a key to a command - 'bind k ++forward' will set k to toggle runningforward.
bind <string> <string>
bind "+zoomin$$-zoomin$$up 1$$down 0$$forward 1$$backward 0$$left 0$$right 0$$bind_load_file C:\CoH\R\R_e.txt"
Now readying Super Speed instead of Sprint.
Now readying Sprint instead of Super Speed.
Now readying Super Speed instead of Sprint.
Shadow Maul is recharged.
Usage:
bind takes 2 args, you gave 1.
binds a key to a command - 'bind k ++forward' will set k to toggle runningforward.
bind <string> <string>
bind "+zoomin$$-zoomin$$up 1$$down 0$$forward 0$$backward 0$$left 0$$right 0$$bind_load_file C:\CoH\R\R_.txt"
Shutting off Super Speed.
[/ QUOTE ]
Also, as mentioned, it all actually seems to work fine, this just spams the top window, not a major problem.
Ok, sounds like 2.3 fixed the major problems, but let me comment on the other problems people are having:
-Chat Window Spam. I've turned off all damage and system text to the chat window, so I don't see this. And I'll never be able to do anything with the "readying sprint instead of super speed"... but if you don't have SS for any characters, don't type Super Speed in as a primary power, and that'll cut it down a little. As for what looks like Help messages from the game telling us how to actually use bind, not sure why that's coming up, but I'll look into it next week.
- Oaken Filipino, are you typing SUPER SPEED in for the Primary Run Power? I used to have it as a default, but I figured there were more players without a SS Char than with, so you have to type the power name SUPER SPEED explicitly now. Seems to be working for Greyhawke, so give it a try.
- Next version, sometime next week, I'll add that last line to my bind files to prevent some of that bind_load spam.
- Falling out of sky when fighting. Yes, it's because you're queuing another power, so just don't do that 
Seriously though, you also are losing your hover defense bonus, and getting an Accuracy penalty, so don't do it. Stand your ground and fight. And when you decide to move, stop fighting (binds usually cancel any queued powers anyway, and move, then stop to fight again.
So, it looks like they're finally in a more stable state, and I can leave changes until Monday. Thanks for the positive comments, they're always nice to hear since we've all put a lot of work into these binds. And if I remember back to when I first came to this thread... Man, I LOVE flying. It's why I got this game. And with these binds, of any flavor, I can spend lots of time just zooming around exploring
Anyway, I hope you all do enjoy them, and kick lots of villain butt.
Gnarly
[ QUOTE ]
As for what looks like Help messages from the game telling us how to actually use bind, not sure why that's coming up, but I'll look into it next week.
[/ QUOTE ]
Well I thought they were Error msgs rather than Help msgs, but now I've sat and played a bit more it seems more likely that the commands are being echoed along with a Help msg.
No matter what 'Channels' I set to 'None' the Help section of the msgs I get will not go away.
However, the second part of the msgs I get (that start - bind "+zoomin$$..... etc) can be made to go away by setting 'System' to 'None'.
I'd rather have a better solution to this though.
Well this part...
[ QUOTE ]
Usage:
bind takes 2 args, you gave 1.
[/ QUOTE ]
along with its explainations, seems to come from the first line in every bind file, which has a command not bound to any key (that's why it says you only have one argument). I am not sure if this was intentional, or something caused by the initial setup program. It also may have been an entry I put in to the initial setup program.
Here's the bind file for R_.txt as an example (I use wasd for movement and v for down):
[ QUOTE ]
lctrl+m "tell $name, C:\CoH\R\R_.txt"
"+zoomin$$-zoomin$$up 0$$down 0$$forward 0$$backward 0$$left 0$$right 0$$bind_load_file C:\CoH\R\R.txt"
v "+zoomin$$-zoomin$$up 1$$down 1$$forward 0$$backward 0$$left 0$$right 0$$bind_load_file C:\CoH\R\R_b.txt"
w "+zoomin$$-zoomin$$up 1$$down 0$$forward 1$$backward 0$$left 0$$right 0$$powexec_name SPRINT$$powexec_name SUPER SPEED$$powexec_name SPRINT$$powexec_name SUPER SPEED$$bind_load_file C:\CoH\R\R_e.txt"
s "+zoomin$$-zoomin$$up 1$$down 0$$forward 0$$backward 1$$left 0$$right 0$$powexec_name SPRINT$$powexec_name SUPER SPEED$$powexec_name SPRINT$$powexec_name SUPER SPEED$$bind_load_file C:\CoH\R\R_d.txt"
a "+zoomin$$-zoomin$$up 1$$down 0$$forward 0$$backward 0$$left 1$$right 0$$powexec_name SPRINT$$powexec_name SUPER SPEED$$powexec_name SPRINT$$powexec_name SUPER SPEED$$bind_load_file C:\CoH\R\R_s.txt"
d "+zoomin$$-zoomin$$up 1$$down 0$$forward 0$$backward 0$$left 0$$right 1$$powexec_name SPRINT$$powexec_name SUPER SPEED$$powexec_name SPRINT$$powexec_name SUPER SPEED$$bind_load_file C:\CoH\R\R_f.txt"
T "+zoomin$$-zoomin$$up 1$$powexec_name SPRINT$$powexec_name SUPER SPEED$$powexec_name hover$$powexec_name hover$$powexec_name fly$$powexec_name fly$$bind_load_file C:\CoH\BO\BO_.txt"
G "powexec_name SPRINT$$powexec_name SUPER SPEED$$powexec_name SPRINT$$powexec_name SUPER SPEED$$powexec_unqueue$$up 1$$down 0$$forward 0$$backward 0$$left 0$$right 0$$bind_load_file C:\CoH\R\R_.txt"
R "++forward$$backward 0$$up 1$$down 0$$left 0$$right 0$$powexec_name SPRINT$$powexec_name SUPER SPEED$$powexec_name SPRINT$$powexec_name SUPER SPEED$$bind_load_file C:\CoH\AR\AR_.txt"
TILDE "follow$$powexec_name SPRINT$$powexec_name SUPER SPEED$$powexec_name SPRINT$$powexec_name SUPER SPEED$$bind_load_file C:\CoH\FR\FR_.txt"
[/ QUOTE ]
I just randomly sampled files in each directory and the first line was not bound to a key in each file.
Again, not a major problem. It works great.
I did, I'll try it again, later tonight, though.
[ QUOTE ]
I just randomly sampled files in each directory and the first line was not bound to a key in each file.
Again, not a major problem. It works great.
[/ QUOTE ]
Hmm... that's the UP bind. Did you rebind up, or choose a default? Do you USE up? If you don't have a key there, I'd be surprised if it DID actually work. Hitting enter should give you "space", the default. So not sure why/how you'd get that. Try running the bind program again, perhaps? If it ends up the same, try actually typing in SPACE (caps not required). Might have been a strange glitch, as it doesn't happen for me, and if people can't jump or go up, I'm sure I would have heard of it.
Edit: thought this right after I hit submit... maybe you can still jump, because without a key, you might not have overwritten your normal +up command bound to the spacebar. If you have Fly, do you switch to fly when pressing up only? You can /bind_save to see how your keys are actually bound.
Oaken, well, if you did that, then it just might not work for Super Speed. Greyhawke, it works for you with SS? How did you configure it? Does Super Speed have a recharge time that might interfere with things?
Gnarly
[ QUOTE ]
Here's the bind file for R_.txt as an example (I use wasd for movement and v for down):
[/ QUOTE ]
Just a thought - it looks to me like you pressed SPACE instead of typing the word "SPACE" when asked what key to use for up. The line without a keybind is the "move up" line.
Here's my R_.txt for comparison:
[ QUOTE ]
lctrl+m "tell $name, D:\games\coh\binds\R\R_.txt"
SPACE "+zoomin$$-zoomin$$up 0$$down 0$$forward 0$$backward 0$$left 0$$right 0$$mouse_look 0$$bind_load_file D:\games\coh\binds\R\R.txt"
X "+zoomin$$-zoomin$$up 1$$down 1$$forward 0$$backward 0$$left 0$$right 0$$bind_load_file D:\games\coh\binds\R\R_b.txt"
W "+zoomin$$-zoomin$$up 1$$down 0$$forward 1$$backward 0$$left 0$$right 0$$mouse_look 1$$powexec_name SPRINT$$powexec_name SPRINT$$bind_load_file D:\games\coh\binds\R\R_e.txt"
S "+zoomin$$-zoomin$$up 1$$down 0$$forward 0$$backward 1$$left 0$$right 0$$mouse_look 1$$powexec_name SPRINT$$powexec_name SPRINT$$bind_load_file D:\games\coh\binds\R\R_d.txt"
A "+zoomin$$-zoomin$$up 1$$down 0$$forward 0$$backward 0$$left 1$$right 0$$mouse_look 1$$powexec_name SPRINT$$powexec_name SPRINT$$bind_load_file D:\games\coh\binds\R\R_s.txt"
D "+zoomin$$-zoomin$$up 1$$down 0$$forward 0$$backward 0$$left 0$$right 1$$mouse_look 1$$powexec_name SPRINT$$powexec_name SPRINT$$bind_load_file D:\games\coh\binds\R\R_f.txt"
T "+zoomin$$-zoomin$$up 1$$powexec_name SPRINT$$powexec_name hover$$powexec_name hover$$powexec_name fly$$powexec_name fly$$bind_load_file D:\games\coh\binds\BO\BO_.txt"
G "powexec_name SPRINT$$powexec_name SPRINT$$powexec_unqueue$$up 1$$down 0$$forward 0$$backward 0$$left 0$$right 0$$bind_load_file D:\games\coh\binds\R\R_.txt"
R "++forward$$backward 0$$up 1$$down 0$$left 0$$right 0$$mouse_look 1$$powexec_name SPRINT$$powexec_name SPRINT$$bind_load_file D:\games\coh\binds\AR\AR_.txt"
F "follow$$powexec_name SPRINT$$powexec_name SPRINT$$bind_load_file D:\games\coh\binds\FR\FR_.txt"
[/ QUOTE ]
I use WASD, with SPACE for up and X for down.
Hope that helps?
[ QUOTE ]
Just a thought - it looks to me like you pressed SPACE instead of typing the word "SPACE" when asked what key to use for up. The line without a keybind is the "move up" line.
[/ QUOTE ]
Ok this seems to be the case although I would have said that I hit enter to accept the default, I guess I did not. I re-ran the speed on demand program and made sure to accept the default and I no longer have the issue.
As far as superspeed, it works great. For my primary ground power I entered
SUPER SPEED
just like that. All caps, with the space not an underscore.
Good luck, and thanks again Gnarly this seems to be doing the job quite well!
[ QUOTE ]
Falling out of sky when fighting. Yes, it's because you're queuing another power, so just don't do that Seriously though, you also are losing your hover defense bonus, and getting an Accuracy penalty, so don't do it. Stand your ground and fight. And when you decide to move, stop fighting (binds usually cancel any queued powers anyway, and move, then stop to fight again.
[/ QUOTE ]
I'm usually the one chasing after the MOBs when I fly during a flight (or else I'm retreating, and then shooting back isn't a priority at that point). It's universally a matter of being too quick on the keys in my case - I've gotta let hover wink on (I have it in my alt tray so I can watch it there) before firing. Not a huge adjustment to my strategy, just a little discipline.
I still maintain that the binds have totally changed the way I play - thank you!
Ahz,
Those last two changes did the trick!
Thank you so much. I'd love to see Joe incorporate these into his 2.4 set and also the tweak that eliminates the combat spam.
Thanks again to all in the thread who have worked on this so hard, including Falstaff for the great batch file.
[url="http://tinyurl.com/4ylgy"]The Wanderers[/url] of Virtue
We farm fun!
Gnarly-
I ran the program again, this time accepting the defaults but the speed on demand thing doesn't seem to be working still. I hit "g" and superspeed turns on as opposed to turning on when I moved. I typed SUPER SPEED like greyhawke did. I'm a bit puzzled because I believe I followed the directions to the letter.
Hmmm...
Ok, Oaken Filipino, here are some things to try, but I'm a bit befuddled too. Try cut and pasting the forward line (just the one line is enough) of your R.txt file, in your R subfolder into your reply. It should have 2 powexec_name calls to sprint, and 2 to Super Speed, with the Super Speed ones being 2nd.
Also, maybe do a /bind_save from the game, then look at the keybinds.txt file and make sure that line is the same as the one above from the R.txt file... if not hit control-R until you 'Tell' yourself that you're in Speed on Demand Mode.
Once we take a look at the binds that the program is making, we'll be able to tell why it's not working.
Gnarly
Ahz, did you get my file and how is it working? It seems that I cannot toggle from run to fly while running diagonally after the changes but there are some pros to the bind.
It does not mess up after porting to another area.
When immobalized while flying, the bind will still bring you to the fly mode after the immobalize is gone.
Hey Sinabyss all I can say is GREAT WORK!! But the only problem I have is that I am a lefty and I use the arrow keys instead of WASD what do I need to do to change the file so it works with those keys??? Thanks again!!
Hi, your script made my life easyer.
I'd like to know one thing:
I usualy use turnleft and turnright instead of left and right.
I found the easyest way to change this into the reset.txt +left by +turnleft and +right by +turnright it works fine for me.
But when i activate by control+r the run and fly mode, it still use the strafe mode. where should i change this because there is too many files...?
Thanks for your great work
[ QUOTE ]
Hitting enter should give you "space", the default. So not sure why/how you'd get that. Try running the bind program again, perhaps?
[/ QUOTE ]
......... 
......... DOH
I will re-do my bindings, this time not just pressing the space bar, lol.
Great work btw, I love them even without UP working as it should due to my error.
EDIT
Just did the changes, all the 'error' msgs have gone and now SPACE with Fly makes me move at a decent rate again.
Once again, Great Keybinds, fantastic work!
Ok, 2.3 is up.
Fixes that problem with blastoff when using the same key for RUN and FLY. This happened because to use blastoff, I change the Fly key to be an up/down key... it's activated on press and release. So you'd press it, go into blastoff, release it, go into fly. Worked fine. BUT, when you press it again (now it's your ground key) it changes you to run/sprint mode on the press, and makes it your fly key again, and then when you release it it puts you in permanent blastoff!
This will take more looking into, but I think keys are ALWAYS run on both press and release, but the release is ignored if it's not a + command. So if you take a non +command key and change it's bind to a +command key, it'll cause problems.
So, to fix it I added a Setdown mode. So now when you're in the air, and press your RUN key and hold it, you will FLY DOWN until you release it, and THEN you will be put in RUN mode. Seems to work for me in both Toggle and separate Run/Fly key modes.
One problem I ran into when changing keys when re-running programs: if you run the program twice, then you need to manually set the keys that were used the first time, but not the second, to NOP (/bind X nop) or you'll accidentally press them from habit, and get yourself WAY screwed up. The program does not clear any binds on other keys. It's probably good to hit CTRL-R into normal mode before re-running the program if you plan to change keys, so at least any old keys won't have a complex bind on them.
Ok, gotta go... but try it out, and post any problems here.
Gnarly