The edit tool was massively changed since 15, so a tutorial from that version will be almost useless now.
I don't think slide on surface uses a handle, so there's nothing to show.
Found 4491 posts.
Search results Show results as topic list.
Technical Discussion » Handle disappears when I click on "slide on surface" .
- jsmack
- 7759 posts
- Offline
Technical Discussion » Why does not work rampparameter in Attribvop?
- jsmack
- 7759 posts
- Offline
The ramp is all black.
Right click the ramp and select revert to defaults to use the ramp defaults visible on the ramp vop.
Right click the ramp and select revert to defaults to use the ramp defaults visible on the ramp vop.
Technical Discussion » Vertex Wrangle ad-hoc group doesn't work?
- jsmack
- 7759 posts
- Offline
Group type "guess from group" only works for explicit groups, or it assumes a point group for ad-hoc groups on wrangles.
Explicitly select 'vertex group' and it should work.
Explicitly select 'vertex group' and it should work.
Technical Discussion » Toggle null visibility in viewport (script?)
- jsmack
- 7759 posts
- Offline
Jonathan de Blok
Here is a function that will toggle all nulls on/off even in nested subnets etc.
Note that this script modifies the scene, and will fill up the undoes.
Modifying scene viewer object visibility filter with a script would leave the scene untouched.
Unfortunately, I don't see any methods in the hou module for scripting the display options on the right sidebar. The menu will have to do for now.
I suggest submitting an RFE to Sidefx for this feature, as all aspects of the interface should be scriptable.
Houdini Indie and Apprentice » Exporting to GLTF format
- jsmack
- 7759 posts
- Offline
LucioFreitas
Is there any way to export an animation in houdini as gltf (GLB file)?
I don't think so
Solaris and Karma » How to stop the renderer?
- jsmack
- 7759 posts
- Offline
kskovbo
I am using Arnold for Houdini 18.5.408. I am looking for a simple way to stop the renderer. I do not want it to continuously update all the time. I only see "Restart" and "Resume" render. I need a "Stop" :-)
There is none. Switching to GL is supposed to suspend the previous delegate. Perhaps this is a bug with the Arnold delegate.
kskovbo
Is there a renderview a bit like Katanas "Monitor" or Maya's "Render View" where I can start/stop the renderer myself?
No, the render is the scene viewer in the Hydra viewport. It can be paused, restarted, or swapped out for another, but not stopped.
Technical Discussion » point deform on tearing mesh not working
- jsmack
- 7759 posts
- Offline
anbt
If I understand well what you say, I should do the same TetPartition on my highres geometry as I am doing on my simmed geometry?
No, I'm not sure that will help. I'm not familiar with using tetpartition. The main thing that is needed is for the capture to avoid captured points crossing over seams. If possible, physically separate the geometry on opposite sides of the seams. The high and low parts need the same translations applied. For example if moving A_hi left 2 units and B_hi right 2 units, move A_lo left 2 and B_lo right 2 as well. Whatever it takes to prevent capture crossover.
Solaris and Karma » Permanent defaults on plugin parameters
- jsmack
- 7759 posts
- Offline
The delegate-specific render settings on the rendersettings node are not part of the node definition, so won't be saved as part of permanent defaults.
The settings tab for each render delegate is added on node creation. Changing the defaults would require modifying the dialog script file distributed with the renderer. Perhaps placing another DS file somewhere higher in the path would take precedence, but that's not something I've tried.
The closest thing to saving defaults for a node with custom spare parameters would be to create a shelf tool that creates the node. Drag any node to a shelf to add the node. Then it can be recreated as is by clicking that shelf tool or using it from the tab menu, (may require editing the tool to add it to the proper context.)
The settings tab for each render delegate is added on node creation. Changing the defaults would require modifying the dialog script file distributed with the renderer. Perhaps placing another DS file somewhere higher in the path would take precedence, but that's not something I've tried.
The closest thing to saving defaults for a node with custom spare parameters would be to create a shelf tool that creates the node. Drag any node to a shelf to add the node. Then it can be recreated as is by clicking that shelf tool or using it from the tab menu, (may require editing the tool to add it to the proper context.)
Technical Discussion » point deform on tearing mesh not working
- jsmack
- 7759 posts
- Offline
anbt
Any clue as to what I am doing wrong?
You're not doing anything wrong. This behavior is to be expected with proximity capture based tools such as point deform.
A possible work around is to separate the pieces for the capture step to prevent erroneous capture across boundaries.
Technical Discussion » "texture" function not support do not pre multiply alpha
- jsmack
- 7759 posts
- Offline
I've not seen this before. Each channel is read independently. I use textures with zero data in the alpha without issues.
Solaris and Karma » Motion blur from camera animation
- jsmack
- 7759 posts
- Offline
ddhoudinitesting
For your Hydra Viewport, you'll probably need to put down a Cache LOP to cache the frames either side of the current frame.
You could also save the camera out first, and read it back with sublayer. Cameras come from other departments most of the time anyway.
Technical Discussion » Houdini AR compatibility
- jsmack
- 7759 posts
- Offline
Although Houdini could theoretically be used, CAD programs are probably your best approach for designing an manufacturing components compatible with the AR weapons platform. Data for upper and lower receivers are probably more available in CAD formats anyway.
Solaris and Karma » Control over how Xforms are written in USD
- jsmack
- 7759 posts
- Offline
mtuckerIs that something new? I've not heard of it.
UsdGeomXformCommonAPI (rather than our own split T/R/S schema…)
I was referring to using individual usd xformops created in the order selected by the transform order menu, such as rotateXYZ, translate etc.
Houdini Indie and Apprentice » `Grave Accent`
- jsmack
- 7759 posts
- Offline
The backticks from from unix shell scripts. The mean ‘evaluate me first’. They are not needed in an expression keyframe, as they are always evaluated at the current time.
Entering non-numerics into a float or integer parameter will create a keyframe with the text as the expression for you, which is why backticks aren't needed in that case.
In string parameters, since text is always entered, there's no reason to automatically add a keyframe. This is why backticks are needed if a keyframe hasn't been manually added. The backticks cause the text inside to be evaluated instead of used as a literal string.
A grave accent sounds like something a Bond villain might possess.
Entering non-numerics into a float or integer parameter will create a keyframe with the text as the expression for you, which is why backticks aren't needed in that case.
In string parameters, since text is always entered, there's no reason to automatically add a keyframe. This is why backticks are needed if a keyframe hasn't been manually added. The backticks cause the text inside to be evaluated instead of used as a literal string.
A grave accent sounds like something a Bond villain might possess.
Solaris and Karma » Render All Frames With a Single Process - Problem
- jsmack
- 7759 posts
- Offline
Can you create multiple render products, one for each camera to render with? I think some renderers will render a view for each render product.
Another option would be to render the lightfields in a single pass using a lens shader to create a photomosaic. Karma is the only renderer I know of that supports lens shaders in solaris at the moment though.
Another option would be to render the lightfields in a single pass using a lens shader to create a photomosaic. Karma is the only renderer I know of that supports lens shaders in solaris at the moment though.
Solaris and Karma » Control over how Xforms are written in USD
- jsmack
- 7759 posts
- Offline
mtucker
Output processors don't let you do anything like this because really this is what nodes are for… I would suggest using a python LOP, and wrap it into an HDA along with the USD ROP.
Is there any reason the houdini nodes that author xforms from TRS parameters don't optionally write them as individual xform ops, (other than, I guess lack of demand or performance?)
Writing Euler rotations as matrices is somewhat lossy, as you might want to directly author rotations of greater than 180 degrees per frame for simplicity.
With USD going to all 64bit xforms of type matrix, sticking with sparse individual ops would produce smaller files as well, since only translate or transform matrix are always 64 bit in the new USD spec.
Solaris and Karma » Demystifying Light Transforms in the Viewer
- jsmack
- 7759 posts
- Offline
Tim Crowson
So is there a predictable way to edit the transforms on a light LOP after the fact, in the viewport?
does clicking on the lop defining the light work? That usually puts me in a state ready to move it.
Technical Discussion » Fuzzy flames problem
- jsmack
- 7759 posts
- Offline
hochenauer
Thank you so much for putting the time into answering:
i was ramping different parameters, but i hit a dead end.
This looks so much better and also explains, why simply more resolution won´t give a better result.
As for using Aces with pyro/houdini:
I´m also a color grader, so i know Aces, but could you point me to the right direction how to implement it.
thank you, you just saved my weekend
Download the latest configs from your github repo of choice, or build it your self from source.
https://github.com/colour-science/OpenColorIO-Configs/releases/tag/v1.2 [github.com]
Then export the path to the config as $OCIO in your environment. (how depends on your OS, but if only needed in Houdini, then it can be set in the houdini.env)
Houdini Indie and Apprentice » @Time in promoted variables in Attribute VOP
- jsmack
- 7759 posts
- Offline
RJM
these variables must be a VEX wrapper for HScript expressions.
These are convenience variables for use in wrangles/attrib vops, but again they're irrelevant since the issue was with a parameter expression which is either python or hscript. VEX is for what's inside the attribute VOP, or the snippet text of a wrangle. A parameter going into an attribute vop has its value determined outside of the VEX context.
With an attribute VOP, these globals are available by naming the parameter with the corresponding name, e.g. “Time”, “Frame”, “TimeInc” and binding the appropriate type. Some of these are already done for you on the geometry vop globals node. The value is ignored and should be left blank/default.
Houdini Indie and Apprentice » @Time in promoted variables in Attribute VOP
- jsmack
- 7759 posts
- Offline
RJMyes
is there a python equivalent?
RJMYes, but it's not used here since were talking about a parameter expression.
i thought VEX was its own language.
RJM
*edit*
still a little confused.
using @Time with hscript set as the language works and when switching to python the parameter turns purple and still works.
so i don't get why it wouldn't work when using @Time in python and just turn the parameter purple.
Changing the language of the node affects future channels, not existing channels. The parameter turns purple when changing the node language to indicate that the parameter's language is different from the node's.
-
- Quick Links