They, i've been researching and test lately. I'm goin to work on my particle engine soon, but i heard something interesting, making them on a single surface system. So i'm guessing u draw all your sprites on one surface or something like that. Well, first thing i'm goin to do with my particle system is have a triangliar and rectangliar sprite system. I think that 2 tris is over kill in some cases (like a ball in a center of a texture. Just use one tri for that). So i'm guessing, I should make all my sprites as part of one BIG mesh instead of having many small meshes. Well, that sounds like an alright idea in some cases, but i won't be able to do some of the effects i'll probably want.
Also animation wouldn't be based on move/position entity right, i'll have to recal all the vertices in the mesh if i want them to move kinda independly of one another. Would using a vertice repositioning code be faster than using positionentity?
Single Surface sounds great for clouds.
Multi Surface sounds great for rocks(the way i'm building it, u can just slap in an entity u want overall. So u can have a 3d rock spin with all the cals for movement) shooting out and having a smoke trail behind it(again, make the spawnpoint based on entities(mesh, to pivots). SO u can have the rock position as a spawn point automaticly) that does it's own thing(use global position to keep the smoke in one place and hae it alpha out).
I'm thinking that'll be clearer and better than tryin to use a single surface system for that. Plus i can still have collision one the rocks.
So what do u think? Should i have a mix system with optional single and multi surface options. Should i have the system be "partcile type" depend. So say the rock is multi surface system, but the smoke coming from the rock that just stays there in the sky...maybe have that single surface?
Is the speed increase worth it? I would run test myself...but i haven't the time lately :(.
Thanks for your help.
Also animation wouldn't be based on move/position entity right, i'll have to recal all the vertices in the mesh if i want them to move kinda independly of one another. Would using a vertice repositioning code be faster than using positionentity?
Single Surface sounds great for clouds.
Multi Surface sounds great for rocks(the way i'm building it, u can just slap in an entity u want overall. So u can have a 3d rock spin with all the cals for movement) shooting out and having a smoke trail behind it(again, make the spawnpoint based on entities(mesh, to pivots). SO u can have the rock position as a spawn point automaticly) that does it's own thing(use global position to keep the smoke in one place and hae it alpha out).
I'm thinking that'll be clearer and better than tryin to use a single surface system for that. Plus i can still have collision one the rocks.
So what do u think? Should i have a mix system with optional single and multi surface options. Should i have the system be "partcile type" depend. So say the rock is multi surface system, but the smoke coming from the rock that just stays there in the sky...maybe have that single surface?
Is the speed increase worth it? I would run test myself...but i haven't the time lately :(.
Thanks for your help.