How do I properly turn my custom character? | Forums

[rlmergeuser]

I'm having trouble getting my custom character to move rotational-wise. For example, when I pull down on the LS control stick I want it to turn upwards. I don't want to just push me up, I want to change the position of the actual object with the LS control stick. I can't get it to move by pulling down on the LS control stick and if change the position at the start just to try something, it won't move while and after it's done.

So, how do I change an object's position with a button trigger? How do I make sure that it still moves once I do that? I've looked at all of Redlynx's tutorial videos and I've looked at both of Telixion's videos, but I still just can't get it.

Help would be appreciated, if you can understand what I'm saying...

[rlmergeuser]

The simplest way would be to use an object position event and change the object's pitch based on the input.

I.e.
[code:2w2iph4t]
ObjectPositionEvent(Rotation only, local):
Yaw: 0
Roll: 0
Pitch: DataSource(Left stick vertical)
[/code:2w2iph4t]

You may need to take the negative value of the stick depending on if you want the controls inverted or not.

One very common issue with Object Position Events is not considering the implications of the values you're setting - for example, whenever you use global positioning, you must set all values unless you actually want to set any of its values to 0. Generally speaking, you'll probably want to set one or more of the values in the Object Position Event to be the target object's current value for that parameter. Local positioning can avoid this issue, but isn't ideal in every instance.

[rlmergeuser]

The simplest way would be to use an object position event and change the object's pitch based on the input.

I.e.
[code:2u6tinqe]
ObjectPositionEvent(Rotation only, local):
Yaw: 0
Roll: 0
Pitch: DataSource(Left stick vertical)
[/code:2u6tinqe]

You may need to take the negative value of the stick depending on if you want the controls inverted or not.

One very common issue with Object Position Events is not considering the implications of the values you're setting - for example, whenever you use global positioning, you must set all values unless you actually want to set any of its values to 0. Generally speaking, you'll probably want to set one or more of the values in the Object Position Event to be the target object's current value for that parameter. Local positioning can avoid this issue, but isn't ideal in every instance.

Thanks, I've figured it out now. I was making it so that when I stopped holding down LS, the value of the pitch would go back down to 0. I'm surprised that I'm not frustrated with the editor. It's probably because when I start to get frustrated I can just back out and play some goofy skill games.