ALE lurker

Ye, but it seem to me the window to the left kinda mixes parenthesis and pairing, which honestly are two very different things, one is basically nesting transformation matrices and the other telling which emitter instance shoots what particle instance and which particle instances are affected by which field instances. Which leads me into another question - how do you deal with multiple instances of same nodes? Do you allow them there? Because that’s very handy and certain results can be accomplished only through that, like the in video above.

Also, straight off the bat - I want to betatest it for start

Aha, that’s cool. So what about parenthesis then? Like sometimes say you’d have emitter having translation animation and you’d want particle to move along with it. Or kind of like nest even same instances one on top of another making funky animations like this:

http://www.youtube.com/watch?v=v8sXwHNKwHY

MeshAppearance is in few effects in vanilla but they’re never actually used and having them spawned by emitter simply crashed the game. Probably was supposed to spawn sort of asteroid fields in THN scenes. But it is kinda unclear what MeshName is supposed to refer to. Not a filename, not a mesh in petaldb, not a vmeshdata name if embedded into ale file (since they’re utf files anyway). Granted it was all just trial and error, I never dug into alchemy dll with debuggers.

Ah, that’s where you’re wrong I’m afraid. Parenthesis and pairing (or who-uses-what, as in what particle emitter uses, etc) are entirely independent, in fact they have no relation whatsoever. You certainly can set one emitter instance to be a parent of another. So then if you have animation on parent it’ll of course affect the ‘child’ emitter since parenthesis (the second argument of each node instance listed in ALEffectLib) simply means that the child node instance inherits its parent node instance transformation matrix, better yet you can nest them for many levels like that. You can drop off say radialfield, by giving it 32768 for parent and it’ll be now in relation to scene or system rather than where effect is.

On my video above it’s actually just one CubeEmitter and one FLBeamAppearance. In ALEffectLib there are four instances of same emitter, and four instances of same particle. CubeEmitter has simple rotation loop in its NodeTransform block. If that emitter instances were attached to root then they’d simply all shoot at same angles, effectively quadrupling beam intensity since the beam particles just overlap. However if goes like this:

instanceID, parentID, type, name
1, 32768, 1, 0xEE223B51
2, 1, 0, beam.emt
3, 2, 0, beam.emt
4, 3, 0, beam.emt
5, 4, 0, beam.emt

you get what you see in that video because transformation matrices stack for as many parent nodes you have in chain, with the last beam.emt node essentially multiplying all of its predecessors and then of course applying its own.

Yes, pairing hierarchy is somewhat that, but there are few interesting tidbits. Just to be clear on what I mean I imply instances that are defined in ALEffectLib as there can be multiple instances of same node from AlchemyNodeLibrary. Here’s what I had observed. Like mentioned earlier a single particle instance can have multiple emitters spawning it (same instances or even entirely different nodes), although one emitter instance can spawn only one particle instance. One particle can be affected by multiple field instaces, although some fields will override almost every other, like AirField, but some can have combined effect on same particle. Also one field instance can affect multiple particle instances.

I don’t have xml from that particular effect since it was just a test one I did a long time ago, but here’s more recent and using same, if not more advanced, approach: grab from pastebin. And you can see it in action at this video when the door starts to open (it’s the one from another thread).

Effectively any node can be stacked to any other node, this is because any node can have own transformation matrix. Heck I even use FxNode which does absolutely nothing at all but can be used for something like a rotation pivot for other nodes (see code in pastebin link above). And you might be surprised what interesting effects can be accomplished by rather unorthodox things like setting appearance to be parent for emitter when you start to animate them all together, so yeah there’s definitely use for that too.

Four floats in effect header in ALEffectLib seem do absolutely nothing, at least no matter what values I set there I couldn’t see any observable difference. Probably unused stuff, much like the unfortunate MeshAppearance and several other properties like NodeClass that kinda do nothing.

Thanks. Although I did find them a while ago but then simply forgot to add them to the doc as well, it (doc) hadn’t seen much use beside myself unfortunately, as a result had been rarely updated.

Here’s the crazy map effect from first post to test your editor. Just replace particle sprite names with your own since I use my own sprite library and not vanilla txms.

@adoxa:

And enabling them just crashes the game.

@Skotty:

Actually no, it’s not missing, it is briefly explained in EffectInstance section. In fact it’s not related to presence or absence of root node (the one with type set to 1). Simply put parent 32768 is world coordinates, except for type 1 root node which serves as a proxy to wherever effect coordinates are and whatever it might be attached to. This is why say particles with parent 32768 wouldn’t move with effect, their transformation matrix doesn’t inherit from root node, instead it is world space. And similarly nothing stops you from having emitters and fields at world coordinates instead, in fact it can be used to create interesting features, like a world gravity for particles which would be unrelated as to what orientation the effect has if attached to something. Or say a radial field placed in world space, and say it may attract particles from your dust effect, like say around some anomaly. Of course that would make effect rather specific to a system as translation offset for radial field would have to match coordinates of where you had placed some anomaly object in system, but there it is.

One more suggestion for edit. You have a time slider at the bottom. Add another slider there for sparam as well. That would help to test things like engine effects, to simulate how they would change in game based on engine usage, cruise mode. Thrusters too use sparam, and finally you can add “use_throttle” for AttachedFX to make attachable effect to be dependent on your engine (but sacrificing 0.9 - 1.0 sparam range that would be used for cruise mode).

0x03503B61 and 0x0ABE0402 appear to be aliases for DupeFirst and DisablePlaceholder respectively.

0x0BA0B3BB also present at beam particles, type of transformation matrix, but seem does nothing.

0xE63AA248 appears in FLDustField, also seemingly no effect.

Yes, I’ve tried and predictably figured out that fields don’t affect node’s transformation matrix, so they wouldn’t have any visible effect on emitters themselves, may not be obvious at first but it is logical since they just affect individual particles vectors. Particle (appearance) nodes are essentially collections of particles, a grouping and instancing mechanism, so transformation matrix in appearance node is applied to them as a whole and not individually. This can be clearly observed when you start to adjust and/or animate scaling.

0xE63AA248 probably existed in their effect composition tool, hence its strange appearance in the vanilla file, but I assume it was never coded to be used in the first place.

Test effect for meshapperance is in attachment.

[VisEffect]
nickname = test_mesh
alchemy = fx\misc\test_mesh.ale
effect_crc = -257469979