@Philipp Oeser (lichtwerk) , the patch seems correct, please commit it :)

Functionality was already there in build_id (but not in build_nodetree), so I guess D3831 could do it?

In T57379#545695, @Philipp Oeser (lichtwerk) wrote:

Static Overrides will eventually be the proxy replacement [but are not ready yet] see rBfbf4c11960db62a27876e1d791d3293071e26c76

Regarding Multiple Proxies: thats a known limitation and not a bug.

oh, yes, mmh no wait... is there any change planned?

oops, @Bastien Montagne (mont29) was quicker...

Static Overrides will eventually be the proxy replacement [but are not ready yet] see rBfbf4c11960db62a27876e1d791d3293071e26c76

This is like the main limitation of proxies actually, you can only have one proxy of a linked data in your .blend file, more are not supported. No bug here, thanks for the report anyway.

But we already do 5) for object matrices. To me it seems best to have a single consistent solution, what breaks if we just copy back the boundbox to the original here?

@Brecht Van Lommel (brecht) Solution 2) does not involve modifying scripts, it’s RNA accessors that need to be updated (getting active depsgraph and calling relevant functions with relevant evaluated data). See a quick-slap test in P794 (seems to be working, but we’d need @Sergey Sharybin (sergey) to know whether that is 'allowed' or not I guess ;) ).

There was a decision to have only one active depsgraph for editing purposes, all the other depsgraphs are for viewing / rendering. So that should help solve this problem?

Spent some time yesterday checking on that problem again, and updated/refined my analysis…

Confirmed. @Sergey Sharybin (sergey), am going to summon you here, since I believe there may be something wrong in DEG - animation is in the CacheFile datablock, hence not in Object one (as any other modifier would be). And it is never evaluated afaict, even though dependency looks correct?

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

Afaik that’s only possible with two main windows (New Main Window from main top menu), using different viewlayers.

Thanks for the report, but bugs about new depsgraph in old 2.7x series are really not relevant at all now, new deg is only developed and maintained in 2.8 branch.

One have to wiggle a lot to make it crash indeed… Looks like yet another COW/threading issue (threaded code from deg evaluation using some COW data already freed from somewhere else)…

Can not really reproduce the issue, but there is a huge amount of dependency cycles reported. The system became more sensitive to what relations are killable and which are not, so need to think of some solution to this.

@Sergey Sharybin (sergey) pchan_array is NULL during evaluation of pose (from depsgraph)… not sure how this can happen?

Can you list out how to have multiple viewports with different collections visible in 2.8?

Thing is, new depsgraph in 2.7x is not maintained anymore, you should only try it in 2.8 nowadays. So unless you can reproduce that behavior in 2.8, this report should be archived imho…

Thanks @Bastien Montagne (mont29), I will take note of this to don't make this mistake in the future.

@Joshua Leung (aligorith) Could you take a look? It's no totally clear what you do here and why you use in sculpt the hash.

OK, I'm going to take a look how is done (this is not my code). I thought it was related to depshgraph issue.

Crash has nothing to do with depsgraph, you are storing ID pointers (material ones) in a ghash accross redo step, with invalidate any pointer in Blender… will check, think you have to rather store ref to ID by its lib/name pair. Also, ghash here is int key, not string ones…

This has been fixed I think (at least, cannot reproduce the crash anymore).

@nBurn (nBurn) transferred the page, link has been updated.