ahzurdan

It looks like you just changed "sprint" to "primary".

What you needed to do was:

Change powexec_name Sprint to powexec_name %primary%

Use the "powexec_name" in the Replace, and keep the "%" signs.

The new version of the binds is up on my website.

[ QUOTE ]
[ QUOTE ]
Start with the basic batch file from Falstaff's page and perform the following change:

powexec_name Sprint changed to powexec_name %primary%



[/ QUOTE ]

Do you mean below the ::::::::NO CHANGES NEEDED BELOW THIS POINT:::::::: part find all lines like (echo %activate% "powexec_name Hover$$powexec_name Fly$$powexec_name Sprint$$powexec_name %sprint%$$bind_load_file %directory%\run\autorunxyz.txt" >>%directory%\fly\autoflyxyz.txt) and change anywhere it says "Sprint" to "primary"?

Like this?- "powexec_name primary$$powexec_name %primary%"

Like I said before, I am retarded when it comes to /commands in CoH.

There are alot of command lines in that .bat file with the word "sprint". do I change them all?

[/ QUOTE ]

Yup. Change them all. I would suggest using WordPad or NotePad. Just do a "Replace All".

My binds were originally set up to use SuperSpeed if you had it, and Sprint if you didn't. Falstaff made a change to allow you to replace SuperSpeed with whatever power you wanted, but it left Sprint as it was.

What these changes will do is allow you to specify a power to use instead of Sprint. Since we are changing the way it works throughout the binds, we need to do a "Replace All".

Sound good?

Actually, I am going to be putting up a new version of my binds a little later today. I have made some updates to fix some small things, and I also made the following changes:

Instead of specifying run powers in the binds themselves, they now toggle on and off the first power in the second tray. I just swap Sprint and SuperSpeed in there when I need to. I did this as I wanted my binds to use Sprint when indoor, and SuperSpeed when outdoors. This also allows me to have SuperSpeed be manually toggled for those situations where you are using the agro radius reduction on SuperSpeed to attempt single pulls. This would help in your situation as you could just move your prestige power to this slot to use it with the binds.

I also changed the "default" key arrangement, so that F still toggles Hover on and off (for catching myself when jumping off things), and TILDE still being FOLLOW.

[ QUOTE ]
[ QUOTE ]

There is no autoruny.txt file
(autorunxyz.txt, autorunxz.txt, autorunyz.txt and autorunz.txt)

In ALL the "run.txt" files it puts the line- "powexec_name Sprint$$powexec_name Prestige Power Surge"

And its still not working in game

[/ QUOTE ]

Ok, my bad on the Y part, I forgot which letter he used for each axis. Anyway, that bind looks correct, to me, except if the binds turn off the prestige power the same way (with only a single call to surge AND sprint) as it'd turn Sprint on when you stop, and surge on when you're moving.

I better leave this one to Falstaff and Ahzurdan

Gnarly

[/ QUOTE ]

Actually, with the way that it is coming out in your examples it should be working.

Here is what I would suggest:

Start with the basic batch file from Falstaff's page and perform the following change:

powexec_name Sprint changed to powexec_name %primary%

then change:

::set sprint=%Prestige Power Surge to: set primary=%Prestige Power Surge

Then make whatever changes you want for key assignments and such, and run the job.

When you get into the game perform the following command while standing still with no travel powers on:

bind_load_file c:/coh/binds/run/norun.txt

That should fix you. If you are still having problems post the contents of your NORUN.TXT file and I will take a look at it.

[ QUOTE ]
Hey Ahzurdan, glad to see you're still lurking around between WoW sessions

Gnarly

[/ QUOTE ]

Keeps me from falling asleep at the office.

[ QUOTE ]
I’ve been using 'Gnarly's Speed on Demand Binds' for a week or more and I REALLY like them, but why-oh-why do I keep dropping out of air for no reason at all?

I'm not talking about the known 'feature' whereby if you try to use a power or inspire at the same time as you move while flying, I am talking about times when I am just moving about, usually manoeuvring to get a good angle on mobs, and BAM! I fall out of the air and straight into their laps!!

It’s happened to me six+ times so far this afternoon and it’s starting to get REALLY annoying!

[/ QUOTE ]

As near as I can tell this happens on occasion for all versions of the fly binds.

In my own use of the binds I have encountered this problem in times of high lag. My general observations are that this happens when you stop moving, which turns off FLY and should turn on HOVER. What I am encountering is when FLY turns off there is a lag before HOVER turns on. This generally results in me hitting the ground and then immediately having HOVER kick up.

If you are encountering something similar to what I just described, then there doesn't seem to be anything that can be done. These binds are VERY-VERY touchy when it comes to lag related issues.

[ QUOTE ]
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.

[/ QUOTE ]

I got the file, but I haven't had much of a chance to look at it. I will get to it though, I promise.

