Blue_Volt_NA

As will I, and Gnarly, no doubt. But my best won't be nearly as good as Joe's best, but Gnarly's best will likely be just a good. Of course, ahz's best is pretty good to...

Madam_O,
I have heard a complint with lag from someone using a fairly sophisticated set of bind files to control flight and sprint. This set used a large aray of toggle-binds that are constantly loading new binds to the movement keys. I've never had the problme myself though.

Ahz,
I didn't start playing until 2 weeks after commercial release, so I'v never seen the beta (I wish I could have seen the Ritiki Invasion!!).
Now that you mention it, I'll admit that I've not seen it recently. Naturaly, I assumed this had everything to do with my um, programing prowess. Considering the vast extent of these skills, fixing it in a patch seem a more likely explanation. It will sure make the binds a whole lot simpler!

ZeroG - THANK YOU!!!

Hey Gnarly, good to see that i was missed!! Any way, I haven't been lurking, just sitting back reading the posts, and, um well, OK, so I've been lurking!!!

Any way, I've got a couple questions for all you gbind guru's our there so:

[ QUOTE ]
One turns the other off automatically.

[/ QUOTE ]

Really? Are you sure? I know I've had some problems where both fly and hover are on at the same time, as a result of the bind coming out of sync. But this may be due to how I've written the bind. I had the same question as ZeroG when I started going through the binds to figure out the logic. Is this 'auto-toggle' feature only active during specific bind paterns? I assume that az's binds work, so there must be something there, I just don't understand the specific conditions that allow it to opperate this way. Any clues?

[ QUOTE ]
But, they do put a "Switching on hover instead of fly" message in your chat box, which I don't think you get if you turn it off explicitly. But I'm not sure on that, as I've long ago turned these messages off to avoid spamming.


[/ QUOTE ]
For the love of god, how, please tell me how!!! And does this eliminte the bind_load_file messages as well? If not, as a side-note for suggested binds, I would love bind_load_file_quiet (or something to that effect). I'd love to can all those messages (after I've de-bugged the code of course!).

Any way, Gnarly, I think you've got it spot-on when saying that the ideal configuration is very user dependant. In truth, I've had very little problem using a variation of the original binds that were restricted to a single key. As I use mouse-look almost all the time, needing multiple keys is very rarely a problem. I have to say, I'm looking forward to your ESDF version of the files. I've stuck with my old files just cause I'm to lazy to keep making the changes as all the new versions come out . I've got a few other bit's thrown in that make my set do what I want, and I'll absolutely add this to any set I ultimately go with.

So, on to the question about a place to get the Dev's attention regarding what the binder's would like to see. I'd say start another thread with DEV in the topic. I think they probably at least glance at any thred with that there, and comment where they believe it is appropriate. If we get no response, then we're probably stuck. Hard-core binding (if you can call it that) is probably pretty uncommon. That said, a list of new emotes come with the update, maybe a couple /commands did as well! I'd start the thread on the general CoH topic. It's probably more likely to get noticed there. If I've got the time, I'll do it myself later, but I've spent enought company time doing this post as it is, should probalby get some work done...

