Any way of, during and animation, breaking the connections between masses?
Picture this:- A box held by four chains which start at each of the top corners
of the box, and converge at a point above and at the center of the box. Then,
at frame 112 one of the "links" breaks leaving the box suspended (weight wise)
on two opposing lengths of chain. Then another one breaks an the box swings
aboot for a bit before coming to rest on the two remaining lengths'o'chain.
Setup so far is using a 2x2 array of mass points for the "box", followed by four
sets of "mass objects" connected together to simulate the chain/rope.
How would one go about simulating the breakage of one chain link?
(I've tried editing the MechSim file to trick it! It doesn't get fooled easily)
Cheers!
P.S. Viscoelastic simulation IS great!
arblick spule schrieb:
> > Setup so far is using a 2x2 array of mass points for the "box", followed by four> sets of "mass objects" connected together to simulate the chain/rope.> > How would one go about simulating the breakage of one chain link?> > (I've tried editing the MechSim file to trick it! It doesn't get fooled easily)
Why not?
A simple way to do that is accessing the simulation data from the scene
with the builtin hooks and manually writing out a simulation data file
using POV-Ray #write without the connection to break and using that as
input data for the next frame.
Sounds ugly but will probably work.
-- Christoph
Christoph Hormann <chr### [at] gmxde> wrote:
> arblick spule schrieb:> >> > Setup so far is using a 2x2 array of mass points for the "box", followed by four> > sets of "mass objects" connected together to simulate the chain/rope.> >> > How would one go about simulating the breakage of one chain link?> >> > (I've tried editing the MechSim file to trick it! It doesn't get fooled easily)>> Why not?>> A simple way to do that is accessing the simulation data from the scene> with the builtin hooks and manually writing out a simulation data file> using POV-Ray #write without the connection to break and using that as> input data for the next frame.>> Sounds ugly but will probably work.>> -- Christoph
Hmm, editing the MechSim file does work... ...the mind boggles!