>
> BTW, I'd never be able to work with code in printed form...
>

Why not? It's like reading a book... Well, okay, like reading ten
related books alongside each other - but hey, we're all up
to multi-tasking, or not? ;)

>
> > Aha. So we're approacing a particle rush?
>
> Not a rush, I've just decided not to implement too many new things and
> consentrate on getting the first version ready for release instead.
>

Well, then you'll also have to keep backward-compability in mind... Not
that I'd think you'd forget that, but just in case you need a reminder...

>
> > If you post yours, and it gets popular, mine won't
> > have a chance... Ah, well.
>
> Well, I for one would probably use it if it's flexible enough. Does it allow
> me to get access to a particular particle's location at any time? For
> example I'd like to know particle X's location at clock=0.6 even though the
> clock of the scene is currently only at 0.3. That's not possible with my
> system but I imagine it could be possible with yours because of the way it
> works.
>
> You see, if that's possible, i could use each particle in your system as an
> emitter in my own system and that way get some truely interesting effects.
> :D

You know, another interesting thingy about the way my system works:
I can calculate one set of particles, save their data, reload it as
emitters for another set of particles... But since my system can't keep
track of existant particles constantly (it would be very parsing and
calculating intensive, to know for each particle, which particle has caused
it, and when...), yours and mine could make a very good combination...

Perhaps when yours is out, we can have a combined look at how we can
make them fit together well and easy?

--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html

Post a reply to this message