Login

Fancade Wiki

Better formatting, fixed link

What are some common problems related to execution order?.md
... ...
@@ -1,20 +1,13 @@
1
[[Click here to read this article in the Wiki with images|https://www.fancade.com/wiki/what_are_some_common_problems_related_to_execution_order]]
2
3
If you don't know what execution order is, [[check this out|https://www.fancade.com/wiki/what_is_execution_order]].
4
5
Execution order is a boon and a curse at the same time. While it helps determining what to execute, sometimes the default Execution Order doesn't actually do what you want. Thankfully, you can easily fix that using Execution Wires.
1
[[Execution order]] is a boon and a curse at the same time. While it helps determining what to execute, sometimes the default Execution Order doesn't actually do what you want. Thankfully, you can easily fix that using Execution Wires.
6 2
7 3
Here are two common problems related to execution order.
8 4
9 5
1. This one is common among newbies. In this case, the problem is easy to spot. The variable **A is defined AFTER the Set Position** that has A as an input. Since A is not yet defined when Set Position was run, it simply does nothing resulting in a buggy script.
10 6
[[https://imgur.com/NZgn9C7.jpg]]
11
12 7
A simple solution for this is to **define A before the Set Position**.
13 8
[[https://imgur.com/4KJxQG5.jpg]]
14 9
15
16 10
2. Create Object is one of those scripts that has **an output AND execute wires** attached to it. If a scripts has both, output and execute wires, it's usually a good idea to set those outputs into a variable using the After Wire. Else, you'll suffer from an **One Frame Delay**.
17 11
[[https://imgur.com/7xNbBVB.jpg]]
18
19 12
The script shown above will suffer from that One Frame delay, since each frame the object that gets created is set onto the variable A **after** the set position has run. A simple fix would be, is to set the variable via the After Wire.
20 13
[[https://imgur.com/4iUV6ZV.jpg]]
... ...
\ No newline at end of file
Fancade Wiki