I tried an idiot's implementation of this, it definitely works (the occlusion is white in this case).
Edit: Had forgotten to attach the hip. This one is against self, with a little bias. Would need to be nice-ified.
Found 329 posts.
Search results Show results as topic list.
Technical Discussion » Copernicus compute ambient occulision of Geometry
-
- protozoan
- 1796 posts
- Offline
Technical Discussion » Swimming noise with attribute VOP
-
- protozoan
- 1796 posts
- Offline
Hi,
you must feed the rest position into your noise instead of P, check the attached hip file.
*Edit: Oops, post was too slow
you must feed the rest position into your noise instead of P, check the attached hip file.
*Edit: Oops, post was too slow
Edited by protozoan - Feb. 20, 2025 10:18:11
Houdini Lounge » Is there a shortcut to "insert node between two nodes"?
-
- protozoan
- 1796 posts
- Offline
The only way I know how to do this specific thing (disclaimer: I sometimes do not know things) is to not select the node you want it inserted after, but to right click on its output, which opens the tab-menu, select or type subdivide, and then press enter twice.
So no keyboard only method.
So no keyboard only method.
Technical Discussion » How to: Camera Look At Primitive in Solaris?
-
- protozoan
- 1796 posts
- Offline
There are probably many ways to do this, here's one:
Stick your point position into a detail attribute (in SOPs), that automatically ends up in a primvar after the sopcreate.
Then add an Xform, and after that you put the previously stored primvar onto the xform as a translation.
Then you point the camera's look-at to the xform, and not the primitive where the position came from.
You also may want to cache this, which I have not done in this example (see attached).
Stick your point position into a detail attribute (in SOPs), that automatically ends up in a primvar after the sopcreate.
Then add an Xform, and after that you put the previously stored primvar onto the xform as a translation.
Then you point the camera's look-at to the xform, and not the primitive where the position came from.
You also may want to cache this, which I have not done in this example (see attached).
Technical Discussion » Seek help! I would like to know the correct way to use "karm
-
- protozoan
- 1796 posts
- Offline
This is expected behavior.
You can do it like this: Put a generic file name into the point cloud file parameter, like pcloud.0001.bgeo.sc
Append a edit material properties LOP after your material library.
Point its primpattern to your point cloud reader primitive, for example /materials/karmamaterial/kma_pcread1/
Press the "Create parameters" button, the parameters of that primitive will now appear underneath and can be modified.
Modify the point cloud file parameter to include the frame token, like pcloud.$F4.bgeo.sc
If you look at it in the geometry spreadsheet, you can now see that when you move on the timeline it will correctly update the primitive parameter.
A simplistic example file is attached.
You can do it like this: Put a generic file name into the point cloud file parameter, like pcloud.0001.bgeo.sc
Append a edit material properties LOP after your material library.
Point its primpattern to your point cloud reader primitive, for example /materials/karmamaterial/kma_pcread1/
Press the "Create parameters" button, the parameters of that primitive will now appear underneath and can be modified.
Modify the point cloud file parameter to include the frame token, like pcloud.$F4.bgeo.sc
If you look at it in the geometry spreadsheet, you can now see that when you move on the timeline it will correctly update the primitive parameter.
A simplistic example file is attached.
Houdini Lounge » ZOOM on tracked camera
-
- protozoan
- 1796 posts
- Offline
If by "zoom" you mean in the viewport only, without changing the actual render output (for example to see something you edit bigger and more clearly): On the left side of the viewport, there is a 'view' icon (small camera icon), if you right click that, you can change the mode from "3D camera" to "2D pan and zoom" which lets you zoom and pan around in the view as needed.
Houdini Lounge » Did the daily builds of 20.5 stop or change log stopped upd?
-
- protozoan
- 1796 posts
- Offline
If I had to guess I'd say that someone accidentally yanked the plug out of the wall that updates the changelog 
Solaris and Karma » How to preview a materialx node?
-
- protozoan
- 1796 posts
- Offline
Solaris and Karma » Can I render rounded edges in Karma XPU?
-
- protozoan
- 1796 posts
- Offline
The vop is called "Karma rounded edge", in Houdini 20.5.
You will find it when you are inside a Karma Material Builder.
The output of this goes into the "normal" input of the mtlxstandard_surface.
You will find it when you are inside a Karma Material Builder.
The output of this goes into the "normal" input of the mtlxstandard_surface.
Technical Discussion » Multi-socket EPYC System can't reach above 50% load
-
- protozoan
- 1796 posts
- Offline
One thing you should consider throwing some more money at is your memory. You got 64gb per socket, that's.. not great. You will likely run into trouble if you really put some parallel load on this box.
Technical Discussion » At which frame particle is generated？
-
- protozoan
- 1796 posts
- Offline
You multiply age by the FPS rate and that's your age in frames. Something like this:
floor(@age * (1 / @TimeInc));
Edited by protozoan - Oct. 16, 2024 09:29:33
Solaris and Karma » Karma is very slow ?
-
- protozoan
- 1796 posts
- Offline
If you can, post the scene file? So that others may dissect it and give hints on possible setting tweaks.
Solaris and Karma » KARMA MatX BUILDER / Auto build your textures ( wip )
-
- protozoan
- 1796 posts
- Offline
I would (strongly) recommend a different name. Because people might mix it up wit the official Karma Material Builder menu entry.
Solaris and Karma » Mtlx Normal missing the vector input in 20.5.332?
-
- protozoan
- 1796 posts
- Offline
Solaris and Karma » How to set dielectric priority for nested dielectrics?
-
- protozoan
- 1796 posts
- Offline
I *think* (someone correct me if I'm wrong) that the whole dielectric priority functionality isn't MTLX, but Karma-specific.
So you'll find it only in the Karma material builder.
There you can set them on the Karma Material Properties VOP, Shading section.
So you'll find it only in the Karma material builder.
There you can set them on the Karma Material Properties VOP, Shading section.
Technical Discussion » VEX: colormap and rawcolormap bugged?!
-
- protozoan
- 1796 posts
- Offline
If you have a windows client, often your network shares are mounted to a drive letter like "Z:\path\to\texture\sausage.rat". A UNC path works like this: "\\servername\path\to\textures\sausage.rat" (without the quotes)
Technical Discussion » VEX: colormap and rawcolormap bugged?!
-
- protozoan
- 1796 posts
- Offline
If it's a windows client and the network drive is an SMB share, one might try an UNC path.
For some people, this has helped in the past with certain access issues.
For some people, this has helped in the past with certain access issues.
Houdini Lounge » Topaz Plugin warning at launch of 20.5.313?
-
- protozoan
- 1796 posts
- Offline
Houdini 20.5 (Copernicus specifically) can digest OpenFX plugins, and when OpenFX plugin paths are set in the environment where it launches, it will try to touch them.
Technical Discussion » Node info window on Fedora
-
- protozoan
- 1796 posts
- Offline
Can you share some details about your window manager setup? Are you by any chance using wayland with the xwayland-compatibility layer to get X functionality?
Technical Discussion » Flakes in copernicus ?
-
- protozoan
- 1796 posts
- Offline
You can simply use sops for that.
Put down a grid with 2 rows, 2 columns, scatter some points, stick that into a voronoi fracture, add an enumerate sop, set it to primitives and the attribute name to "index".
Make a copnet, put down a sop import and point it to your grid, stick the output of that into a rasterize geo cop, add an output type ID, and set the name to index.
Done.
Edit: attached a small demo hip.
Put down a grid with 2 rows, 2 columns, scatter some points, stick that into a voronoi fracture, add an enumerate sop, set it to primitives and the attribute name to "index".
Make a copnet, put down a sop import and point it to your grid, stick the output of that into a rasterize geo cop, add an output type ID, and set the name to index.
Done.
Edit: attached a small demo hip.
Edited by protozoan - July 12, 2024 06:08:48
-
- Quick Links