Hot Particles - particle editor

[ReFreezed]

That would be great for placing stuff on a background image

Yeah, I was thinking that.

How would I put this in the main.lua ? So I can access a parameter say on particleDatas[2] for example.

Just access parameters with the dot syntax. In the example there are two particle systems, which means these two code snippets do the same thing:

Code: Select all

for _, particleData in ipairs(particleDatas) do
	particleData.system:update(dt)
end

Code: Select all

particleDatas[1].system:update(dt) -- Use the dot to access table fields.
particleDatas[2].system:update(dt)

Look at the Lua manual if you're unsure about syntax rules in Lua.

Also what part do shaders play ?

You can specify a custom shader in the program if you want to render particles in a different way. If you're not using shaders then just ignore/exclude everything shader-related.

[Jayverb]

@ReFreezed
Gotcha ! That's exactly what I needed to know, Thanks !
So am I writing

Code: Select all

particleDatas[1].system:setPosition(x-200,y-200)

and that should do the trick keeping local intact.. because system=ps ?
I have looked into shaders and yes that's a whole other kettle of fish
Looking forward to spending some time creating some assets.
I have to say that this feels like the perfect place to start with love2d using your program as a basis, it's a hella lot of fun.

[ReFreezed]

Update 1.8

Changes since 1.7:

• Particle systems can now have individual position offsets.
• Fixed particle path previews not using the specified area distribution.
• Templates: Values have been moved to the 'exported' namespace (i.e. particleSystems is now exported.particleSystems). (Values are also available in the old place so existing templates still work.)
• Templates: Added exported.emitterPosition and exported.particleSystems[n].emitterOffset.
• Templates: Deprecated exported.particleSystems[n].offset. (Use exported.particleSystems[n].textureOffset instead.) ('offset' is an alias for 'textureOffset' so existing templates still work.)
• Templates: exported.particleSystems[n].texturePreset is now empty if a custom texture is used.
• The default templates have been updated.

I've also updated the examples repository.

[Jayverb]

Re Update 1.8,
Thanks for this ! Happy days

[Jayverb]

@ReFreezed
Does this mean we can overlay on top of a background image to export and emitter positions will be correct ?
Will have to test asap, thanks again !

[ReFreezed]

@Jayverb
Yes. Just look at what the updated default exporter outputs to see where you can get the coordinates.
No problem!

[ReFreezed]

Update 1.9

Changes since 1.8:

• Particle color gradients can be saved and loaded. (Right-click on the preview.)
• Fixed slider handle position being slightly off while dragging.
• Exporter: Updated dialog to show all files that will be exported, and if they overwrite anything, at the bottom.
• Templates: print() now prints to the log.
• File browser: Click in the file list and type to search.
• File browser: Enable name filter for the file list by entering a filename with an asterisk (e.g. "*.lua").

[4xEmpire]

This is extremely useful, ReFreezed.

Thank you for posting this. I'll let you know if I have any feedback!

[ReFreezed]

@4xEmpire I'm glad you find it useful.

[ChicoGameDev]

Hi,

Amazing tool !

I can't start the MacOS 1.9.0 release, it's says I don't have authorizations to open it. I don't get it, it's not even blocked by the security and all the rights are on read/write.

Any idea why?


Thanks