Bugs in 1.6.7

Bugs in 1.6.7

PostPosted by timur » Wed Aug 07, 2013 10:16 am

Hello,

I have found the following bugs in 1.6.7 version:

1. Out blending for sub-state machine:
For example: you have top state machine with Idle anim. In this top state machine you have sub-state machine with Jumps logic (simple jump, double jump, may be some mixing transforms).
Idle animation is blended with Jump animation when we go INTO sub-state machine. But Jump anim doesn't blend with Idle anim when we go OUT from sub-state machine . It's just play sequentially.
I have checked the source code and there are really only Input Weight supported for StateGraph.
The documentation says that StateGraph has "Out" time.
"When transitioning away from this state, this is the amount of time (in seconds) that it should take to fully blend out of this states animations."

2. Chained conditions doesn't work
If you have one condition which is linked with another then whole bunch will not work. The release notes says that the issue was fixed in 1.5.4 version.

Thanks Timur
Last edited by timur on Thu Aug 08, 2013 12:45 am, edited 2 times in total.
timur
 
Posts: 5
Joined: Wed Aug 07, 2013 10:01 am

Re: Bugs in 1.5.7

PostPosted by AlteredReality » Wed Aug 07, 2013 9:10 pm

First off, I've verified the first bug with blending in/out of a state machine node in 1.6.7. As well, I verified the bug with chained condition nodes. I will be looking into a fixes for these ASAP. Sorry about any inconvenience.

Secondly, are you actually on 1.5.7? Or did you mean to say 1.6.7? If you are on 1.5.7, I strongly recommend upgrading to 1.6.7.

I'll post and/or email when i have the issues resolved. And thanks for reporting these issues!
Andy - Altered Reality
AlteredReality
Site Admin
 
Posts: 118
Joined: Fri Jan 06, 2012 8:31 pm

Re: Bugs in 1.6.7

PostPosted by timur » Thu Aug 08, 2013 12:43 am

Thanks for reply! And yes, of course I mean 1.6.7 version not 1.5.7. Sorry about the confusion. I have corrected the title.
timur
 
Posts: 5
Joined: Wed Aug 07, 2013 10:01 am

Re: Bugs in 1.6.7

PostPosted by AlteredReality » Thu Aug 08, 2013 11:01 pm

I believe I have both of the issues resolved. I went ahead and emailed you the beta version of 1.6.8 with the fixes. Let me know how that works for you. Thanks!
Andy - Altered Reality
AlteredReality
Site Admin
 
Posts: 118
Joined: Fri Jan 06, 2012 8:31 pm

Re: Bugs in 1.6.7

PostPosted by timur » Fri Aug 09, 2013 8:05 am

I have checked the beta version and both bugs are resolved there. Works perfect!

Thank you very much!
timur
 
Posts: 5
Joined: Wed Aug 07, 2013 10:01 am

Re: Bugs in 1.6.7

PostPosted by AlteredReality » Sun Aug 11, 2013 8:33 pm

timur wrote:I have checked the beta version and both bugs are resolved there. Works perfect!

Thank you very much!


Awesome! No problem at all. Let me know if you have any other questions or issues.
Andy - Altered Reality
AlteredReality
Site Admin
 
Posts: 118
Joined: Fri Jan 06, 2012 8:31 pm

Re: Bugs in 1.6.7

PostPosted by timur » Mon Aug 12, 2013 8:27 am

Hi again :)
I think I found another issue.

Forced Trigger always choose condition which is not satisfied. So if you have trigger which is linked with two conditions, one satisfied and one is not, the trigger will go to "wrong way". I believe the issue came from the following code in "SageConditionStateNodeSlot" file. Since trigger choose node with less cost,it chooses not satisfied condition.
Code: Select all
        public override float InCost
        {
            get { return m_bConditionSatisfied ? 0.0f : -1.0f; }
            set {  }
        }
timur
 
Posts: 5
Joined: Wed Aug 07, 2013 10:01 am

Re: Bugs in 1.6.7

PostPosted by AlteredReality » Wed Aug 14, 2013 8:23 pm

Have you tried locally returningna really high value instead of -1.0? I'd imagine that would like resolve the issue. Regardless, I'll look into it when I get time. Thanks for the report!
Andy - Altered Reality
AlteredReality
Site Admin
 
Posts: 118
Joined: Fri Jan 06, 2012 8:31 pm

Re: Bugs in 1.6.7

PostPosted by timur » Mon Aug 19, 2013 7:00 am

Yep, I have tried my fix locally and it works fine. I just though that you can fix it in release version to be sure that this is the correct fix. ;)
timur
 
Posts: 5
Joined: Wed Aug 07, 2013 10:01 am

Re: Bugs in 1.6.7

PostPosted by AlteredReality » Tue Sep 10, 2013 9:15 pm

I've submitted a fix with this in Sage 1.6.9.
Andy - Altered Reality
AlteredReality
Site Admin
 
Posts: 118
Joined: Fri Jan 06, 2012 8:31 pm


Return to Bug Reports

Who is online

Users browsing this forum: No registered users and 0 guests


Style by Gokinstudio | Free forum hosting by ProphpBB | Software by phpBB | Report Abuse | Privacy
cron