You need to specify where and how you render.
The options visible on the screen are intended for the old Mantra, and now everyone is trying to render it in Karma in Solaris. there is a different principle for assigning materials.

The only important thing about buttons is the need for a button to temporarily enable or disable snapping. This is what we need to hammer home to developers.

It’s better to use the “reference image” node in obj, it seems to me. I got tired of using the background on the D key at one time, and I don’t touch it anymore.

This is an interesting question, I did some digging and realized that I have no idea how this works. Problems on both sides.
Problem #1 in blender - blender doesn't load attributes at all. But it loads groups of Houdini primitives as materials. This means we need to load groups of primitives into objects into the alembic.
And this is where Houdini's problems come in. Let's save the alembic and immediately load it back into Houdini, what will we see? First of all, Houdini doesn't categorically preserve some attribute names and I don't understand why. For example, the class attribute - it is not there after loading, but if you rename it, it will be loaded. Strangeness number 1, but not the last.
I moved the class attribute into primitives and turned it into groups. In the table we have 4 new groups g1, g2, g3, g4. But only one group g4 is loaded back. Why the first three groups disappear is completely unclear; renaming does not help. So the theoretically correct move - to write down groups in the alembik - actually does not work.
Well, the option to build a hierarchy had no effect. Although in fbx this hierarchy by name is built normally.
So maybe someone else can solve this puzzle?

Wow, guys, did you know that Houdini now has the option “Tangent Plane Snapping” for snapping to primitives? And now the object will snap exactly at the intersection of the axis of motion and the inclined plane, which was impossible in any way in 19.5. I've been asking Sidefx about this for a long time, but I didn't see it in the changelogs and thought they ignored it. But they did it somehow unnoticed by me. SideFx, I express my deep gratitude to you publicly! You made me happy! It’s funny, but recently I was modeling in Houdini, and was putting together a large scene in Blender, because there was a lot of similar object snapping, and I didn’t know that this snapping had finally appeared in Houdini. This is very cool ! Thanks a lot ! All you have to do is save the snapping settings to make the modelers completely happy. SideFx, you are great guys! Lately, you have pleasantly surprised me with the speed of improving the interface! Do not stop !

God, how pleased I am!

Guys, you will be surprised, but disconnecting a node is in the menu and you can simply assign a key to this action. I assigned X to myself and my node is disconnected, leaving the nodes above and below connected.

I'm frustrated by the "curve" node. It breaks Houdini with a probability close to 100% if you move the points in it a little. Although it is much more stable now, in version 20 it crashed almost immediately. But even now, when I launch the node, I understand that the crash of this file is inevitable. Very frustrating, I always need curves.

alexeyvanzhula1984
in the upcoming modeler edge flow was rewriten from scratch. now it is multithreaded and works much better.

I'm really looking forward to the new modeler !

By the way, I use edgeflow from the modeler and there is another free one on orbolt. In principle, they work fine. Of course, it's a pity that they are not in the original instruments.

I misunderstood your question at first.
As I understand it, the array index does not work in the table filter (which is quite strange), but you can do the same using a temporary wrangle - check the array element in the wrangle and set a certain temporary attribute to 1 and filter the table by this attribute.

Hurray, everything is fixed in 299! And binding to the center of primitives and to midpoints. Great job, sidefx! Thank you that we didn't have to wait 18 years. Now I can safely use the Vulkan.

I'm shocked, of course. 18 years of ignoring basic amenities and user requests... I definitely won’t live to see the correction.

And its not fixed in 298.

Nikyone
Could you please provide more details or specify what you are referring to?

Unfortunately, in build 297 they were completely broken, so I can’t even show them.

Question for the staff - how can I save the new settings for snapping? Every time I open Houdini I change these settings. Midpoint, attraction. Every time. A thousand times. And they are not saved in any way. But somewhere in the files are defaults stored? Please tell me where they are stored and I will change them directly in the file.

I really like everything, but a significant minus for me is the small font for the number of elements in the group. Why ? This is useful information, often necessary for debugging, and you have to strain your eyes to see it, while below there is a lot of rarely used information with large numbers that seems to have been created or modified with simply huge numbers. Who needs them? This is weird. Maybe you can think about the size of the numbers in groups?

Snapping to midpoint also doesn’t work on Vulcan, but it does in OpenGl. You didn't report this?

What should I use in the transform field, for example in the duplicate node, similar to SOP with bbox(0,D_XSIZE), to shift duplicates exactly by the size of the bound?

Yes, funny thing, I completely forgot about them. But you need a temporary binding using a hotkey or an automatic binding at the time of creation. But it turns out strange - without enabled snapping you cannot start placing an object correctly, and with it enabled you cannot finish placing it correctly. Ironic.