@m_magalhaes said in Blip before Correctly Updating:
As i understood, your matrix is linked to your generator using a input field or a InExclude List.
I did when I posted this, but I can have it work from an InExclude or from the child input, in either case the 'blip' exists.
Did you try to send an update message to the matrix object ?
I didn't. From what I can tell GVO is being called twice. Once before the child Matrix is dirty and once after, which is creating the blip.
How would I know if I should update the Matrix in the first GVO call?
Don't be afraid of making the Matrix calculate its cache twice in a frame execution.
This isn't something I should avoid? Seems risky to update an object multiple times per frame.
GetContour at the same time can be strange sometimes.
I'm not doing both at the same time, but I wanted to be able to use the solution in either function. It seems like each one has it's own way of updating and access to different variables. So I wanted to make sure I wasn't limited to just one case.
How would I delay the GVO call in Execution?