Anyone Notice Rule Attribute Problems in 9.4?

The_Gamesalad_GuruThe_Gamesalad_Guru Member Posts: 9,922
edited June 2012 in Working with GS (Mac)
Maybe it's just me but my code is usually pretty tight. I'm noticing when say I have an attribute like > or a boolean condition for a rule to fire or not fire that sometimes the rule doesn't fire or doesn't keep firing if the conditions aren't met. I'm not one to blame GS so maybe I'm missing something. I though if I say had a rule if self.position x doesn't equal 345 then I have a move to x 345 it should keep firing until the attribute cuts it off. I read they fixed somthing about "Fixed an issue where the evaluation parameter in a rule does not update when chaning the type of variable to be evaluated." Just curious what other advanced users might have to add.

Best Answer

  • simo103simo103 Posts: 1,331
    Accepted Answer
    David .. I believe GS has an issue with being exactly at an X or Y IE: your move to 345 might be 345.0001 or something ... don't know if that helps any?

Answers

  • The_Gamesalad_GuruThe_Gamesalad_Guru Member Posts: 9,922
    edited June 2012
    Yeah I am noticing a delay in rule execution. I have some pretty fast gameplay and sometimes the rules can't keep up. I have my rules sorted properly I may have to add some < and > with decimal places and see. Thanx (Okay so I added a floor() funtion to my position in the rule attribute and the move to behavior, it processes much better this rounds off the position up or down from the decimal place.
Sign In or Register to comment.