I have to say ditto to really liking what has happened with the evolution of these binds. I saw some of the capability at one point, but Joe, Gnarly and ahzurdan are much better able to put them into action. I'm just glad I was involved in bringing this thread back to active. The set I settled with is only capable of handling two keys pressed simultaneously, but eliminates much of the overhead. Of course, ahzurdan seems to have done it all in about as many files. But hey, I'm in marketing. I just like coding binds as a hoby (yes, I'm sick and need help!).

Any way, I did have some serious stuff to post about:

[ QUOTE ]
But do you know for a fact that binds are saved server side?

[/ QUOTE ]

Yep, the key-bind configuration with any changes is stored server-side with the character. If you sign on from any other computer, your binds will be there. No need to re-enter. But once bound, there is probably little/no need to comunicate with the server. However, as these binds continally re-bind the key definition, there must be constant communication going on. I can't say I've noticed any real changed in performance, but I'm still using my very much toned down binds until you can all settle on something and move on . Actualy, since I've changed the default keys for movement and this seems to be changing faster than Windows, I've given up trying to keep up with the editing the new files till I can figure out which set I want to use.

Any way, kudos to you all. I MAY have something to contribute in the future, but you're all moving a bit to fast for me!!

Wasabi_joe (hot name, by the way ),
Great stuff. Looks like you picked up on the bind_load toggle long before I did! I've been working on a set that will do this, but only up to two keys at a time. Guess I can skip that now...

Any way, I've got a question for you. What is the purpose of the "$$" command on it's own? I know it acts as a seperator between multiple command, but don't know what it does when on it's own. Is this the same as "nop"?

Thanks

Gnarly (and everyone else...),
To use that technique for creating a new chord key, you would start the bind with "+up$$-up$$<the rest of your bind>.

This provides the '+ functionality' to the entire bind, while adding the -up cancels out the move comand.

Well Gnarly, it looks like you and I are really on the same page. I tested that theory a couple days ago, and am most of the way through setting up a fly-bind package that will 'solve' the two-key issue. I've also got it set up so that releasing a key mid-move will not confuse the bind. I'm not quite finished, but it looks pretty similar to yours. I haven't had a chance to test these files yet, but I hope I'll be able to post them this week-end, or early next week after I've had a chance to proove them out.

Also, another possible use for that trick is to effectively create another chord key. You set the key up so that it loads a set of binds to certain keys when pressed, and another set when released.

P.S. Darn you!! I wanted to reveal that sweet little idea!!!

Hm, interesting bit on 4 comands per line. My only argument ot that is my 'reset' key, which is:

lalt+button4 "tell $name, Flight Re-set You are now hovering$$powexec_name Sprint$$powexec_name Hover$$powexec_name Fly$$powexec_abort $$powexec_name Hover$$bind_load_file c:\flybind3.txt"

That single line has 7 commands and works fine, as far as I've seen. I'm reasonably certain that all portions are being executed. At leaset, is will always go into hover, and shut down fly and sprint if they are on. It loads the bind_file (since the mouse4 and 5 buttons work properly from that point), and I get the 'self-tell' feed back.

Any thoughts?

Gnarly,
I think what you've written will do what you've said - BUT, how will you turn of Hover? You'll need another key to do that, or set T to toggle turning that on or off. But, you'll probalby end up with some confusing key conditions. i.e., if you turn off hover manually, at that point, pressing a movement key will turn hover on while holding the key, then move you into flight when you release it (unless you press G first to set the movement keys for ground). You can do it, but it could be messy. You might want to think about having a couple toggles set up for each of these functions if you want to avoid this sort of thing.

The only other comment, on what you've got for the G key, it's powexec_abort, not powexec_name abort.

Oh, and for flying at a 45 deg angle, I was toying with that last night (I just realized it gave you better ground visibility. hey, I only just learned to fly, after all!!).

I aven't tried it, but I would sugges using:

<up 1$$forward 1> using this format will ABSOLUTELY turn that move mode on, and avoid some of the problems coming from having multiple movement keys pressed. i.e., if you are already auto-moving forward, and you use <++forward$$++up>, it will toggle forward off, so you only move up. THEN, you need to bind another key (or toggle bind the same key) with <up 0$$forward 0> to turn movement off.

Sorry Smak, I'm stumped. Everything you've got there looks fine. With the error messge you are getting, I've only ever seen that when the path or file name was wrong, so that's where I'd look. That's not to say that something else won't cause it. If you've done that and they are fine, I don't know what else to suggest.

The only other things I can think of:

Have you sucessfully bound any functions to the mouse buttons before? I've heard some mention about button4 and button5 not being supported by CoH. I don't know if this is hardware specific, or something that has been sloved. Maybe try a couple 'standard' keys just to check?

You do have hover and fly, right?

If you want, leave your e-mail address. I can send you the exact files I use, and you can just modify the path and keys as you need. I must admit, I can't see anything wrong with what is here, so I don't know if that will help.

Not sure what else to say. Sorry.

Mezmro,
Are you using the bind combination I mentioned, or one of the original binds?

If mine, did you put in the 'reset' function? I've found that to be VERY helpful, sicne things can quite easily get out of wack. I'd reccomend using the alternate I proposed (that re-sets to hovering). I made that change, and am much happier iwht it. You can re-set while still in the air. I've gotten into the habbint of hitting re-set after every fight, and just as I log on (as well as any time I see that it is needed). It keeps thing working very nicely.

As for down, there is not reason is shouldn't work, but if you're using my binds, I didn't set it up to shift into fly for the down (x) key. You can change this by dooing the following:

Add this to flybind1, 2 and 4
x "+down"

Add this to flybind3

x "+down$$powexec_name hover$$powexec_name fly"

This should make the x key work the same as the other move keys.

[Edit]
Oh, for the use of multiple move keys, that why I've got the 'fly' mode in there. That allows 'normal' use of any combination of move keys. I'll say, I don't have this problem much (unless I forget to [censored] to 'fly') because i generally only make small positional corrections in combat. Also, using mouse-look (as Curveball put in his key-bind guide, on this forum somewhere) very significantly minimizes the need to use multiple move keys, at least for me.

Gnarly,
Good thought, but I think the length limitation only comes in for the length of a bind file for a single key, not for a complete file. Of course, this has not been tested wither way (to my knowledge). I recall someone having a problem with a very long bind attached to a single key, but that’s it.

In any case, I’m using (almost) the exact same files without problem, so I don’t think it is the file length.

Smak,
Are these a direct cut & paste of the files you have? If so, I saw the following typos:

-In the ‘reset’ bind (lalt+button4), there is a ‘space’ after powexec_abort (before $$)
-In flybind2, you are missing the “ at the end of <space “+up”>

Other than that, I’m not sure what to say. The files look good otherwise.

You said that you can get Sprint to turn on and off, and that you can go into Hover. Is this using the mouse buttons? Have you tried the ‘reset’ button (lalt+mouse4), and does that seem to work (at least, after you correct the above comment)? Exactly when do you receive the ‘unable to load’ error message?

OK, consider the above then here are some things to try:

First, if you were having any problems, you should re-load the base bind file (after correcting the ‘reset’ button syntax, if needed) just to get you back to a good starting point. Remember, after a bind is loaded, it will stay there until overwritten. So, if you left in the middle playing with these and having problems, you could have some fairly confused key configurations.

Next, try each key individually, see what happens, and note EXACTLY when you get the first error message. At that point, scroll back through your chat text and have a look at the bind command that went in. It should be in there.

Judging by what you said (you can get into hover but not fly), look closely at the ‘button5’ line in flybind1 and flybind2. This is what calls the file (flybind3) that will allow you to go into fly-mode). Then, look very closely at the name of flybind3.txt to be certain that you’ve got it spelled correctly. That seems to me to be the most likely problem.

