2D particle system for BM
Community Forums/Showcase/2D particle system for BM
| ||
Particle Dreams is an OpenSource project under LGPL license. It uses the standard Max2D module to take care that it will be compatible to other rendering modules than glmax2d as well. Features: - Particle Type based - Emitters can have any number of particle types attached Emitter properties - types can be (de)activated on a slot base with start and life time - emitters can be (de)actived on command as well as with a life time Particle Type properties - start time, life time - particle trails - size, variation, change per second - color, variation, change per second - speed, ... - alpha, ... - emission, ... - rotation - circular motion around its emitter - emission shapes *not finished* - emission angle (inner and outer) - gravitation, wind, groundheight and bounce properties - weight, variation - fully object oriented You might visit for further information and download: Particle Dreams |
| ||
Good to see this is LGPL! |
| ||
New version is out. I fixed quite some bugs and added a documentation Note: linux version will follow this evening when I return home to my linux box :D EDIT: Linux version is now online |
| ||
nice |
| ||
can we get some screenshots ? I am interested in this. :) |
| ||
I'm not sure what is happening with freeing memory but when I have just only 6000 particles and they start to be freed the system grinds to a halt. Also memory useage seems to be exponential - that can not be right. Ah your not freeing emitters either. |
| ||
@Indiepath: Hmm? Emitters are not freed if they end, they are just stoped for restarting. If you want them to be freed, a simple call does this including all their datas. The data of the particles is collected by BMs garbage collector. The memory usage does not drop for a long time if a BM app is running as garbage collectors don't give free memory directly to save time on later reallocs (this is the right value in memory output). memalloced only shows how much of that RAM is actually used within BMs Memoryblock (left value in memory output) There is nothing you can do about that behavior. Beside that there should everything be freed ... If not I'm interested in the situation to fix the problem. @Deux: I haven't usefull screenshots at the moment because this is a module, not an application ... when my showcase app is finished, I will add them :) |