POV-Ray : Newsgroups : povray.binaries.animations : Particle matrix effect with I/O (277kb mpg) : Re: Particle matrix effect with I/O (277kb mpg) Server Time
19 Jul 2024 19:24:11 EDT (-0400)
  Re: Particle matrix effect with I/O (277kb mpg)  
From: Mark James Lewin
Date: 3 Nov 2002 18:31:22
Message: <3DC5B1C2.20802@yahoo.com.au>
I haven't tried it yet (hopefully will in a few days), but assuming

V(new) = V(old) + Acceleration*Delta_Time
P(new) = P(old) + V(new)*Delta_Time

I cannot see too much trouble with negative Delta_Time values so long as the 
Acceleration term is constant. Environmental collisions shouldn't be too much of 
a problem either. Am I missing something here?

As for saving particle data for each frame, I do this sometimes to make 
re-rendering a slow-parsing animation faster (eg. if I want to change how the 
particles are textured). I can typically save data for 1500-2500 particles before 
the data files get larger than a 320X240 frame saved in an uncompressed format. I 
don't see this as a major problem considering hard disk sizes nowadays.

MJL

Rune wrote:
> Slowing down to a stop I can understand, but I can't see how you can
> make it run backwards, without having to recalculate everything from
> scratch in those frames that run backwards (which would parse very
> slowly). Unless of course you save the data for each calculation step so
> that you have at once the data for the entire simulation, as opposed to
> just for one frame at a time. But that can require quite big amounts of
> space for simulations with many particles...


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.