HOME | DD

Description
No fancy info boxes are built in so listen up:

Gravity is pretty simple. This value is added to the y velocity of each particle every frame. It can be neggative and really large... but expect things to break when you put it higher.

Bounce is the number the y velocity (well, relative to the line) is multiplied by when a line collision is detected. This means it's neggative. -1 would be no velocity is lost when it bounces, below that would be physically impossible in the real world as energy would be being added to the particle.

Gravitate to the Mouse simply turns on and off gravitation to the mouse. No constants can be changed in this version.

Trail Fade is the number that is subtracted from each trail segment on each frame. This means that 0 would make the trails not fade at all, but they do have a maximum length. The lower the number the more CPU it takes. I made the scale non-linear so that you have finar adjustment when the numbers get smaller.

Lines:
- Drag them from the center.
- Stretch them from the ends.
- Rotate them from anywhere else.

The only bugs that I know of are on a perfectly straight line the particles will sometimes fall through when they are not bouncing at all.

This took a fair amount of time to make and it would have taken much longer without:
smurfMX
Some of the guys from #flash on efnet.
And bit-101 where I originally got the idea from.

Description
No fancy info boxes are built in so listen up:

Gravity is pretty simple. This value is added to the y velocity of each particle every frame. It can be neggative and really large... but expect things to break when you put it higher.

Bounce is the number the y velocity (well, relative to the line) is multiplied by when a line collision is detected. This means it's neggative. -1 would be no velocity is lost when it bounces, below that would be physically impossible in the real world as energy would be being added to the particle.

Gravitate to the Mouse simply turns on and off gravitation to the mouse. No constants can be changed in this version.

Trail Fade is the number that is subtracted from each trail segment on each frame. This means that 0 would make the trails not fade at all, but they do have a maximum length. The lower the number the more CPU it takes. I made the scale non-linear so that you have finar adjustment when the numbers get smaller.

Lines:
- Drag them from the center.
- Stretch them from the ends.
- Rotate them from anywhere else.

The only bugs that I know of are on a perfectly straight line the particles will sometimes fall through when they are not bouncing at all.

This took a fair amount of time to make and it would have taken much longer without:
smurfMX
Some of the guys from #flash on efnet.
And bit-101 where I originally got the idea from.