SC2Mapster

I don't really understand it. What I have is a periodic trigger that makes the unit face the yaw over .1 game sec. but when I give it a move command, the trigger takes over and stops the unit and turns. Not sure if this is a trigger or data issue, is there a flag or something that separates moving and turning?

Firstly, this is the data section.

Secondly, have you tried simply issuing a move order that's, say, 1 unit infront and 0.1 units to the left or right? Or point with polar offset where the offset is the unit facing +5 degrees or somesuch?

@Eiviyn: Go

im working on the data WASD movement for TPS/FPS so it's acting different than if I were to give the command via trigger. Actually had it working, but making the unit face the yaw isnt working right.

@DrSuperEvil: Go

Haha, I have no idea how it works, but I'll give it a try. Thanks

@DrSuperEvil: Go

okay tried it, but the issue has to do more with the unit mechanics and not the visual actors.

@DrSuperEvil: Go

tried that before, but no difference. though i did manage to fix it by changing the trigger. Instead of using a periodic event, I changed it to a while statement and added a longer delay. guess the trigger just doesnt work right with the move ability. now its moving smoothly and turns. Again, this is for WASD movement for TPS/FPS

@DrHu:

Sounds like you might need to turn the yaw rotation into an ability. Then you could instead of changing the yaw directly through the trigger, use the ability with the trigger, and then have it set to "before current actions" so that once the rotation is complete (almost instantly) the unit will continue to move.

If you do this periodically (like a WASD would have to) it might cause some choppy side effects, but I don't think there is another way to do this properly. (Well at least that I can immediately think of)