playMaker

Author Topic: "Get Angle to Target" now needs it's own explicit state?  (Read 976 times)

Red

  • Hero Member
  • *****
  • Posts: 563
    • View Profile
"Get Angle to Target" now needs it's own explicit state?
« on: March 17, 2013, 10:13:38 PM »
I've had it in systems before and it would work fine but since the update it's only working when it is in it's own state in the FSMs...

it doesn't seem to fire off at all when it has to share space in a state with other actions.

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 12344
  • Official Playmaker Support
    • View Profile
Re: "Get Angle to Target" now needs it's own explicit state?
« Reply #1 on: March 17, 2013, 11:37:15 PM »
Hi,

 Can you share a repro scene? I am not sure what you mean by "space"

could it be that one of your other action finished the state, and therefore "everyframe" actions stop functioning?

bye,

 Jean

Red

  • Hero Member
  • *****
  • Posts: 563
    • View Profile
Re: "Get Angle to Target" now needs it's own explicit state?
« Reply #2 on: March 18, 2013, 07:09:20 AM »
Here you are. the one that is "Angle compact" doesn't fire off the get angle to target (and always results with a "0" regardless where the target is) and the "Angle Spread out" does.

I think it's as if the order in the state is no longer applying and the Get angle to target is not executing fast enough before the float compare fires off. If the order in the states are essentially borked, that means that there may be other states in the systems i have that are not firing off in the correct order either.