Exporting GPU Particles out of Ember

Chiming in since I’m having a lot of issues getting usable particles into Houdini.
Summarizing the above, it seems like the current issues are:

  • inconsistent id values
  • no usable age attribute
  • no animated color attribute
  • nan positions

I haven’t come across the last 2, but the first 2 issues basically make particle exports unusable for any use case I can think of.

Someone mentioned a list of known issues. Where can I find that?
How do we track the progress of these issues?

1 Like

The issue is on our GitHub where we keep track of all software issues. There aren’t any publicly facing updates but we will certainly notify everyone when we have progress. And tbh, after we test internally we may reach out to you and @Andrej730 with the specific build so that we can be sure it works for your use cases as well. But hard to tell when that will be, having to code alembic exports from scratch isn’t super easy and there isn’t a lot of documentation on the matter.

1 Like

Faced now the problem of no age attribute in abc when importing it into blender. Any updates on this problem? More precisely, what does the lifetime setting do at all when exporting?

Hey sorry, no updates on this yet but our focus after this week will be fixing and refining all of these issues now that LiquiGen is out.

Very looking forward to the fix for the inconsistent exported particles ids - it currently breaks any attemps to tweak particles outside Embergen (e.g. in Niagara) and seems to also break motion blur in some cases.

1 Like

We now have a public roadmap and will periodically add potential bugs to upcoming patches if they’re significant enough. For general alembic particle exports we’ve created a card here: https://jangafx.com/roadmap?feature=fa0b261d-31b1-4c99-8b0e-c5a3835a15f3

Currently it being fixed for EmberGen 1.x is up in the air because of how we coded the particle system initially. By design we weren’t planning for alembic exports, only image based exports, and as such alembic was sorta shoehorned in. In 2.0 we’re rebuilding it from the ground up and will ensure that alembic exports work natively. We’re going to try our best to patch this, but may not be possible.

1 Like

@Andrej730 @stevedeegreen @Noveles @anakin78z We just recently put out a pre-release version of EmberGen available to those in our discord channel who have a subscription with us and have linked their accounts. This has Alembic particle fixes that we would love for you all to test if you can. Please let us know if this works for you or if you have any questions!

Great news! Just tested - issues with nan values seems to be gone and ids are consistent now, it is a great breakthrough, as it allows to do all kind of stuff later in Niagara or in other particle system. Will test further.

1 Like

Still can confirm that ids are stable, but found a few issues:

  1. Exported alembic with all particle attributes enabled (Cd, density, age, size)

but exported alembic has just pos, id, v:

image

  1. Second problem we found that if you export a lot of particles there are multiple particles reusing the same ids. Though they seem to share the same attributes, but it seems like a redundant data and it’s hard to predict how some other particle system might interpretet them, so it is an issue.