Is there actually a reasonable tutorial for the latest version of MPE?

I've been struggling with it for some time now. Initially, I downloaded the latest version from this site, and incorporated it into my project by including the libraries in the relevant places.

I tried loading a ParticleEffect from an xml file, which proved in itself to be a difficult enough task, and then I tried drawing it. It's at this stage I find it is essentially impossible to get the thing to work.

I tried, first off, to create a SpriteBatchRenderer and tell it to render particles to the screen. That worked. Then I gave it the camera matrix. The ParticleEffect rendered completely in the wrong place.

From this point, I had a collection of ridiculous issues, such as the ParticleEffect not following the camera correctly, not being correctly aligned with the camera, having it always be stuck where the camera is DESPITE changing the trigger position constantly, and having the particles from the emitter constantly change location to match the position of the camera (counter-intuitive)

I eventually, after much googling, decided to try and write my own, primitive, Renderer. I downloaded an older version of Mercury (I can't even get the latest one to load files) and incorporated it into my solution. I wrote up my own primitive renderer fairly quickly - it iterates through each Emitter in the Effect, and calls SpriteBatch with the relevant BlendState, then draws each of the particles per effect with the correct settings. The result looked nothing like the Editor - and I'm not sure why. Sometimes, the particles didn't remove themselves properly; they just stayed on the screen.

I'm here in the hopes of getting some help - maybe somebody could take a short while to try and explain how to get the latest version of Mercury to actually work - the documentation on the site is of no help at all :(. I think the editor is great, and I'd just love to get some help on incorporating those effects with my game. I'd made another thread about the camera alignment issues, but didn't garner a response.

Additionally, the latest version of the source code seems bugged - in that the Editor has a strange offset on the particle trigger.

Any responses would be much welcomed - in need of some help :(

I've had similar issues. I got an older version of the binaries working in my project where I could create an effect in the editor and use it in my game, using 2D coordinates. But this didn't give me access to the source code, so I finally decided to get the latest source and fix the issues with the editor not being in the solution and a bunch of other build issues. After this, I realized the support for rendering in 2D is no longer there and the system only uses 3D coordinates, which is a pain for my project.

It doesn't seem like there's much documentation anywhere, and all the documentation I do find online is for older source code so it doesn't apply, so I'm just relying on the solution's TestBench project as an example.

Editor isn't working, either.  I can't seem to import or export anything.  The buttons just simply don't work.

So, we are stuck in v3.1

Well I've got a project up and running, and the editor works except it doesn't load most of the examples they supply. I haven't tested making new effects yet, so I don't know if all the emitters and controllers work in the editor and export properly.

I'm just plowing through without any documentation to try to figure out how this library works. After a bunch of attempts at getting proxies working, I'm realizing they aren't intended to be used the way I thought (I can't find any documentation anywhere that talks about this object). I thought they were intended to be used as the "instances" of a particle effect, but it appears they are just used to render the same effect multiple times. I can't seem to get the proxy translation working.

So I guess I have to rely on using DeepCopy to make multiple versions of the same effect.

you can load the examples supplied but you do so by using the import -> default serialiser menu option instead and they work fine from the little I've played with them.