@m_magalhaes

Sorry about the late reply again! I went to build some simplified code to post and I might have figured it out in the process.

It seems that if I correctly mark the children with AddDependence then GetCache returns the cache I expect. Having the object lower in the object manager than mine causes it to lag behind slightly, but that seems consistent with other Cinema objects.

Dan

@m_magalhaes

Hi! I don't mean to be a bother but I'm just giving this a bump in hope of a response!

Dan

@m_magalhaes

Yes, or in GVO() depending if I'm returning a spline or not.

Hi Manuel,

I was going to post my code but at the moment it looks as if the linked thread is giving the results I need with the matrix object, the blip is gone! using Current State to Object.

I'm not sure if you'd prefer for me to make a new thread for this question, but I've had similar 'blip' issue with Generators returning Polygon or Spline objects in both GVO and GetContour.

Using GetCache I'm able to browse and get the actual Polygon and Spline object, but when they're a child or further down the Object Manager Hierarchy than my plugin, I'm getting the previous cache, not the new one.

I know there are plenty of ways to rebuild the cache but is there a best practice method that offers the least overhead?

Dan

Sorry about the delayed reply!

the voronoi object is registered with the flag OBJECT_INPUT.

I have this set as well, and I've swapped to taking the child matrix in as a child and I'm still having the same blip.

Hi Manuel,

I implemented that and didn't notice a difference in my error though.

To be clear this is the sort of error I'm getting as shown with the Voronoi Fracture.

When the Matrix is above or a child of the Voronoi Fracture it updates correctly. When after the Voronoi Fracture it doesn't, there's a blip, that makes sense to me.

The difference is that in my plugin having the Matrix as a child of my plugin still has the blip where the Voronoi Fracture doesn't.

first of all: It is unclear to me what you mean by "the points of a Matrix". Do you actually interpret the components of a matrix as points

Correct, I'm getting them from the MoData.

you should register your generator with OBJECT_CALL_ADDEXECUTION and then overwrite ObjectData.AddToExecution to tell Cinema that that object type should be evaluated after all other generators (via EXECUTIONPRIORITY_GENERATOR).

I'm unsure how to do this part.
Adding to the PriorityList is easy enough, but from my testing it seems like using AddToExecution() only effects when Execute is called. Should I be doing this in Execute then?

@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.

Using GVO and 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?

Thanks,
Dan

Hello, I'm working on a plugin where I'm taking the points of a Matrix and using them as an input. The problem is that when the Matrix is changed there is a 'blip' where I'm getting the previous state of it, the old locations of the points, before it updates and then gives me the new updated locations.

This doesn't happen if the Matrix is above my plugin in the Object Manager, which makes sense to me.

The blip happens if the Matrix is after my plugin, which makes sense and is fine.

But the blip also happens if the Matrix is a child of my plugin and this is the behavior I would like to fix.

I'd like to get this working correctly in GetVirtualObjects() and GetContour() if possible. I currently have no dirty checking going on in GVO, since it should be updating at all possible then.

Is there a flag or a check I should be doing to update at the right time and avoid the blip?

Dan

Thanks! That's exactly what I needed!