LukeLetellier

Did you ever find a solution to this?

Doh! Thanks!

I have a sparse sim in which several pyro events occur at different times & different places. As new elements are sourced into the sim, the overall bounds of the sim increase - sometimes dramatically changing the quality of the sim as the voxel size adjusts - see two back-to-back frames below. is there a way to maintain a consistent voxel size throughout the duration of the sim while using the sparse solver? Thanks, Luke

Thank you as well!

Great technique with the solver SOP! I just found that if you're emitting multiple objects per frame, instead of creating the patch name in the Vellum source, you can stick an Assemble in the Solver SOPs to create a piece attribute & do the for/each by piece. Very helpful when you have over a thousand objects to keep track of.

Great information. Thank you!

I wasn't sure how to phrase this, but I'm looking for a list in the documentation that outlines all of those quick relative references/shortcuts for referring to other nodes in expressions, along the lines of "." and ".." I'm specifically looking for a relative reference to the node that wires into the current node, so if there's a list of those hidden in the documentation somewhere, that'd be swell. Thanks! Luke

Spotted on Twitter. Do you people sleep?!

Here's the end result; thanks again for the help!

Yup, you're right. Everything works as you mentioned! I don't even need to split them apart manually at all, as the OSM importer already generated an attribute called "highway" that I can use. Thank you Henry!

How does one enable "Use SOP Path"? Its grayed out on my end. I've tried enabling the other options, thinking that one of them would do the trick, but I can't find the magic button. Thanks! Luke

Hello, I have a large group of road splines (generated by the lovely OSM Importer), and I've separated them into primitive groups based on their function (highway, residential, etc). I'd like to export all the road splines in a single alembic file (or another universal file format) in such a fashion that when it is re-imported (in my case, into C4D) the different splines are separated into separate Alembic spline objects. Currently, they import as a single object (even when I try importing them back into Houdini). I've also tried exporting them as point groups, but still they come back merged as a single object. Since there's thousands of splines as part of the OSM file, I can't simply split them up in C4D post-import & manage them that way. The only way for sure I know now is to export each spline group as a separate Alembic file (10-12 files total), and bring them into my scene one at a time - but I'd much rather have just one file. Demo file for testing: hSpline_Export.hiplc Demo Scene Node graph pre-export: Demo Scene Nodes once they are reimported as Alembic: Any thoughts? Thanks! Luke

Since they don't mention anything about why they're no longer developing, I'd say they were bought out.

Thank you! After a few more adjustments, this is working great.