I just got accepted to the WoW beta (woo!), so my free time just become rather scarce. It may be a bit.

[ QUOTE ]
Ahz, I modified quite a few lines in your binds in an attempt to make them more solid. Know that some times the binds cause problems after porting? Yah that problem seems solved now, even if someone get itchy fingers and toggles extra stuff on during the movement, the bind will automatically reset itself to normal. Not sure how I can send it to you for checking......you have MSN or something?

[/ QUOTE ]

You can email me a ZIP file at:

ahzurdan -at- yahoo -dot- com

[ QUOTE ]
Ahz, I did as directed with the batch file for Joe's binds, and it didn't work at all.
Blastoff didn't work properly (just jumped).
When hover turned on, sprint continued to come on.
Pressing F toggled whether sprint would come on, but would not disable hover.

Suggestions?

[/ QUOTE ]

Yup. I missed two things, which you will need to do after the find/replaces already listed:

powexec_name %sprint%$$powexec_name fly$$powexec_name fly changed to powexec_name %sprint%$$powexec_name hover$$powexec_name fly

%activate% "+down$$powexec_name fly% changed to %activate% "+down$$powexec_name hover$$powexec_name fly%

Each of thes updates should change a single row, but once done it should get you up and running. As with the other, I am looking at this at work, so I am unable to actually test it out. Let me know if you hit more problems.

[ QUOTE ]
Sigh, I am having some major problems with getting the Ahzurdan binds at Falstaff's site and Gnarly's recent bind update to work properly, anyone has the same problems? Cos I don't think its just me.

[/ QUOTE ]

What kind of problems are you encountering?

[ QUOTE ]
Oh yes Azhurdan, your bind can be broken by pressing 2 opposite direction keys at the same time and letting go together. This causes the hero to have sprint on even when standing still. However, the binds reset themselves nicely if you move so its not a big problem at all. Just to keep you updated though, and thanks for the nice work.

[/ QUOTE ]

I ran into this. This isn't really a problem with the binds so much as it is a limitation of the binds, in that the game actually attempts to do both key-releases at the same time, and the binds cannot be written in a way that accounts for that.

Thanks for reporting problems as you find them, but I can't do anything about this particular one as things currently stand.

[ QUOTE ]
[ QUOTE ]
Great Binds!!! My character just got fly today and these are by far the best thing to happen to flying characters!!! Thanks to everyone for all their work ... simply amazing.

Ahzurdan, I have noticed one thing with your latest version (linked in your post 2 above this post - 6:08pm). I've come up with steps to recreate it and listed them below:

1 - While not flying or sprinting, Ctrl+R to get into the "autofly" mode.
2 - Press 'R' to start autorun (autofly)
3 - While autoflying, hold down the spacebar to elevate (typically used to get a nice view of the cityscape below without losing altitude)
4 - Release the spacebar
5 - Press and release 'R' to exit autofly mode ...

After step 5, my character is still moving forward (autorun/autofly still active), but fly is switched to hover. From this point forward, fly/hover are reversed (CTRL+R 2 times to repair).

Sorry to bring this up .... otherwise they seem perfect.

Thanks!

Shady

[/ QUOTE ]

I can't see any problems with the binds here at work. I will have to test this out tonight when I have a character on, and see if I can recreate your problem. I'll keep you updated on what I figure out.

[/ QUOTE ]

Wasn't able to actually isolate this problem to something wrong with the way the bind was set up, but I was able to recreate the problem.

I did some narrowing down, and finally determined that for some reason ++FORWARD wasn't being toggled when it should have been. No idea why.

Anyhow, I changed the binds a bit and fixed the problem. I used an explicit turn on/off of FORWARD. Updates, as always, are here.

[ QUOTE ]
Hey, Ahz, I've been using your bind for sometime now, and I like it, but I just got superspeed and i noticed that if I stop, I revert to sprint mode, which i don't quite want to do, since this character's quite an endurance hog. Is there anyway to change that? perhaps I loaded the bind incorrectly?

[/ QUOTE ]

If you are using an older version (I put up a new one yesterday) I believe that this has been fixed. Please try the newest version, and if you still have the same problem let me know.

[ QUOTE ]
Great Binds!!! My character just got fly today and these are by far the best thing to happen to flying characters!!! Thanks to everyone for all their work ... simply amazing.

Ahzurdan, I have noticed one thing with your latest version (linked in your post 2 above this post - 6:08pm). I've come up with steps to recreate it and listed them below:

1 - While not flying or sprinting, Ctrl+R to get into the "autofly" mode.
2 - Press 'R' to start autorun (autofly)
3 - While autoflying, hold down the spacebar to elevate (typically used to get a nice view of the cityscape below without losing altitude)
4 - Release the spacebar
5 - Press and release 'R' to exit autofly mode ...

