Pity, because I have that same bind setup on my warshade and don't get the reticle (normally). It does bug sometimes and give me the reticle once on the first port, but subsequent ports do not.
If you've made a typo in the "lbutton", then the bind went to lshift instead of failing. do a /bindsave and check the bind, fix it as necessary, and reload the file after fixing the bind.
For the longest time, my brain insisted that the bind was lshift+lclick, and I got the same results, because lclick isn't a real keyname.
@Roderick
Quote:
It could also be because lshift+anything isn't a real keyname either.|
Originally Posted by Roderick
If you've made a typo in the "lbutton", then the bind went to lshift instead of failing. do a /bindsave and check the bind, fix it as necessary, and reload the file after fixing the bind.
For the longest time, my brain insisted that the bind was lshift+lclick, and I got the same results, because lclick isn't a real keyname. |
LSHIFT itself is a key_name, not a modifier. You can't really bind LSHIFT+key, or it will do one of 2 things:
1. * truncate the key_name to LSHIFT
2. * bind to SHIFT+key anyway (pressing RSHIFT+key will still active your bind the same way)
The bind you probably wanted was:
SHIFT+LBUTTON
..just to avoid #1 from happening.
If you want to ALWAYS get the reticle, you can simply bind teleport to LSHIFT by itself, and then you will get the reticle and click your destination when you want to anyway. That's what I use on my toons, and I've never had a problem with it:
/bind LSHIFT powexecname Teleport
-or-
/bind LSHIFT powexecname Shadow Step
Really?
My hand is never even close to the RSHIFT key when I'm playing, so I don't use LSHIFT or RSHIFT; I just use SHIFT. I'd always thought that all three were vali chords.
@Roderick
Quote:
The wiki lists them separately as well, but it's not really the case. The left and right keys for control, shift, and alt can be bound separately as standalone keys, but when used as a chord, it defaults to allow either side of the board to work.|
Originally Posted by Roderick
Really?
My hand is never even close to the RSHIFT key when I'm playing, so I don't use LSHIFT or RSHIFT; I just use SHIFT. I'd always thought that all three were vali chords. |
This can be tested and verified by simply making a test bind chording LSHIFT, but using RSHIFT to activate, and also by doing a /bindsavefile and looking at the contents of the file.
That did it! Thanks Master-Blade. Much appreciated.
Now, to see if these Kheldians are all they are cracked up to be.
Our lives begin to end the day we become silent about things that matter.
--Dr. Martin Luther King Jr.
I also like to make sure people know about this thread:
The Ultimate Teleport Bind - The Program
It handles other fun things like
- Removing all windows from the screen
- Pulling the camera back for wider view to click in
- Differences between normal, PB, or WS teleports
- Restoring the camera and windows after you release the trigger key.
Changed using TP from a chore, to a favorite travel power.
There is also an alternate thread for laggers, but I haven't looked at that, and don't know which is a more useful thread.
.
I'm guessing you had a typo in lbutton. The lshift+lbutton bind still works as I just made a new teleporting character today that I've been using it on. And, it's been working correctly.
Quote:
Like I said above, that does indeed work as well, but there is still a small chance it wont for some people (apparently the OP). Do a /bindsave and look at your file now...|
Originally Posted by Forsyth
I'm guessing you had a typo in lbutton. The lshift+lbutton bind still works as I just made a new teleporting character today that I've been using it on. And, it's been working correctly.
|
You'll see that you really bound SHIFT+LBUTTON, not LSHIFT+LBUTTON like you thought you did. I just feel that because of the oddities in the game's bind system, it's easier/better to use the correct key definitions when binding so that you don't accidentally and unnecessarily come across glitches like the OP had.
Pressing RSHIFT+LBUTTON will activate the bind you just made as well. Try it!
Well I've had the same problem as the OP has had. Teleporting for my stone tank works well, but for my warshade it is still buggy.
I've modified the bind to this:
/bind ctrl+lbutton "powexec_name shadow step$$powexec_name black dwarf step"
and it works perfectly in Dwarf form.. no reticle, and I can hold down the crtl button to fire off a chain.... but in human form it will not do any of that
In human form the first time I hit it, it brings up the reticle. if I lbutton again I fire it off once.. then I need to lift off the crtl button in order to cycle through the bind (which works with the lbutton activating the power)
So what is wrong with how I'm doing it?
Quote:
Having more than one powexecname in a command gets a little tricky getting it to do exactly what you want in general, even without the reticle trick. |
Originally Posted by Galetta
Well I've had the same problem as the OP has had. Teleporting for my stone tank works well, but for my warshade it is still buggy.
I've modified the bind to this: /bind ctrl+lbutton "powexec_name shadow step$$powexec_name black dwarf step" and it works perfectly in Dwarf form.. no reticle, and I can hold down the crtl button to fire off a chain.... but in human form it will not do any of that In human form the first time I hit it, it brings up the reticle. if I lbutton again I fire it off once.. then I need to lift off the crtl button in order to cycle through the bind (which works with the lbutton activating the power) So what is wrong with how I'm doing it? |
The second command is probably trying to cancel the first one, causing you to have to re-run the command again. This is why it works in one form, but not the other. If you reverse the commands, I suspect it'll work the opposite way for your forms.
Also, keep in mind that the auto-left-click activate is not really by design, but a trickery of the fact that you have to left click your location anyway. Binding the power to include the left click works without a reticle as long as there is absolutely no delay in processing the power command as the button being clicked. Having 2 commands is probably breaking that delay.
Personally, I use the same bind you do, but I just bound it to the LShift key and let the reticle appear. It doesn't take any extra time to press LShift again after I click the location because you have to wait for the teleport animation anyway. You don't have to wait for the teleport animation to start the power.. just don't click until your screen actually moves and puts your retilce farther away.
I've figured out my problem.. and listed it here:
http://boards.cityofheroes.com/showp...0&postcount=58
Quote:
Yep, having a rotating bind file would have been my other suggestion, but glad you got it sorted out.
|
Originally Posted by Galetta
I've figured out my problem.. and listed it here:
http://boards.cityofheroes.com/showp...0&postcount=58 |
It has been a very long time since I made a character with Teleport, and when I did, I used Grotus' great teleport bind.
/bind lshift+lbutton "powexec_name Teleport"
Worked like a charm. No sign of the reticle, and a simple hold down the lshift button while clicking the lbutton on my mouse let me get around.
But now I am trying out my first warshade. I adapted the bind thusly:
/bind lshift+lbutton "powexec_name Shadow Step"
and it works... sort of. Now, rather than simple clicking, I get the reticle as soon as I press the shift key, and then I have to lclick. Did something change in the way that this bind works?
Ordinarily it would only be a minor annoyance, but I use the shift button with a lot of my binds, and this is really messing me up, as while the other binds work, I always have a targetting reticle up for Shadow Step now... annoying!
Any ideas? Suggestions? Pity?
Our lives begin to end the day we become silent about things that matter.
--Dr. Martin Luther King Jr.