Blue_Volt_NA

Yes, 'soon' is far to informative. A better word would be 'eventually'.

Weaver,
I don't know that there is a bind for what you want to do. However, I would suggest doing the normal bind_save, and then re-name the file to what ever you want. You won't be effecting any other character or default settings, as the bind_save file is never actually used, unless you do a bind_load command. And, if you've gotten to the point where you are creating custom settings by AT or character, you probably will never need to use bind_load. It will always be bind_load_file.

Volt

Hey Justice Blues, what you are looking for can be done. Try the following:

/bind space "+up$$powexec_name combat jumping"

that should do it.

Just check that the power name is correct. Can't remember if it's combat jump or combat jumping for the binds...

Volt

[ QUOTE ]
OK, I admit it, I've been playing some WoW.

I know some of you have, too.

Thing is, the Mouse look on WoW is exactly the opposite of the mouse look on CoH. Anyone else find that annoying? It takes me several minutes to switch gears from one to the other. What I'm talking about is, when you hold down the right mouse button and move the mouse, it cahnges the view. In CoH, if you hold down the right button and push the mouse forward, it rotates teh cammera DOWN. In WoW, it rotates the camera UP. And vica versa.

So the obvious questiuon is: Can teh mouse look in CoH (rbutton) be reversed so that pushing it forward looks UP, and pulling it back looks DOWN?

Before anyone flames, YES, I'm asking the same questions at WoW about changing the mouse look there.

A little help, O gurus of the bind?

[/ QUOTE ]

Dread,
You need to find a setting in WoW (Or CoH, depending on which configuration you want to keep) called "Invert Y Axis". That should change the way it responds.

Volt

Hwy JusticeBlues, you could just as easily bind any single key to (for example):

u "bind_load_file c:/bind/name1.txt"

So, you bind the 'u' key to load the bind file for the given character. YOu do that once for each character, and you don't need to change it ever again. You don't need to bind a different key for each character. It can be the same key.

Volt

Voodoo,
I don't know that anyone actually got this to work. I think that there are issues with the length of the hero name, the presence of spaces, etc.

However, I remember this conversation ending with, "why whould you want to?" When you load a set of binds for a character, those binds are saved on the server with the character. So, there is no need to re-load binds when changing the character you are playing.

Now, is there a use for this that you have in mind that I am missing?

Volt

Hey Panther, actually, no, it doesn't matter. Having the '-down' counteracts the '+down', so no movement occurs.

Volt, erm, the Blue one, that is...

Not sure if you've seen this but, actually, it IS possible to activate multiple powers with a single key-press (not a single bind). It works using the '+' prefix, the details of which I learned from a wize old bindster that shall remain nameless

The way it works is you create two bind files such as:

bind1.txt
b "+down$$-down$$powexec_name build up$$bind_load_file bind2.txt"

bind2.txt
"+down$$-down$$powexec_name aim$$bind_load_file bind1.txt"

With the '+' functionality, I reasoned that what it actually does is execute the key functionality on both the press and release. By loading a second bind on the press, you can execute that bind on the release, and then re-load the first bind. It's really just a toggle bind that toggle's mid-keystroke. By using the auto power command, you can get that up to three powers in a single press. This concept is actually the key to the speed-on-demand binds that Grotus and others have put up on that thread. By the same token, you could also string multiple sets together, and execute 4 powers in 2 presses, etc.

Oh, and using '+down$$-down' gives you the functionality without actually making the character move.

Let me know if you have any questions.

By the way, what bood are you writing?

Volt

There is a 'restore defaults' in the options section. That should do everything, but I've never used it...

Sillvanor,
The SoD files do not affect the 'turn' keys in any way. Only the actuall movement keys (forward, back, up, down, slide left, and slide right). You shouldn't have any problems.

Volt

OK. It’s Monday, I finally got myself completely out of debt after nearly a complete level of having some level of debt. So, I’m happy, and that means I feel like being helpful!

So:

Graystar,
There is a little trick you can use to get around the problem you’ve got with the long bind command. Break it up into two binds that are toggled on the same press of the same key. As an example:

upend1.txt
numpad9 "+down$$-down$$Local <color #FFFFFF><bgcolor #999999><border #000000><Scale 1.5> *dialog*$$emote victory$$bind_load_file c:\coh\binds\Secret_identity\upend2.txt”

