Change Costume with Travel Power

raighn

I tried using the method in the Sticky about popular Keybinds to do this, however it doesn't seem to work properly any more. It will change to Costume Slot 2 on activating properly, but when I try to return back to costume 1 no matter how much time passes it gives me the cannot change at this time error. It seems the keybind is triggering costume 2 every time i activate or deactivate my travel.

Archived Post wrote: »

How can I change costumes/builds when I activate my travel power?
Create the following 2 txt files, with the listed contents in your Champions Online\Live Folder.

fly.txt:
t "+PowerTrayExec 14 $$ buildset 1 $$ bind_load_file land.txt"

land.txt:
t "+PowerTrayExec 14 $$ buildset 0 $$ bind_load_file fly.txt"

Then run:
/bind t "+PowerTrayExec 14 $$ buildset 1 $$ bind_load_file land.txt"

To change costumes, instead of builds:
Change "buildset <#>" to "setactivecostume 0 <#>"

I followed the last part as well on all 3 parts since I only wanted costume to change.

Additionally... is there any way to get xbox controller commands to trigger keybinds?

If anyone could help me get this bind to work properly that would be wonderful.

r9xchaos

mhh sounds interesting... hopefully this gets answered sometime soon

grapemousse

Not sure if it is related, but have you accounted for the fact that the setactivecostume bind starts counting costumes at 0? So 0 in the bind refers to costume number 1, 1 refers to costume number 2, etc. That's the only explanation I can think of, though I'm not overly experienced with binds.

raighn

grapemousse wrote: »

Not sure if it is related, but have you accounted for the fact that the setactivecostume bind starts counting costumes at 0? So 0 in the bind refers to costume number 1, 1 refers to costume number 2, etc. That's the only explanation I can think of, though I'm not overly experienced with binds.

Yep, I'm not new to arrays and as I said in my post, It changes to the second costume just fine, but when trying to get the second part changing back to occur, reguardless of if I deactivate travel an hour later or a minute later, it gives me the costume change lockout message since it keeps trying to apply the 2nd costume, I tested this by manualy changing to a 3rd costume after activating and waiting a bit to deactivate only to see it once again change to my flight costume and give me an error about changing costumes not being possible at this time.

dikawolf

Your bind looks ok, but hearing about your problem it sounds like the files are reloading the fly.txt at the click up. Try this instead.

fly.txt:
t "PowerTrayExec 1 14 $$ buildset 1 $$ bind_load_file land.txt"

land.txt:
t "PowerTrayExec 1 14 $$ buildset 0 $$ bind_load_file fly.txt"

Then run:
/bind_load_file fly.txt

The drawback to this, is the travel power will automatically charge to full with each press.

Another solution would be trying 4 files.

fly.txt:
t "+PowerTrayExec 14 $$ bind_load_file fly2.txt

fly2.txt:
t "+PowerTrayExec 14 $$ buildset 1 $$ bind_load_file land.txt"

land.txt:
t "+PowerTrayExec 14 $$ bind_load_file land2.txt"

land2.txt:
t "+PowerTrayExec 14 $$ buildset 0 $$ bind_load_file fly.txt"

Then run:
/bind_load_file fly.txt

Or if you don't want the travel power to shut down after the change, try this:

fly.txt:
t "+PowerTrayExec 14 $$ bind_load_file fly2.txt

fly2.txt:
t "buildset 1 $$ bind_load_file land.txt"

land.txt:
t "+PowerTrayExec 14 $$ bind_load_file land2.txt"

land2.txt:
t "buildset 0 $$ bind_load_file fly.txt"

Then run:
/bind_load_file fly.txt

raighn

dikawolf wrote: »

Your bind looks ok, but hearing about your problem it sounds like the files are reloading the fly.txt at the click up. Try this instead.

<Clip>

Either I messed up somewhere or none of these are working... though I guess it could be related to the lag I've been dealing with today... Wish I knew where this lag was comming from, I've never had this bad of lag issues before and it's just happening on Champions.

lazirul

hmm,so why not post the binds you made for it.

raighn

The one i'm currently using is:

fly.txt:
t "PowerTrayExec 14 $$ setactivecostume 0 2 $$ bind_load_file land.txt"

land.txt:
t "PowerTrayExec 14 $$ setactivecostume 0 0 $$ bind_load_file fly.txt"


/bind_load_file fly.txt


The costumes in use are in Slots 1 and 3 hense 0 2 instead of 0 1

dikawolf

raighn wrote: »

The one i'm currently using is:

fly.txt:
t "PowerTrayExec 14 $$ setactivecostume 0 2 $$ bind_load_file land.txt"

