In T37578#189565, @Lukas Toenne (lukastoenne) wrote:

Reading/writing cache files simultaneously should be as smooth as possible. I have to investigate the details of how Alembic files can be accessed more-or-less simultaneously, but generally it should follow a one writer / multiple readers model.

Hm strange, saw a crash once here (when pind->kkey[1]->time wasnt accessible)
but cannot reproduce ever since...

Hi, any news on this bug? It really makes it impossible to use Blender as generator of fluid simulations for use in other apps. This should be high priority, because all the work spent by someone to make Blender support VDB is negated by this unwise file naming. I mean if you are doing sims to be used in Blender, you can just use the default point cache. VDB makes sense mainly because of interoperability with other 3D packages, yet this interoperability is broken for exactly this reason :(

Thanx for getting back [and for finding a workaround/solution]
I'll archive this then (though it is still not completely clear whether this is intended behaviour or not -- but report can always be reopened or found as reference)

In T55151#504978, @Philipp Oeser (lichtwerk) wrote:

This is actually working as intended, so calling this "corrupted" is not really appropriate.
I agree though that flipping index and framenumber would probably have benefits in a pipeline involving other software.
This could certainly be done [would need to take care of reading both naming-conventions then...].

Dont think this is a bug [more of a TODO - if at all], but maybe @Brecht Van Lommel (brecht) or @Sybren A. Stüvel (sybren) have a comment?

This is actually working as intended, so calling this "corrupted" is not really appropriate.
I agree though that flipping index and framenumber would probably have benefits in a pipeline involving other software.
This could certainly be done [would need to take care of reading both naming-conventions then...].

I'll look into Alembic separately

commited rB5e7a21a5f549

I did solve this with majoy difficulty.

is this bug found? will it have a solution?

This doesnt seem to be related to a ParticleSystem in particular.
It just works well with object transformations on the target (same as your First Layer example), but not so well with object data transformations...

Though this might be inconvenient, this seems to be by design (and not a bug) then.

OK, will have a look

Yeah, rotation sliding on Z is bothering me

Sorry this report hasnt been answered in quite a while.

Lukas T. I just hope what this doesnt go in perpendicular with your work in hair_guides branch.

Your objects geometries have very long/thin faces which makes it harder/impossible for the simulation to end up being somewhat realistic (lack of edges to bend at).
So without going into details (you should be able to find plenty of tutorials online), you should already end up with something more pleasing by just adding a couple of edgeloops in your file like here:

Ah, sorry, having a look now...

I did, it is beside my graphics card version on the link "F2596406". I know, that's a weird place, I don't know why it's there. I just drag and dropped it.

could you please upload your example file, so we can have a look?

Is it possible to work around it using Python?

Thanks Sergey!
You are right about new particles messing up old projects.
Is it possible to work around it using Python?

Thanks for the report, but it was already fixed in rB35ee9ff.

Ok, so now crash seems to have disappeared again. Issue with rendering remains though. :)

Committed modified patch rBb0af44fa4d7a2e134b315c49a4fbdf573f781004

I apologize for only getting back to you now. Your CMake definition of "LBM_GZIP_OPEN_FN" is not working and I'm not experienced enough with CMake to figure out a solution.

I can confirm that enabling/disabling X-mirror in Edit mode enables/disables it for Particle Edit mode, too.
Particle Edit mode re-uses Edit mode tools to manipulate particles.

Seems like the .blend is missing?

Can confirm this, D3008: T53823: prevent crash prevents the crash, but maybe we should spend time making sure we only have the weight brush available for hair? (@Campbell Barton (campbellbarton) : I could have a look if this is worth the time...)