x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

AnswerHub Maintenance

Background maintenance is scheduled to occur between 9 - 11am EDT on Tuesday, May 21. Site operation may be slower than normal during this time and a brief interruption in operation may be observed

How and when are variable values cached/read for animation transitions?

Hi there,

(UE 4.12.5)

We had a case where a the animation system in an animation graph does something we don't expect while setting variables during transition events.

I've made a simple reproduction case that highlights my problem.

Setup

alt text

The premise is simple, we have a start node, that waits for a variable "Start Process" before transitioning to the DECIDE node. A second variable "Go To Node B" will determine whether DECIDE will end up in NODEA or NODEB.


Transition rule for DECIDE -> NODEA


alt text


Transition rule for DECIDE -> NODEB


alt text

At this point as "Go to Node B" is true by default, if I run the graph and trigger "Start Process", I'd expect the final state node to be "NODEB". This works as expected.

I now add custom events to set "Go to Node B" to false.


First place is on the "Entered State" node: alt text

Second event is on the "start transition" event of the "Start->Decide" transition. alt text

The "ResetGoto" event in question simply sets "Go to Node B" to false, which should cause the final node to be A instead.

What I Expect:

The thinking is that we switch over to DECIDE, and during this switch we then have some logic that decides whether "Go to Node B" is true or false. After switching to DECIDE the appropriate transition should be made based on the current value of the variables.

What actually happens

Now if I ran the graph and triggered the "Start Process" variable, I still end up in node B at the end despite the fact that the value test for going to node B is false. I tried outputting the values of the variable along the way, and it all clearly states it's FALSE. Yet the transition to node B still is taken.


What it looks like to me, is that at the start of the frame the "YES/NO" value for all transitions are evaluated, and then the state machine is traversed without taking into account any possible changes. Is this assumption correct? Or am I missing something else...

I had more pictures, but it seems I hit the attachment limit - if anything is unclear please let me know and I'll try to explain it better :)

Kind regards,

Johan Conradie

Black Forest Games GmbH

Product Version: UE 4.12
Tags:
1.png (79.8 kB)
4.png (22.7 kB)
5.png (19.2 kB)
2.png (15.6 kB)
3.png (14.4 kB)
more ▼

asked Sep 12 '16 at 04:37 PM in Blueprint Scripting

avatar image

Johannes.Conradi
21 2

avatar image HologramMonster Jan 19 '18 at 02:51 PM

This is still problem in 4.18.3 it forces to use tedious workarounds. Is there reason for this behavior?

(comments are locked)
10|2000 characters needed characters left

0 answers: sort voted first
Be the first one to answer this question
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question