Hey Gith, It's true, the distance from point to point is a scalar and the point's position is a vector. To have your particles spread out, you'd want to move each point away from the neighboring points. My suggestion is to use self.pointposition minus the average neighbor position. That gives you th...

oh... I noticed later on that some of the compounds were broken and despite having used them previously they didn't appear to do what I intended them to... But it's crunch time at work. Joy! I hope to fix what's there and add more funky things later... I don't know what I was thinking when I uploade...

yes! ...almost They aren't random, they're a reasonably even distribution of vectors. if you mapped them all out it would look like an icosahedron. If I knew how to define an even 3d distribution of directions mathematically I would have, but I haven't the knowledge. note that a regular sphere is no...

There isn't a built-in solution to avoiding the overlapping of particles when they spawn. I fiddled around and here's what worked reasonably well for me. - get the closest points (within a range, the distance apart you want the particles to be) - find the average position - get the distance from eac...

I sent an email back on the 23rd to uploads at this website.com, but I got bored of waiting for an answer or post, so I'm putting up a couple more nodes from my website. Then again, maybe there are virii inside! Obviously download at your own risk from an external source. Y'know, having online space...

I read this and thought it was a cool idea so I challenged myself to make up a scene that does the same thing differently. It worked too, well enough. pictures are big so I'll just link them though, instead of embedding. Instead of using closest point queries, I used statistics. Assuming there is on...

You could, if you wanted to, explore inside the "state" node. Within the state node there's a Simulate Particles node built in. You can replace that with Simulate Rigid Bodies and whichever collision objects you need plugged into it. some cons to this approach though: - You'd have to do th...

Expose value hack. you use it when you want to expose the value of a branch you're building, but haven't gotten to the point where it actually plugs into anything in your ICETree. Like if you want to know the average number of neighboring points each particle has within a radius. you can easily grab...

added a couple more: *Transform.xsicompound -- We all know that SI doesn't like it by default if you try to modify kinematics. Some of us know that you can multiply an object by a matrix to achieve the same effect (although the pivot point stays still) That's what this node does: you execute it and ...

there! near the bottom is Compounds.zip -- I wonder how the php files gets the order of these files?

I just stuffed a really simple php file in there (14 lines!) to display the files in the folder. Maybe later I'll make it pretty and more useable...

yeah. except Nifty Particle Denter.xsicompound. And any other exceptions in italics. Also, the Refract Through Surface is like 90% of "Bounce Off Surface" heh, the list isn't even in alphabetical order. I guess I COULD zip 'em up. :| get 7-zip. it works a billion times better than winzip b...

http://joepolygon.com/ice/fi.php Added Feb 27th, 2010: ================== *Emit Particle Tree.1.1.xsicompound (Direct Link) -- Ok, so I'm not very good at condensing cool constructions into a single node, but I think I did a good job here. Only one problem is that you need to have two point clouds ...