land.txt:
t "PowerTrayExec 14 $$ setactivecostume 0 0 $$ bind_load_file fly.txt"


/bind_load_file fly.txt


The costumes in use are in Slots 1 and 3 hense 0 2 instead of 0 1

You need either a + before the PowerTrayExec so it reads "+PowerTrayExec 14" or a 1 between the command and the powertray number so it reads "PowerTrayExec 1 14". A plus before means to set the power on or off depending on its current setting. The 1 being a designation to force the power on regardless of current setting.

The + designation also has another property in which tell the game to run the bind twice, once on downclick of a key and again when the key is released. The original bind posted loaded the fly again because of the +, on the downclick it loaded the land.txt file, and on the release of the key reloaded the fly.txt file.

To illustrate upon pressing the T key, the bind ran the following:
"+PowerTrayExec 14 $$ buildset 1 $$ bind_load_file land.txt"

Which turned on the travel power if it was off, changed the build to the second one (1), and replace the bind to t with the contents of the land.txt file.

However with the "+" designation at the beginning of the bind, it also told the game to run the bind again when the key is released therefore running the following:

"+PowerTrayExec 14 $$ buildset 0 $$ bind_load_file fly.txt"

Which turns off the travel power, and reloads the bind in t to the contents of the fly.txt. It doesn't change the build because of the 30 second cooldown between build changes.

raighn

dikawolf wrote: »

You need either a + before the PowerTrayExec so it reads "+PowerTrayExec 14" or a 1 between the command and the powertray number so it reads "PowerTrayExec 1 14". A plus before means to set the power on or off depending on its current setting. The 1 being a designation to force the power on regardless of current setting.

The + designation also has another property in which tell the game to run the bind twice, once on downclick of a key and again when the key is released. The original bind posted loaded the fly again because of the +, on the downclick it loaded the land.txt file, and on the release of the key reloaded the fly.txt file.

To illustrate upon pressing the T key, the bind ran the following:
"+PowerTrayExec 14 $$ buildset 1 $$ bind_load_file land.txt"

Which turned on the travel power if it was off, changed the build to the second one (1), and replace the bind to t with the contents of the land.txt file.

However with the "+" designation at the beginning of the bind, it also told the game to run the bind again when the key is released therefore running the following:

"+PowerTrayExec 14 $$ buildset 0 $$ bind_load_file fly.txt"

Which turns off the travel power, and reloads the bind in t to the contents of the fly.txt. It doesn't change the build because of the 30 second cooldown between build changes.

If I'm reading what your saying correctly then your saying there is a big problem with this type of bind and that what I'm wanting to do isn't even actually possible. Since if I use 1 it wont allow me to turn my travel off but if I use + it will run my bind twice preventing me from having the costume change properly on disable of travel.

Also, I don't know why everyone seems insistant on the buildset bind when there is a costumeslot bind command as well, which all i'm after is a costume change upon activating & deactivating my travel power.

dikawolf

raighn wrote: »

If I'm reading what your saying correctly then your saying there is a big problem with this type of bind and that what I'm wanting to do isn't even actually possible. Since if I use 1 it wont allow me to turn my travel off but if I use + it will run my bind twice preventing me from having the costume change properly on disable of travel.

Also, I don't know why everyone seems insistant on the buildset bind when there is a costumeslot bind command as well, which all i'm after is a costume change upon activating & deactivating my travel power.

I did the buildset since you used as an example on your first post. I was reitterating what was happening on that bind that caused the same costume to display over and over again.

The binds in my examples counter the effect of + by turning on the power on the click down, and change the costume on the release of the key (notice how their is no powertrayexec command on fly2.txt). By understanding what is happening, you can work with it. Once you understand how the binds work, you could do exactly what you want to do, and there is a bind to force a power off.

For instance, as I said, to force a power on you use PowerTrayExec 1 <TrayNumber>. To force a power off, the bind is PowerTrayExec 1 <TrayNumber>$$PowerTrayExec 1 <TrayNumber>. It's weird that it looks like I'm turning on a power twice, instead of using PowerTrayExec 0 <TrayNumber> to turn it off, which actually doesn't work for some reason. I know this sounds counter intuitive cause it is. However, it works because the game doesn't allow powers to be activated twice by the same click, so it shuts it off instead.

raighn

Ok, I'm trying your second 4 file bind again, but the issue i'm having now is that it's simply not doing anything... my travel power activates but my costume doesn't change at any point, I don't even get the cooldown...

fly.txt
t "+PowerTrayExec 14 $$ bind_load_file fly2.txt"