If this doesn’t work, let me know the answers to the above questions, and I’ll see if I can come up with something else.

Good luck!

Smack,
Take a close look at the actual name of the root file and what you are typing. Other than that, I'm not sure what to tell you for the initial file load.

As for the rest, be certain that the file path and file name for all the sub-files is correct in each of the files. Have you changed the path in flybind1-4 to accomidate where you have put them? Also, if you didn't see it, check out the post right after mine where Fishie mentioned (an I specified afterwards) I had the wrong file name on my post in a couple spots.

I realize this is a fairly obvious thing to check, but that is exactly what the error message is suggesting as the problem.

Good luck!

Thanks Fishie. I see what you mean. This was taken from my 'development' foulder on my lap-top, not the working file on my gaming computer. I thought I'd made all the needed corrections.

All, the corrections that need to be made are in flybind1.txt and flybind2.txt. The last file reference should be flybind3.txt, not flybind3b.txt or flybindb3.txt.

Incidentally, the alternate re-set key I proposesd also works quite well, and I've switched to that in my config. Much better to be able to re-set without having to land (or come crashing to the ground!).

OK, I’ve just got my first toon (on Virtue, name of, well, Blue Volt!) to 14th level and I must say that I LOVE flying!!!!

First, to Jade_Dragon and Synabass, mucho kudos to both of you. I would not have come up with the bind I’m about to pass on without seeing what you had done, so in the end, I take very little credit for it. I’ve been reading the bind threads for ages, and had been dying to try out these binds. I thought they were both VERY clever. I thought it fantastic to have the ability to automatically up-shift and down-shift through walk/sprint/hover/fly (I even modified JD’s bind for walk/sprint/hover when I first became air-borne). When I saw Synabass’ bind, I absolutely knew that I would be the one running out of end ‘cause I forgot to switch back to hover in the middle of a battle. Being the type of person that I am, I always want to have my cake and eat it to, and I really had that feeling here.