upend2.txt
numpad9 “+down$$-down$$Local <color #FFFFFF><bgcolor #999999><border #000000><Scale 1.5> *dialog*$$cc 0$$bind_load_file c:\COH\Binds\Secret_Identity\upbegin.txt"

The ‘+down$$-down’ is just to give the bind the ‘toggle on press and release’ functionality. On the press, it will operate the first part bind and load the second. On release, it will operate the second, and load the next step in your bind sequence.


Vincent,
From the looks of it, the bind you’ve put up should do exactly what you want it to. The ‘+’ prefix gives a ‘start on pres, stop on release’ functionality to a command. Changing this to ‘++’ gives a ‘start first press, stop on second press’ functionality.

The only other thing I’ll say is that there seems to be some ‘issues’ (at least for me) with using multiple ‘+’ triggers in a single bind. I find that it can be slightly buggy, but not overly problematic. Give that a try and see how it works. If you have problems, here is something else to try –

Create the following two text files and place them in a folder called ‘bind’ located in the root c:/ directory (you can change the file path if you want):

speed1.txt
w “+down$$-down$$forward 1$$mouse_look 1$$powexec_name Super Speed$$bind_load_file c:/bind/speed2.txt”

speed2.txt
w “+down$$-down$$forward 0$$mouse_look 0$$powexec_name Super Speed$$bind_load_file c:/bind/speed1.txt”


Now, type ‘/bind_load_file c:/bind/speed1.txt

The difference here is, by using the ‘1’ suffix, you know that you are turning the function on. By using the ‘0’ suffix, you know you are turning it off. It may seem overly complicated, but it avoids the duplicate ‘+’ commands in a single string. Again, try the bind you’ve already proposed first. Us this as a backup if that doesn’t work the way you wanted.

OK, I hope this works for everyone!

Volt.

Graystar, there is a limit to the length of a bind. I think it's someting like 256 characters. So, it's pretty large. I know you've checked this, but the message you've stated suggests an issue with file name, path, etc. A bind that is to long will load, but will be truncated, with the last bits simply removed from the bind. I can tell you that from experience. Post your binds, and I'll have a look.

By the way, this may just be on your post, but the command is bind_load_file, not load_bind_file as you've got typed here.

Volt

Yeah. Based on what Kalen said, you can probably just move the files off the c:/ dirrectory and into the CoH folder, and then go back to the way you were doing it before. Or, you can do what I suggested, but you well still need to go to CoH directory for the keybinds.txt file.

Volt

SBeaudway,
The bind_load command loads the specific file (named keybinds.txt) into the current toon. The keybinds.txt file is created by using the bind_save command. Bind_save will save the key bind configuration for the toon that is active when the command is used, and will OVERWRITE any previous file. So, if you have the key-bind patern for another toon, you must have re-saved the keybind.txt file from that toon.

What you need to do is create a seperate file for each toon with different bind configs (and re-name them). Then use the bind_load_file commenane to load that file.

I would reccomend creating a folder called 'bind' located in on your root c: directory. For a file called 'blue_volt.txt' located in that folder, the commen would look like this:

/bind_load_file c:/bind/blue_volt.txt

If you've already overwritten the keybind.txt file with one toon, and have already loaded that into another toon, I don't think there is any way to restore any custom key-binds you may have had. My only suggestion is to do a re-set (somewhere in the options menu) and re-load any customer set-up you had.

Volt

It has something to do with changing the function of the key in the middle of executing the bind. I don't remember the specifics. I just remembered that the bind-load should always be at the end from my newb bind days...

PantherShade,
The first thing I would try to do is to move the bind_load portion of the bind to the very end. Make that the last thing in the line.

Otherwise, everything seems OK.

If that doesn't work, let me know if it changes anything.

Volt

DJCKidd,
I know exactly what you mean. I have the same problem using either build-up or aim just prior to my sniper blast as well. BUT, I think this is a bug that has been fixed in the next issue. I've been on the test server a little, and it apears that you can now cue the sniper blast immediately after firing off either aim or build up. I didn't really test this, but I did notice that after going to the test server, then back to the regular server. So, don't give up hope yet!

[ QUOTE ]
<ul type="square">
numpad3 “+down$$-down$$powexec_name maneuvers$$bind_load_file c:/cohkeys/assault.txt”[/list]
Thanks again for your help.....