fly2.txt
t "setactivecostume 0 2 $$ bind_load_file land.txt"

land.txt
t "+PowerTrayExec 14 $$ bind_load_file land2.txt"

land2.txt
t "setactivecostume 0 0 $$ bind_load_file fly.txt"

in game:
/bind_load_file fly.txt

I don't know what i could have possibly done wrong...

dikawolf

If I'm reading it correctly, it seems you want to change the costume when you turn the travel power on. Then change back when you turn the travel power off. That bind would look like this:

fly.txt:
t "PowerTrayExec 1 14 $$ setactivecostume 0 2 $$ bind_load_file land.txt"

land.txt:
t "PowerTrayExec 1 14 $$ PowerTrayExec 1 14 $$ setactivecostume 0 0 $$ bind_load_file fly.txt"

dikawolf

raighn wrote: »

Ok, I'm trying your second 4 file bind again, but the issue i'm having now is that it's simply not doing anything... my travel power activates but my costume doesn't change at any point, I don't even get the cooldown...

in game:
/bind_load_file fly.txt

I don't know what i could have possibly done wrong...

Thats cause it takes a second before binds reset. So you have to hold the key down for a second. If you click too fast, you face the same problems you had before.

Edit: Come to think of it, you might need a second plus to get the change happen on the click up. I remember that was the case in CoH.

In that game, I had to do the following:
fly.txt
t "+PowerTrayExec 14 $$ bind_load_file fly2.txt"

fly2.txt
t "+ $$setactivecostume 0 2 $$ bind_load_file land.txt"

or

t "+Up$$setactivecostume 0 2 $$ bind_load_file land.txt"

land.txt
t "+PowerTrayExec 14 $$ bind_load_file land2.txt"

land2.txt
t "+ $$setactivecostume 0 0 $$ bind_load_file fly.txt"

or

t "+Up$$setactivecostume 0 0 $$ bind_load_file fly.txt"

Hope that works.

raighn

dikawolf wrote: »

Thats cause it takes a second before binds reset. So you have to hold the key down for a second. If you click too fast, you face the same problems you had before.

I held it for the full charge and nothing happend still.

dikawolf

I made some edits. Try those.

raighn

still nothing... I think the game might be having issues recognizing the /bind_load file fly.txt command... cause i havn't been able to get it to respond at all since I started using that.

raighn

Ok, I got it to work finaly... turned out my files somehow saved with double extentions so they wern't reading.... resaved everything and it works now....


now if I could just get it to trigger from my xbox controller as well... but I guess thats probly not possible till a dev decides to take it upon himself to complete the controller binds

dikawolf

raighn wrote: »

Ok, I got it to work finaly... turned out my files somehow saved with double extentions so they wern't reading.... resaved everything and it works now....


now if I could just get it to trigger from my xbox controller as well... but I guess thats probly not possible till a dev decides to take it upon himself to complete the controller binds

What I do for my xbox controller is since the build changes are already handled by Joypad_down + XB (YB, BB, AB, RB, and LB), I just had the travel power toggled on/off with the Joypad_down.

/bind joypad_down "+PowerTrayExec 14"

raighn

dikawolf wrote: »

What I do for my xbox controller is since the build changes are already handled by Joypad_down + XB (YB, BB, AB, RB, and LB), I just had the travel power toggled on/off with the Joypad_down.

/bind joypad_down "+PowerTrayExec 14"

I'll have to try that... so basicly I'd just add a second line to my bind files using joypad_down in place of t?

dikawolf

raighn wrote: »

I'll have to try that... so basicly I'd just add a second line to my bind files using joypad_down in place of t?

Actually, I was giving an example of how I was doing it, since I use the travel power just as an effect for the build change (I currently have it that the travel power is also disabled with the build change). In your case since, what you are trying to do is do the costume change with the activation and deactivation of the travel power, I'd build the binds with the LStick (which activates travel powers on the XBox controller). I'd add a second line to the bind files that's exactly the same as the binds for the T key except replacing the "bind t" with "bind LStick". That way the LStick and the t key work synonymously.

raighn

dikawolf wrote: »

Actually, I was giving an example of how I was doing it, since I use the travel power just as an effect for the build change (I currently have it that the travel power is also disabled with the build change). In your case since, what you are trying to do is do the costume change with the activation and deactivation of the travel power, I'd build the binds with the LStick (which activates travel powers on the XBox controller). I'd add a second line to the bind files that's exactly the same as the binds for the T key except replacing the "bind t" with "bind LStick". That way the LStick and the t key work synonymously.

works like a charm ^-^ TY