Using the EXCELENT binds provided here by both Jade_Dragon and Sinabyss, I combined them into a single bind-set so you CAN have it both ways, at least to some extent.

First, let me tell you a bit about my default set-up, as you will see a number of changes to the default key pattern from what you may use:

1. I’ve take to using the mouse-look move bind that Curveball put in 1.1 of his bind guide, so you will see some of the bind geared around that.
2. As a touch typist, I’ve 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. Again, this was suggested by someone else on these forums. Apologies for not having his/her name to credit.
3. I’ve replace ‘autorun’ with ‘++forward’ (keyed to ‘T’, originally on ‘R’). As far as I could tell, autorun would not work in the air, where ++forward works in air or on ground.
4. I use mouse button 4 and button 5 to control switching between sprint/hover/fly/walk
5. All my bind_files are stored in c:\cohkeybind\. You can obviously substitute what ever path you wish to use.

OK, here are the bind files that I use, essentially set up just as Jade_Dragon has done:

First, I’ve got a ‘master’ bind file that covers my basic key set-up, from which I launch a number of other binds (including this one). Into that file, I add the following lines:

lalt+button4 "tell $name, Flight Re-set$$powexec_name Sprint$$powexec_name Hover$$powexec_name Fly$$powexec_abort$$bind_load_file c:\cohkeybind\flybind1.txt"

button4 "tell $name, Sprinting$$powexec_name Sprint$$bind_load_file c:\cohkeybind\flybind2.txt"
button5 "tell $name, Hovering$$powexec_name Hover$$powexec_name Hover$$bind_load_file c:\cohkeybind\flybind3.txt"

This sets up the initial key settings, to make the bind work. I’ve also added the ‘Tell’ to provide some feedback to you, so you know what ‘mode’ you are in, as well as a re-set key to help out when you get knocked out of the air, or confuse the bind by hitting a ‘bad’ key combination. I found that to be necessary after a very short amount of time…

OK, and here are the other four files.

flybind1.txt:

button4 "tell $name, Sprinting$$powexec_name Sprint$$bind_load_file c:\cohkeybind\flybind2.txt"
button5 "tell $name, Hovering$$powexec_name Hover$$powexec_name Hover$$bind_load_file c:\cohkeybind\flybind3b.txt"

e "+forward"
s "+left"
f "+right"
d "+backward"
space "+up"

flybind2.txt:

button4 "tell $name, Walking$$powexec_name Sprint$$bind_load_file c:\cohkeybind\flybind1.txt"
button5 "tell $name, Hovering$$powexec_name Sprint$$powexec_name Hover$$bind_load_file c:\cohkeybind\flybindb3.txt"

e "+forward"
s "+left"
f "+right"
d "+backward"
space "+up"

flybind3.txt:

button4 "tell $name, Sprinting$$powexec_name Sprint$$powexec_name Hover$$bind_load_file c:\cohkeybind\flybind2.txt"
button5 "tell $name, Flying$$powexec_name Fly$$powexec_name Hover$$bind_load_file c:\cohkeybind\flybind4.txt"

