Updates on sodium and super fast particle system

http://binarydemons.com/~strike/files/sodiumupdate.JPG


Technical breakdown:
- Using two stacks to sort used and unused particle IDs. Calculated a 2000x increase in performance (using AMD CodeAnalyst) since destroying and creating particles is now O(1), and processing valid particles is O(N) where N is the number of used particles.
- The flags field in sodiumscript's AttachEmitter (0x00 in this example) can be used to specify emitter creation flags. With this, the scripter has the option of creating an emitter whose individual particles have unique fading speeds, color changing, scaling, etc. If these options are not needed, leaving flags to 0 will minimize memory usage and give a slight performance boost.
- Particle flags enable and disable features passed onto created particles. There is minimal overhead using this so each particle can be given its own set of unique flags by calling this directly before creating a particle (same goes for color, alpha, and scale).

I'd like to make a little music video / tech demo with all the stuff I'm putting in, but there's a few other things I need to finish up first (like sorting geometry and potentially multi-pass rendering and loading geometry into video card mem).

[Try to keep images <= 1024x768 -JG]

Um....okay..... maybe I'm just outta the current loop but whats this for? Looks purdy nonetheless. (tho not quite as yellow as I remember Na to be when I did my flames tests :p)

Oooh shiny. You on the SITH2 team yet?

P.S. Sodium particles taste bad. They kind of burn and generally feel icky.

You've got some nice effects going on there (for JK ) I hope you do join the Sith 2 team and implement some of this stuff.

wtf wait? you mean I spent 3 years perfecting explosion and plasma effects in jk and getting round the lameness of the engine and NOW you;re creating a new jk explosion system? this sucks (the program however, RULES)

if(getThingFlags(source) & 0x8){
  do her}
elseif(getThingFlags(source) & 0x4){
  do other babe}
else{
  do a dude}

Kyle, with every reference you make to your stupidity and science, I laugh even more.

I'm not stupid; I'm just suicidally curious.

He's not making a partical system for JK, he's making a partical system for his own engine based off of JK.

It's not based off of JK (an impossibility without the source code), it can just load some JK resources.

that's like, the definiton of basing an engine off another. without resources, the engine is useless, so it has to be tied to jk in some way.

Er, no it's not. Jedi Outcast engine = based off Quake 3 engine. Sith 2 != based off JK engine.

Um... no. JO IS Q3 with modifications. Sith2 is BASED on JK.

I meant the JO engine... content NOT EQUALS engine. Two separate entities. The engine that runs Jedi Outcast is based on the Q3A engine because it uses the Q3A source code as a base and adds many features on top of it. The game content that it runs, however, is NOT based on Q3A content.