After step 5, my character is still moving forward (autorun/autofly still active), but fly is switched to hover. From this point forward, fly/hover are reversed (CTRL+R 2 times to repair).

Sorry to bring this up .... otherwise they seem perfect.

Thanks!

Shady

[/ QUOTE ]

I can't see any problems with the binds here at work. I will have to test this out tonight when I have a character on, and see if I can recreate your problem. I'll keep you updated on what I figure out.

[ QUOTE ]
Hey Ahzurdan, just wondering whether you could make an adjustment to the "+up" key when on the ground so that those guys who have super jump can activate it when they press that key and it auto shuts off when its released. Then this bind can be upgraded to the "Best travel bind EVER!!!" lol.

[/ QUOTE ]

I have actually considered this. There are two problems.

1. You activate SUPER JUMP everytime you jump. Most people use COMBAT JUMPING when they aren't going long distances, and I can't tell the difference between a short journey (jumping to the second level in a mission) and a long one (crossing a zone).

2. If you activate SUPER JUMP with the +UP key, the character will actually jump and then turn on SUPER JUMP. Your first jump will always be a normal jump.

I find it easier to just pick a key that is not already part of a bind, and bind the following to it:

/bind [insert key here] "powexec_name Combat Jumping$$powexec_name Super Jump"

This will toggle between the two.

[ QUOTE ]
Ahzurdan,

I switched to your binds today because the version of Wasabi's that I was using didn't likr a character having hover without fly.

I'm really missing mouselook, though. Can you tell me how to add it?

[/ QUOTE ]

Honestly, it would be easier to add the functionality to Joe's binds that would allow for HOVER to come on when you don't have FLY.

Download Fallstaff's Batch file for the latest version of Joe's binds from his site. Extract it, and then edit the batch file with Notepad.