e "+forward$$powexec_name hover$$powexec_name fly"
s "+left$$powexec_name hover$$powexec_name fly"
f "+right$$powexec_name hover$$powexec_name fly"
d "+backward$$powexec_name hover$$powexec_name fly"
space "+up$$powexec_name hover$$powexec_name fly"
lshift+space "+down$$powexec_name hover$$powexec_name fly"

flybind4.txt:

button4 "tell $name, Sprinting$$powexec_name Sprint$$powexec_name Fly$$bind_load_file c:\cohkeybind\flybind2.txt"
button5 "tell $name, Hovering$$powexec_name Fly$$powexec_name Hover$$bind_load_file c:\cohkeybind\flybind3.txt"

e "+forward"
s "+left"
f "+right"
d "+backward"
space "+up"
lshift+space "+down"

In all cases, you get a ‘self-tell’ so you know what movement mode you are in.

When you are in ‘hover’ mode, you can use the directional movement keys, and they will shift you into flight, using the bind developed by Sinabyss. You still have the problem with using multiple direction keys simultaneously. However, by using mouse-look most of the time (as I do), this is rarely a problem.

For times I am not concerned with the end conservation and just want to free-fly (such as outdoor, non-combat movement), you can shift into a ‘normal flight’ mode, where you can use as many movement keys as you want.

Last of all, on the re-set key. I find that this is pretty necessary, as the bind can get mixed up fairly easily (knocked out of the air, etc). The re-set key I’ve got now will shut off all movement and re-set the bind. It’s occurred to me that you may be in the air when you need to re-set, so shutting off flight may not be such a good idea. I’ve not tried this yet, but do think it will work (and plan on giving it a try soon). Try changing the reset key to the following:

lalt+button4 "tell $name, Flight Re-set You are now hovering$$powexec_name Sprint$$powexec_name Hover$$powexec_name Fly$$powexec_abort$$powexec_name Hover$$bind_load_file c:\cohkeybind\flybind3.txt"

This should re-set you quite nicely, and leave you safely in the air without crashing to the ground!

Well, sorry this was so long, and I again extend the overwhelming majority of the credit to Jade_Dragon and Sinabyss.

Let me know what you think.

CoCoNoNo,
I am also in the office, so also can't test .

I suspect that the move commands will over-ride the follow command. Not sure what it will do. I think it will simply have you doing a circle strafe on the natural focal point (as if you were holding the turn/move left keys), but may just take the last command. I'm pretty sure that the move commands stack in a bind, but I'm not positive.

SV - Here is an exerpt of what I meant. but I think you've probably seen it already.

[ QUOTE ]
"C:\program file" is also "C:\progra~1" under windows. It's called msdos compatibility

So, try :
/bind c "bind_load_file c:\Progra~1\City~1\binds\myFly.txt"

[/ QUOTE ]

Going back and looking, I think you've probably seen it already as you've also posted there... In any case, I thought that this problem may be what you are seeing as well, though I've not had any similar problems my self, and I don't know if this is OS dependant, but thought it may be worth a shot.

Now, looking at the command you've put in your last post:

[ QUOTE ]
NUMPAD9 "bind_load_file c:\kb/$name". The character named files are all sitting in c:\

[/ QUOTE ]

If they are all sitting in the C:\ directory, shouldn't the command be:

NUMPAD9 "bind_load_file c:\$name"

As you've typed it here, it suggests that the files would be in a foulder named "kb" in the c:\ directory, though one of the slashes is going the wrong way for that. Was this just a typo here, or a cut and paste?

In any case, I've gotten the same error message when I mis-typed the file path, so this could fix your problem.

Hope it helps!

Supper Volt,
It may not be the syntax. You may be having a problem with the name being to long to recognize all the characters. This problem is talked about on the "post your binds here" thread. Try shortening the file name to "sv" or something with 8 or fewer characters.

I have to admit, I've not seent this problem using file names quite a bit longer, but I've got the extension on all of them. I don't know if that will make a difference.