This is quite tricky situation which combined: - Boolean modifier which accesses other object's derived mesh (in fact, it's nothing to do with boolean modifier, any other modifier which uses other's DM will have same bug). - Dependency cycles in the scene which is rather russian-roulette from the cycle solver point of view. - Multiple instanced objects used as boolean operand. With all this things combined boolean modifier was accessing operand's derived mesh which was referencing data from Mesh datablock. The issue is that those references are becoming invalid after EDBM_mesh_load(). This function already had code to make sure object itself does not end up with dangling pointers from derived mesh. Make it now so no possible instanced objects are left with dangling pointers. And who said it's a good idea to reference something from derived mesh..
38 KiB
38 KiB