Do the following three replace alls, in this order (cut and paste to make sure you don't mistype):

powexec_name sprint changed to powexec_name %sprint%

%activate% "powexec_name fly changed to %activate% "powexec_name hover$$powexec_name fly

and

%activate% "powexec_name %sprint%$$powexec_name fly changed to %activate% "powexec_name %sprint%$$powexec_name hover


Then save that and run the batch job. Everything will be the same in Joe's binds except that, if you don't have FLY, HOVER will be used instead.

****************************************


If you don't feel like messing with Joe's binds, then the item that you are going to want to add is to mine is Mouselook 1 to turn it on, and Mouselook 0 to turn it off.

The general way that the files are set up is: when you are in NORUN or NOFLY every POWEXEC_NAME command is used to turn a travel power on, and in all the other files POWEXEC_NAME is used to turn the power off.

You can edit the files and just add Mouselook 1 after the power coming on, and Mouselook 0 after the power turning off.

<font class="small">Code:[/color]<hr /><pre>For example, in NOFLY.TXT:

a "+left$$powexec_name Fly$$powexec_name Fly$$bind_load_file c:/coh/binds/fly/flyx.txt"

would become:

a "+left$$powexec_name Fly$$powexec_name Fly$$Mouselook 1$$bind_load_file c:/coh/binds/fly/flyx.txt"</pre><hr />

Just add the MOUSELOOK command before the BIND_LOAD_FILE command, and you should be good. This should allow you to set it up so that mouselook only comes on when you want it to. You will just have to figure out when you want it on, and when you don't.

Fixed some more follow problems. Updates are here.

[ QUOTE ]
Hey Ahz,
I have run into a problem w/ the fly binds. when I hit autorun w/ the fly binds on I stay in hover mode. its not swithing to Fly. I did a lil modfiying to it, because I dont need the run binds. Is the autorun feature depended apon the run binds? If so, can it be modified to work w/o it? everything else works great, just have the lil prob w/ autorun part.

[/ QUOTE ]

This was actually a bug. It has been fixed in the newest version, which (as always) is available here.

You might try making the executable available by itself, with all the other pieces seperate. That way each person would only need to download the DLL files to run the executable once, instead of over and over for each update.

Not sure how long geocities takes to reset your load limit, though.

[ QUOTE ]
ahzurdan, I played with your binds last night and love them! I'm really thrilled by your brilliant axis concept.

I think I found another minor error. In both followfly files take a look at the F bind. I forgot to test toggling flight while following.

[/ QUOTE ]

Fixed this problem. I apparently got the POWEXEC statements all backwards. This should be fixed now. I also removed file FOLLOWRUN.TXT, as it was no longer being used. These updates have been posted to my site. I have added date/time of the last upload on my site, for version tracking purposes. I can just never tell whether it should go to version 2 or 1.1

Fallstaff's batch job is excellent! Use it!

I also stuck up a second version that I like, which uses POWEXEC_ALTSLOT instead of POWEXEC_NAME. Just put Sprint, Super Speed, Hover and Fly in slots 1-4 of your alternate power tray. What this will allow is, if you want an indoor version that doesn't toggle Sprint or Super Speed just put together another tray where slots 1 and 2 are empty, but 3 and 4 have Hover and Fly, and then switch your alternate power tray to display that other tray when you enter a mission. I will be testing this version for the first time tonight, so there may be some issues.

I have officially given up on trying to implement the "Blastoff" and "Setdown" functionality within my binds. I apologize if anyone finds this particularly irksome. For those that are interested in that (and the mouselook) functionality, I have every faith that the new set that Joe has said he is currently working on will contain both of those, and probably blow us away.

I am pretty happy with the way that my binds are working right now, so until I see something go by that makes me want to update my binds, they should be stable for a bit.

Let me know if you find any more problems.

CONTROL+R should already do that. First time it should put you back to the defaults, and then if you do it again it will reload NORUN.TXT.

I've never been able to get Hover on at the same time as Fly. Could this have been during beta, or something that is true now but wasn't true when you experienced your problem?

I believe that the Devs set it up (either originally or with a patch) so that there was no way to get both the defense bonus of Hover and the speed of Fly.

And I would also like to know how to stop the spam.

Slow day for me too, actually.

I actually enjoyed the banter back and forth. Kept me looking at the binds in different ways, and from falling asleep in my cubby. I am still looking into both the issue with jump being used faster than the keybinds can reload themselves, and the "Blastoff"/"Setdown" functionality.

On a different note, if we were gonna post something along the lines of a "Bind Issues/Wishlist" with the intent of getting Developer feedback, where would you all suggest we put it?

I think we really need to make them aware of how the BIND_LOAD_FILE command is actually being used by the community, and get their feedback on the network traffic that the command seems to spawn.

I would also really like some new Slash Commands; such as TURN_OFF_ALL_ACTIVE_POWERS, and TARGET_TEAM_NEXT.

Just not sure which forum has the best chance of Developer response.

I'm not having problems with it; it works. I was just explaining why I did it that way.

[ QUOTE ]
Thank you for the clarifications, ahzurdan. There was another thing I forgot to ask earlier. When reading your files it seemed that they assume +forward to have an inherent autorun 0 and not +backward. I thought it was the opposite. +forward does not turn off autorun while +backward does.

For instance autorunz has s toggle autorun while w does not but in both cases you are transferred to normal run files. In my current binds I added autorun 0 to my w bind.

[/ QUOTE ]

When I was testing this out I found that both +FORWARD and +BACKWARD turned off ++FORWARD, but for some reason when you used +BACKWARD to turn off ++FORWARD instead of immediately running you backward it would stop you entirely until you let go of the +BACKWARD key and hit it again. Adding the ++FORWARD fixed that for me.

[ QUOTE ]
In gaming I've run across the idiosyncrasy that autorun does not turn off follow. This caught me twice last night. I tried adding follow 0 to my autorun bind but it did not work. Obviously I don't want an indiscriminate follow toggle in my autorun.

In your followrun R toggles autorun and loads autorunz, but follow is still on at this point. Of course hitting a or d will break follow but do you know a way of specifically setting follow to off within a bind?

Otherwise the files match my expectations; +right/+left break follow but not autorun etc..

[/ QUOTE ]

I am not going to guarantee this atm as I am still in the office, but I believe that while "AUTORUN 1" does not turn off FOLLOW, ++FORWARD will. Also, I keep getting errors adding parms to FOLLOW. "FOLLOW 1" and "FOLLOW 0" both give me errors saying that I supplied the wrong number of parms for the FOLLOW command. This is why I use ++FORWARD instead of ++AUTORUN or "AUTORUN 1"/"AUTORUN 0"; AUTORUN seems to have some weirdness in that it doesn't interact with FOLLOW in the same way that ++FORWARD does. Not sure why it works that way, though.

[ QUOTE ]
In every file in the run directory, modify all the files with NO y in the filename so that space is "+up" only, and x is nop only.

For all files WITH a Y, erase the entire bind for space and X except for the bind_load_file command. These files with a Y are no longer called when in run mode, and are only used when switching from fly to run and x or space is depressed. Changing the binds as I've said lets you release that key and puts you in the right mode without changing anything else.

Gnarly

[/ QUOTE ]

Heh. You keep posting while I am painstakingly hunting/pecking out my own posts.

I think this still runs into the problem that when switching from RUN to FLY you don't know whether or not to go to the FLY file with the Y axis stuff in it, or not. I have alot of times where I will hit and hold jump and then hit F (to approximate what F did in Joe's binds), all while running forward. I would now be coming out of RUNZ and would end up in FLYZ instead of FLYYZ, where I really want to be.

This is basically the stumbling block I am running into with the "Blastoff" and "Setdown" functionality.