[Bf-committers] Design considerations for data handling in the depsgraph

[Fazekas László]

Just from outside, but I'd like to ask this:

today I met something interesting in the bugs section. There was a 
calculation to get one object's derivedmesh on a sub-frame time position 
between two frames. The goal was to calculate this fast, without 
involving independent objects of the scene. Calculating a random time 
point is not easy because of the "current frame" concept...

Let's imagine I'm calculating something for the current frame, but 
during this, some nodes on the depsgraph needs data from different 
timeline points.

How the new depsgraph solves this situation? With a "child" depsgraph? 
What parts are shared? What happens if different nodes access the same 
time point? How to minimize calculation time and memory size?

I hope these are useful questions somehow.
Laszlo Fazekas


2014-06-17 18:06 keltezéssel, Lukas Tönne írta:
> As requested during last sunday meeting, here is a wiki page with thoughts
> on how to handle data with the depsgraph:
>
> http://wiki.blender.org/index.php/User:Phonybone/Depsgraph
>
> Discussion would be appreciated. The dependency graph will affect every
> area of Blender so we better do this right!
>
> Regards,
> Lukas
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>
>