Using particle2dx.com for CBEffects?

Gymbyl Coding
#1

There is a nice website http://particle2dx.com/ which lets us create great particles and export them to Corona SDK. However the particle engine is only avaliable for Pro+ subscribes, which poor collage students like myself cannot afford.

What if we could export json generated by the website into CBEffects? Technically this is quite simple to achive – just rename the fields to the ones CBEffects takes as arguments, but practically… I found myself not knowing what some fields stand for in both CBEffects and generated json.

To see the list of emmiter settings I opened_ CBEffects\cbe_core\vent_core\frame.lua. _

Is anybody else interested in this idea? How difficult is it to make it work?

#2

@Soin08,

I’ll let Caleb chime in with the official line, since CBEffects is his creation, but you’re talking about two different particle system styles:

  1. The particles exported from particle2dx.com are for use with the built in particle emitter object (Pro+ as you say).  This emitter is the display object and all the particles are not (AFAIK).

  2. In Caleb’s system each particle (emitted from a vent) is a display object (imageRect).

  3. Additionally, I don’t think Caleb’s emitter parameters are all compatible with those used by the built-in emitters.  Having said that, if Caleb had a way to import/convert those parameters into something meaningful and equivalent that would be cool.

My suggestion is you get the list of built-in parameters and compare them to CBEffect parameters to see if this is feasible.

#3

As roaminggamer said, CBEffects and particle2dx.com are different systems. I doubt that you can directly translate between CBEffects parameters and particle2dx.com parameters.

That said, I don’t see any problem with trying :). You can attempt it by making an example particle2dx.com effect and looking for a connection between particle2dx.com and CBEffects speeds, angles, etc., then try to automate that process. I don’t see it being extremely hard (famous last words), because most particle systems use approximately the same process (move X/Y vel each frame, tint, etc.).

  • C
#4

I am making a table of all CBEffects parameters in Excel and trying to match them up with those generated from article2dx.com. I will post my results here. If any questions pop up I will post them here as well…

@Roaminggamer, @Caleb P, thanks for your support.

#5

@Soin08,

Hi again.  I believe I may have misspoke or been confused above.  There are the following (and more) possibilities for particles now:

  1. New Emitter - Supported by  Pro+
  2. Physics Particle Systems - Supported by  Pro+
  3. Caleb’s (awsome) CBEffects - Supported by latest public release (2381).

#1 - The particles are not display objects.

#2 and #3 - The particles are display objects.

None of these has (fully) compatible parameter lists.  That said, it would be helpful to know where they overlap so thanks for putting in the effort to investigate this.

Cheers,

Ed

Hmmm updated again.  Latest public release (2381) still requires pro for some of the above features, which make sense.

#6

@Soin08,

I’ll let Caleb chime in with the official line, since CBEffects is his creation, but you’re talking about two different particle system styles:

  1. The particles exported from particle2dx.com are for use with the built in particle emitter object (Pro+ as you say).  This emitter is the display object and all the particles are not (AFAIK).

  2. In Caleb’s system each particle (emitted from a vent) is a display object (imageRect).

  3. Additionally, I don’t think Caleb’s emitter parameters are all compatible with those used by the built-in emitters.  Having said that, if Caleb had a way to import/convert those parameters into something meaningful and equivalent that would be cool.

My suggestion is you get the list of built-in parameters and compare them to CBEffect parameters to see if this is feasible.

#7

As roaminggamer said, CBEffects and particle2dx.com are different systems. I doubt that you can directly translate between CBEffects parameters and particle2dx.com parameters.

That said, I don’t see any problem with trying :). You can attempt it by making an example particle2dx.com effect and looking for a connection between particle2dx.com and CBEffects speeds, angles, etc., then try to automate that process. I don’t see it being extremely hard (famous last words), because most particle systems use approximately the same process (move X/Y vel each frame, tint, etc.).

  • C
#8

I am making a table of all CBEffects parameters in Excel and trying to match them up with those generated from article2dx.com. I will post my results here. If any questions pop up I will post them here as well…

@Roaminggamer, @Caleb P, thanks for your support.

#9

@Soin08,

Hi again.  I believe I may have misspoke or been confused above.  There are the following (and more) possibilities for particles now:

  1. New Emitter - Supported by  Pro+
  2. Physics Particle Systems - Supported by  Pro+
  3. Caleb’s (awsome) CBEffects - Supported by latest public release (2381).

#1 - The particles are not display objects.

#2 and #3 - The particles are display objects.

None of these has (fully) compatible parameter lists.  That said, it would be helpful to know where they overlap so thanks for putting in the effort to investigate this.

Cheers,

Ed

Hmmm updated again.  Latest public release (2381) still requires pro for some of the above features, which make sense.