eikonoklastes

@Alain2131Thank you kindly for your help. I should have clarified that this is a bit of a contrived setup as part of a learning exercise for compile blocks - I specifically want to learn how to reliably get them to work with complicated nested blocks. The generate_line_points wrangle was only created because I wanted to try plugging Block Begin into it, and the Line SOP doesn't have an input. That whole for each loop block is not required, and can be sorted with something simple like pscale, that will drive the line length as I need it. The Distance Along Geometry SOP just needs an internal named reference replaced with a spare input and it will compile. It's a minor oversight on SideFX's part; I've put in an RFE and they should fix it soon hopefully. Once again, thanks for your time, this forum is amazing.

Hi, can someone help me figure out how to fix the compile block error? I have a nested For Each Loop, and I likely need a Block Begin somewhere set to Fetch Input, but I can't figure out where. Reeds_test.hiplc

Slight modification to what Gorrod just posted. To keep things cleaner, set the Points per Point to 1, and define an attribute than returns between 10 & 20 randomly per point. The new Attribute Adjust Integer SOP is perfect for this.

I'm sorry, I'm still extremely confused. You mention a 6x6 inch grid, but I see a rectangle, not a square. Are you talking about each face being 6x6? Then you mention image 3 being an example of a 12x12 quad selection, but I see no 12x12 selection anywhere. It would really help if, rather than screenshots, you post a sketch of what you're after, or at least annotate over your screenshots, because I can't see what you're describing. Specifically, it would help if you could draw out exactly what "6x6" and "12x12" means.

The animation data is stored on the node you're keyframing. Shift+click the channel to bring up the Animation Editor for that track.

That documentation is for selecting gradient points in the Composite View, when working in a COP network. Is that what you're after, or are you referring to a ramp parameter in SOPs? If it's the latter, you can Ctrl+click to select non-contiguous points, or Shift+click to select a range in sequence. The visual indicator for the selection is pretty poor, but it does work.

I'm sorry, but I got completely lost. Can you post a couple of screenshots, preferably with sketches/annotations of what you're trying to achieve?

Sorry this is a bit off-topic, but surely the game engine you're running manages back-face culling by itself? Why manually delete perfectly good faces?

This was a bug that was fixed ages ago. You shouldn't be having this issue on any recent version of Houdini.

Make sure this is enabled:

If you install SideFX Labs, they add a handy option to the File menu, called 'Open Crashfile'.

This currently doesn't exist outside LOPs. Hopefully that changes soon.

Since you're in a Geometry network (SOPs), you're dealing with a single object, so it will export as a single object. There's probably a Python automation for this somewhere out there, but you need to basically follow these steps: Use a File SOP, set to Write, inside a For Each Primitive loop to export each face out to a separate file. Import all those files back into Houdini to create a separate Geometry network for each one (untick "Show sequences as one entry" in the import dialog and multi-select all the files as individuals entries). When using the FBX Export dialog, select only those objects as the Source Objects. That will give you a single FBX file with multiple, separate objects in them. Edit: There seems to be a bug currently (in both 18.0.499 and 18.0.532), where specifying multiple objects to export in the FBX export dialog results in a broken export (the file reimports empty). Using Alembic works, however. I've submitted a bug report, if you're having the same issue, please do the same.

Quad Remesher offers a 3-month subscription for $16. For the results it generates, that's a steal.

Here's a non-VEX approach, that doesn't even use any rotations. I'm applying a linear gradient across the top face, and then using a Soft Transform to move the points up based on that mask. You do need Labs for the Gradient SOP. columns01_soft_transform.hiplc