[/ QUOTE ]

Yep, that will do it! Most people don't seem to have a 'deafult' key-bind file, so I don't normally suggest that (but it is my best suggestion on how to do it..).

The only thing to watch out for is if you manually activate one of the powers through the power tray. If only one of them gets activated that way, you will have the powers our of synch. That is easily corrected by 're-synching' the powers using the power tray keys/icons.

Good luck.

Oh, and your welcome!

Hey DJCKid,
I don't think what you've got there will work. When you execute the macro, Maneuvers will activate. Then, you will probably get some kind of error message on the bind_load. I'm not sure on that part. Running the bind_load_file command will not actually execute the sequence stated in the file. It simple binds keys as defined by that file. In fact, the devs were pretty careful about ensuring that you could not execute more than one power with a single key-press. However, they were not perfect about preventing it.

Try this:

<font class="small">Code:[/color]<hr /><pre> maneuvers. txt
p “+down$$-down$$powexec_name maneuvers$$bind_load_file c:/cohkeys/assault.txt”

assault.txt
p “+down$$-down$$powexec_name assault$$bind_load_file c:/cohkeys/maneuvers.txt”
</pre><hr />

Create these files in your cohkeys directory, then type:

<font class="small">Code:[/color]<hr /><pre> /bind_load_file c:/cohkeys/maneuvers.txt </pre><hr />

on the chat line. Now, when you press the 'P' key, both powers will activate if off, and deactivate if on.

The '+down' at the beginning of the command sets the operation such that the command is executed on both the press and release of the key. By performing the bind_load, you change the function of the key mid-stream, allowin a second power to be activated.

Hope this helps.

Volt

Hey Gnarly,

em/ salute

Sorry to see you go. Good luck out there!

Well, simply put, you can't activate two powers in a single bind. You can only toggle between the two, as you've seen. The devs designed it that way to prevent botting of complicated combat sequences.

Now, if you want to know how to get around that, read my last post. The one right above your post...

Yep, it is possible. Here is a set that will activate build-up on key-press and power thrust on release.

hchange1.txt

lshift+u "+up$$-up$$powexec_name build up$$bind_load_file c:/bind/blue_volt/hchange2.txt"

hchange2.txt

lshift+u "+up$$-up$$powexec_name power thrust$$bind_load_file c:/bind/blue_volt/hchange1.txt"

Of course, you will probably need to change the buind-load path. This is straight out of my files. The trick is in the +up$$-up at the beginning. The +u gives the functionality to execute on press and release, and the -up prevents it from actually making you move.

Now, you can change the file names, paths and powers called to what ever you want.

Good Luck.

Volt

Hey Blue, good color choice

To answer your question, try this. Type:

/bind {key} "follow$$powexec_name fly$$powexed_name fly"

on the chat line. You DO need to keep the quotes, and replace '{key}' with the key you want to do the comand. This will turn on fly if off, and will leave it on if it is already on (that's why the double command).

Hope that helps!

Volt.

Regretably, yes. I'm affraid that is the only answer that has been found so far...

Curveball Dude! You taught me (almost ) everything I know about key binding. THANK YOU!!

So, it is with great hesitancy (but some certainty, none the less...) that I dare to contradict the Great One.

I think you've got the +/++ command functionality backwards. The '+' trigger will act such that the command is active only while the key is pressed and held, while the '++' will act as a toggle activating on one press and de-activating on a subsequent press.

Don't worry, I'll chalk it up to early in the morning and not enough coffee.

EvGen, the trick you are talking about works like this: by using a command with a '+' trigger at the start of a more complex bind, you add a 'double execute' functionality to the key. i.e. it will execute the function tied to that key on press, and again on release. Using +down$$-down adds this functionality without actually affecting the movement of your toon (due to the -down), but still passes the '+' functionality on to the rest of the bind.

There are a number of things you can do with this, such as changing the function of a key mid-press if you include a bind_load_file command within the key bind.

Now, what you have asked is actually how it is already working. A basic 'powexec_name' will only trigger a power when the key is pressed. I suspect the proble you are having is related to the key pad just as you've already figured. That is, it is auto-repeating very quickly, causing the power to double-trigger. With a toggle power such as hover, that will toggle it on and off again very quickly.

I hope that this helps you a bit!

Volt