Pressing keys to turn on objects doesn't work. Help

[Lane]

 You don't need to get key and get button, they're totally different actions.

[coffeeANDsoda]

You don't need to get key and get button, they're totally different actions.

What should I do then? Because if I can't use those actions to turn on a light then I don't know what to do.

[Lane]

Just use Get Button Down, send an event from it, go to the next state and use Get Button Up, fire an event back from there. Make a circle. If its down, then its in this state, if its up then its in the other state.

[coffeeANDsoda]

Just use Get Button Down, send an event from it, go to the next state and use Get Button Up, fire an event back from there. Make a circle. If its down, then its in this state, if its up then its in the other state.

When I press play, the first state with the arrow pointed down lights up green. The second state named "On" (where the Get Button Up action is located) is grey. So it still doesn't light up.

[redikann]

I wouldn't use Horizontal because it has a positive and negative key (a, d). Just use key up and key down. Do you really need 'turn on' to be a global event. Seems to me that current set up might confuse Playmaker.
Your telling Playmaker that on the 'turn on' event you want to loop back into your start state.

[coffeeANDsoda]

I wouldn't use Horizontal because it has a positive and negative key (a, d). Just use key up and key down. Do you really need 'turn on' to be a global event. Seems to me that current set up might confuse Playmaker.
Your telling Playmaker that on the 'turn on' event you want to loop back into your start state.

How about applying that to three objects? Because what I want to do is have a set up like Up, Down, left or right. Or D for the lowest object, A for left and D for right.

[redikann]

Each object can have it's own FSM listening for it's own key input. You could use the axis event action but it might be cleaner to do it by object.

[coffeeANDsoda]

Each object can have it's own FSM listening for it's own key input. You could use the axis event action but it might be cleaner to do it by object.

So for each button(three in this case) all 6 states would have Axis Event? Or would all three objects just have it with the first. Given the face the first is "Off" so each Off state would have Axis and Set Light Intensity. Like the one one highlighted in blue?

https://db.tt/tZdRa2SS

[Lane]

Dude, Get Button uses the inputs defined in the Input Manager. They are axi. There is positive and negative for all of them. You call them by their name with Get Button. Get Key uses buttons on the keyboard defined in that action - totally different. You can use either here.

So unless you have an input you created called "off light" then that action isn't going to do anything.

[coffeeANDsoda]

So unless you have an input you created called "off light" then that action isn't going to do anything.

Then why doesn't the action act like it's connected? Plus, are you sure I don't have to add a FSM to PlaymakerGUI?

https://db.tt/PuvIMJx0

[redikann]

I am taking a guess but look under the "Start" event you will see 'turn on'. Try deleting that.

[coffeeANDsoda]

I am taking a guess but look under the "Start" event you will see 'turn on'. Try deleting that.

The start FSM? How would that effect it though?