Found 4508 posts.
Search results Show results as topic list.
Solaris and Karma » editableStage() does not work in Expression context
- jsmack
- 7803 posts
- Online
Houdini for Realtime » Startup warning: Viewer state type conflict
- jsmack
- 7803 posts
- Online
I think you have two installs of labs. The one in your documents folder is probably the older one, since the launcher now installs labs in the launcher folder.
Technical Discussion » polyextrude on grid not working as expected
- jsmack
- 7803 posts
- Online
grantstaley
hi All,
Thanks for the replies, really appreciate it. As learning any new software...big frustrations with simple answers.
I ended up just starting from scratch so that all the default settings were reset. That seems to have fixed whatever the issue is. I will have to remember the "ctl-minus" if I see it again. I am sure when I was trying to add a node, I forgot to hit tab first, which I am sure caused me to hit some kind of hotkey for something.
All resolved now. I was trying to cancel this post but It had to go through admin since my first time.
Thanks again for the help.
The draw mode of each object is also in a menu on that object's parameters which helps if you forget the hotkey.
Edited by jsmack - July 18, 2022 12:26:16
Houdini Lounge » is Karma the replacement for Mantra now for rendering?
- jsmack
- 7803 posts
- Online
tamte
It depends on your needs and workflows
Karma is still not 1-1 replacement for Mantra
It's in addition to Mantra. Mantra is still the only way to render objects directly.
Technical Discussion » polyextrude on grid not working as expected
- jsmack
- 7803 posts
- Online
Enivob
That looks like the result of a subdivide node. Do you have one in your network? If you do, change the algorithm to OpenSubdiv Bilinear.
I don't think so, it looks like viewport subdivision. You can tell by the wireframe not matching the surface.
Hit the ctrl-minus key combination to disable smoothing on the current object.
Technical Discussion » How to Convert Points "Directly" to VDBs?
- jsmack
- 7803 posts
- Online
tamte
- create empty VDB volume with voxel size and alignment for one of your points and then use Volume Rasterize (or alo try Volume Rasterize Points/Particles)
- you could also try Volume Rasterize Attributes, but then you don't have a control over the voxel alignment so may not be a useful, however its a wrapper around Volume Rasterize Particles so you can break in and adjust if needed
Volume rasterize particles has a point filter mode, which if the points are perfectly aligned to voxel centers should only sample the particle as the center of the voxel.
Houdini Lounge » clEnqueueNDRangeKernel Vellum bug ?
- jsmack
- 7803 posts
- Online
naseful
I don't think it's driver fault
I have been that error in 18.5.
I just use 17.5 version, and didn't get any error.
17.5 didn't use native command queuing so it was impossible to have that error.
Houdini Lounge » Any houdini 19.5 rumors?
- jsmack
- 7803 posts
- Online
osong
RandomWalk SSS, crack-free displacement seems to be MatX exclusive
These have been in the mantra principled shaders for karma cpu for a while. Random walk has anyway. I'm pretty sure mantra displacement was always crack-free.
Technical Discussion » polybevel problem
- jsmack
- 7803 posts
- Online
The warning on the polybevel might be a clue. One of those edges looks non-oriented, the faces sharing the edge have opposite winding order. Meshes should always be oriented when modelling.
Technical Discussion » Billowy smoke - Houdini 19 vs Houdini 18
- jsmack
- 7803 posts
- Online
archz2
I asked a friend of mine who is using Houdini 18.5. He doesn't have to do control click. His smoke system automatically gets attached to the sphere after just simply selecting it and pressing the billowy smoke icon in the shelf.
use 18.5, that workflow is gone.
the old pyro tools were hidden in favor of the new tools, but new ones require you to build the sourcing setup yourself.
You can get the old tool back by right clicking on the pyro shelf, and selecting edit shelf tab...
Then highlight 'billowy smoke' in the tools list and accept. this will add the old billowy smoke tool to the shelf. Then click away.
Technical Discussion » Unpacked/expanded OTL/HDA performance hit?
- jsmack
- 7803 posts
- Online
olliRJL
Is anyone doing this?
My initial intention was to "pack" the otls at release time using the hotl tool but in my testing I pretty much immediately encountered a couple of otls that "unpacked" fine but errored out when "packing" back. And there is no useful error information from the hotl tool. The weird thing is that those same otls unpack and pack just fine when using the asset manager gui inside Houdini.
I have a mix of packed and unpacked otls in the pipeline and haven't seen if it causes a performance impact. The number of otls is more of a factor than if they are packed or not. It's better to not install tools that you aren't using.
Solaris and Karma » Karma Slow when Rendering to Disk or Mplay
- jsmack
- 7803 posts
- Online
caden
I think that what is happening is that without having "render all frames with a single process" checked Karma automatically defaults to a CPU render when hitting render to disk.
No, but it will open each usd file as a separate frame, render the image and then exit when done. This start and spin down process probably takes much longer than rendering a frame. That's why render all frames in a single process is much faster. There is also the usd export time on the Houdini side. By default, each frame is saved as a single usd file and rendered before moving on to the next frame. This allows sloppy scene authoring and animating properties that cannot be animated in USD. This is why it is the default. If you notice when enabling XPU, the Optix device will say 'init' for quite some time while the image first starts rendering in the viewport. This is how long it takes for the nvidia rendering library to load and for the assets to be transferred to the GPU. For me it takes about 30 seconds. This could be a large part of the time between frames when rendering frame by frame instead of all frames at once.
Try rendering something that takes more than a few seconds to render, then the start up time won't matter as much.
Technical Discussion » Detail Attribute Returning 0
- jsmack
- 7803 posts
- Online
geordiemartinez
I see that I cannot use the detail function in a field that expects an integer otherwise it sets a key.
At least this is true for frame range fields.
So I added an null (exactly like the example file above) and that null had a string attribute that I put the detail function.
then I copied a reference to this field and pasted it into the frame range field and it now works.
What's wrong with setting a key? no ` required. I use keyframes on string parameters too.
Houdini Lounge » Easiest ACES-CG to SRGB Jpeg?
- jsmack
- 7803 posts
- Online
TangheStudent
If you right-click your image in view or composite view you can select save as and there you can select the LUT.
when i the LUT, however, the colours are still weird and incorrect
You might have automatic gamma correction enabled. Make sure "convert to image format's colorspace" is disabled and gamma is 1 when using an ODT lut.
Relying on baked luts to apply an ocio transform isn't always viable. Any custom looks would require baking new luts. They may also lose some precision.
Houdini now ships with oiiotool, which is renamed 'hoiiotool'
use the command line script to apply an ocio display/view transform when converting from scene linear images to display referred images:
hoiiotool -i input.exr --iscolorspace "scene_linear" --ociodisplay "ACES" "sRGB" -o output.jpg
replace input.exr and output.jpg with the actual file names and replace "scene_linear" with the actual input color space if not scene_linear. Use the display and view defined in your config. For example an OCIO 2.1 config might have a display called "Display - sRGB" and view "Output - SDR Video - ACES 1.0"
Edited by jsmack - July 13, 2022 20:32:34
Houdini Indie and Apprentice » Disable automatic wiring connection when copy-paste nodes
- jsmack
- 7803 posts
- Online
If you paste them into a network with node names that don't match the source network, then they won't connect. There's no way to selectively paste the nodes without pasting the connections.
Technical Discussion » Basic detail function not working... how?! SOLVED
- jsmack
- 7803 posts
- Online
olivierth
bottom one (named "fetch_float"):
f@testValue = detail("../source/", "value", 0)
...but the bottom wrangle gets the value 0 instead of 8. isn't this suposed to work?
attribute functions in VEX can't reference other nodes, only read from files. The first argument is a path to a file on disk. Houdini can read from nodes as if they are virtual files by prefixing the node's path with op: as @gorrod suggests.
Houdini Indie and Apprentice » Viewport not displaying the correct result.
- jsmack
- 7803 posts
- Online
Enivob
I noticed immediately when I started using Houdini in 12.5. I reported it, and SideFX support mentioned the product is transitioning to new OpenGL shaders. The problem still persists today. Stale data gets trapped in the display buffer and the viewport reset, or Houdini restart is the only fix. It's not just Mac, I experience it on Windows and Ubuntu.
You can use the Report Bug/RFE menu option under the Support menu.
It's behavioral too though. If you avoid the actions most likely to result in stale viewport data, you'll never see it. One tip, never dive into a sop solver without pinning the viewer above it.
Technical Discussion » COP file reader problem
- jsmack
- 7803 posts
- Online
Tom Mangold
The only other node I came across is the Labs DDS node which reads files. Wonder how they created it. Could some python code on a null work as a read node?
it's not possible to read images into cops using python.
You could try reading the images as textures via vex.
Technical Discussion » bad parameter error?
- jsmack
- 7803 posts
- Online
What are 'min' and 'max' referring to? The transform sop doesn't have any such parameters.
Technical Discussion » COP file reader problem
- jsmack
- 7803 posts
- Online
I'm confused, there aren't any SOPs in COPs, by definition. Do you mean the file COP? I've had problems with getting the file COP to read an animated non-sequence frame sets. It seems to be hard-coded to work with frame sequences only. I don't think the sequence expression can be animated how you describe. You need to use a different file node for each sequence.
-
- Quick Links