Howitzer99
-
Content count
57 -
Donations
0.00 CAD -
Joined
-
Last visited
-
Days Won
1
-
On the surface, it's not much different. Looking at the update info, there are more refined toolsets underneath. Like 2.0 versions of existing tools, and that it's working in H18.
-
In your scene file, I placed a new poly sphere down, and linked to your mesh light. Worked as expected. In the image below, I just disabled the camera visibility for the light. When I opened your scene file, the sphere you were using was hidden, which also hides the affect of the mesh light. Not sure which forum hip files you're referring to. Hopefully this helps.
-
Yes, definitely put your custom VEXpressions.txt in the user directory, much safer than editing the original file. The user directory VEXpressionl.txt file will get automatically appended to the SESI version, so only add the custom expressions starting from a blank file (not a copy of the SESI version).
-
It's actually from the Modeler 1.0.4 manual, must be included by mistake. Thanks, I'll see if I can create my own menus. I like the idea of having a larger subset of the tools in a single menu, instead of my full-screen menu invoked with the space bar. Overall, the tools are quite handy, a bit cryptic, but has helped with some modeling tasks I've had recently. Hopefully the menus will be enhanced in future releases, as well as the documentation, and updated tutorials.
-
Thanks Andy, I'll try the smaller Edit Mesh menus. I guess what I'm looking for is the older style with the Zone Menu setup (page 20 in the Modeler manual). Maybe the manual was just pasted from an earlier version, since there is no menu on the shelf to hotkey to, per the instructions.
-
Yup, that's the method. You need to have an existing pane for KitBash to spawn into. I haven't played around with it too much, but does look pretty useful.
-
Does anyone know where we actually go for support with Modeler? Was hoping Alexey would be more active here. Needing to get some of the setup issues resolved.
-
I was looking for that as well, it looks like it doesn't have them? Reading some of the older docs, you needed to set a hotkey for the menu item, but I'm not seeing a menu item for Zone Menus. Alexey, are the Zone Menus coming in a future release? Also, I'm still having issues with errors when launching Houdini, even when removing the two lines from the key config that you mention in the docs.
-
Convert particle velocity to colour
Howitzer99 replied to RudyardKipling's topic in General Houdini Questions
Here's one way to recolor the particles based on their velocity. You would use Cd to drive your custom AOV, depending on your renderer. v_to_cd.hiplc -
Automatically remove interior from double-sided geometry
Howitzer99 replied to mottosso's topic in Modeling
Cool, the measure idea is a nice way to ensure you don't remove the large groups. I believe the Group Expand node is new to Houdini 18, just FYI. -
One way would be to first transform the points into uv space. You can achieve this by adding a VertexSplit node to the end, and then using a PointWrangle with this: @P = @uv; The vertexsplit makes any shared vertex in unique points. You could then create a square-format orthographic camera and render the mesh using the Cd value for the constant color, and align it as close as you can to the original uv layout position. Screenshot below of Flip. p_to_uv.hipnc
-
Cool, glad I could help. Additionally, I have having some issues with the hotkeys throwing errors, even after removing the two lines stated in the manual. Anyone else have this problem with this?
-
Redshift OCIO FAIL after adding camera Tag
Howitzer99 replied to bruchhagevfx's topic in Lighting & Rendering
By tag, you mean the CamParms button on the Redshift sheft, correct? I'm on Houdini 18.0.348 and RS 3.0.16 and am not seeing this issue, but then, when I create a camera the parms are already in place. Can you post a file? -
Magnus had a good idea with using dot products. The dot product will give you a scalar to use as a multiplier for your wind. If you take the positive value of the dot product, then this will only increase the spread in the direction of the wind, where the spread angle and the wind angle are in a similar direction. Hopefully that makes sense.
-
The only issue I had with installing was the MODELER_PATH needed to point to the modeler subdirectory. For example: MODELER_PATH = "C:/Users/<USER>/Documents/Modeler1.0.4/modeler" To check if it's being picked up in Houdini, you should be able to see a shelf called Modeler in the drop-down list, and a Modeler tab menu.
