Aizatulin
divide (avoid small angles)

Thanks
I've used remesh with only the large polygons selected. It triangulates the rest of the object.

soulcage_dpt
hi,

i have 1x houdini indie.
i wrote a little python script that can submit a houdini file to backburner with hpython2.7.exe, hrender.py and redshift as the renderer for network rendering...
for testing i installed houdini indie on 2 PCs.
but only the one PC that has the license server installed can render.

is houdini indie capable of network rendering (like mayabatch) with only one license?

Nope, not Indie. But what you can do is to get 3 free engine licenses and use them for network rendering.

No answer to that in 5 years?

SIgor420
Hi folks, me again. This time with trying out DM modeling with vanilla Houdini stuff. At this point, I am not really sure why people are saying that DM modeling sucks, or it's not possible or I should not do it in Houdini. From what I have learned in the past two weeks is that things are quite the opposite. I have found a lot of nice solutions for different modeling tasks. I have to spend a lot of time trying out things and I am quite happy with what I can do with Houdini DM. It needs a bit more functionality to really make it awesome, like for example, Proportional Beveling. Now, I can see how people might have an impression that DM sucks in H. I have watched a gazillion of tutorials and none did show DM modeling in a way I managed to model this. So it's not about that H sucks in this regard, it's more about others simply not demonstrating what's possible and how.

This is still a work in progress. I plan to push this as far as possible.

It's not that it sucks (with the additions in the past two years that is) or that it is not possible. It is just that modelling is still faster and more direct in other tools. Like XSI....
But as I said a lot has been done and I find myself using it more often for the entire workflow.
The biggest issue for me is still the lack of multi object editing. Having a model consistent of many parts, all in one tree with only tedious methods to directly select and transform a part in the viewport is slowing the flow down a lot. Being able to just grab all upper points of windows, doors and walls and adjust the y position - while having them being separate geo - is something you don't want to miss...

In the end what makes you the money is never what you can do but how fast you can do it and how many people you need.

Hans Palacios
That parameter Preserve Bubbles is set up to hide when the Method parameter is set to its default option, Average Position. When the Method is changed to Spherical, then the Preserve Bubbles parameter is made visible. The conditional for the Preserve Bubbles visibility is noted in the Hide When field of the Edit Parameter Interface screenshot.

Oh, thank you. I wish the manual was as clear as you, and I wasn't as blind as a mole

toadstorm
You can introduce divergence into the simulation, either through a point attribute on the FLIP points or by sourcing a divergence field from SOPs with a positive value. Positive values will force the volume to expand around the affected areas.

Thank you that helps a lot. Never thought of divergence in that context.

Have you tried unpacking the abc file after load before instancing or recaching?

Can someone explain why "preserve bubbles" is missing from the UI in the particlefluidsurface node in H 18.5 (563)?
It was there in 2020 still according to the screenies in this thread:
https://www.sidefx.com/forum/topic/74336/ [www.sidefx.com]

This is a screenie from yesterday:



The parameter is there in the UI editor and is not hidden.
Is it in any way conditional? The docs don't say anything. Mysteriouslier...

I am trying to fill a container from an "inflow" inside the container, making the liquid rise and overflow.
Obviously any source that is submerged will stop emitting. I could of course add a pipe and let the liquid flow in from another container but I was hoping there is another more elegant solution, like constantly emitting particles inside the fluid.

Any advice welcome.
Thanks in advance.

As much as I would like to see a CAD importer, without the accompanying tools for multi renaming, restructuring and scene analysis like "which element has which material", quickly isolating one or a group of elements, editing across multiple objects in separate hierarchies, hiding sets of faces and so on, a CAD importer would be pretty useless - at least for more complex data sets.
You can do some of that in Houdini, but when importing a dataset with hundreds or thousands of elements with part names and multi-nested hierarchies, you quickly realize that you made a mistake importing into Houdini. Digging your way through nested hierarchies without a proper scene tree is a pain in you know where. Not even to mention the time it takes to redraw a scene every time when you come back to object level.
CAD import is more than just reading a format.

I use MOI 3D for conversion. It has one of the best meshers you can get and it is fairly cheap. I also model stuff there.
For scene cleanup, shader reassignment and restructuring I still use Softimage.

stevenong
Here are examples in the Online Help for this
http://localhost:48626/examples/nodes/dop/fluidobject/BallInTank
http://localhost:48626/examples/nodes/dop/fluidobject/FluidFeedback
The key is to set the Feedback Scale parameter found under the Internal Forces tab of the Fluid Solver.

Cheers!
steven

Sorry for reviving this, but I would like to know how that would work with a flipsolver which doesn't seem to have the feedback parameter.
Any examples for that?

I am looking for this too. No answer after one year?

I figured it out. It is so obvious - and so absurd - that I subconciously ignored the possibility:

The view background sequence is loaded into the OGL Cache, which is, yes the VRAM on your graphics card.
So you have a choice: Fill up your 6-12 gig of VRAM with a third of your sequence which prevents you from rendering with Redshift while the better part of you 64 gig of RAM is empty, or…. switch back ( again ) to a software where you can load easily you view background in your ram where it belongs while happily rendering with your GPU renderer.
RFE has been logged now. I wonder if they'd noticed it once Karma went GPU….

I have the same issue. I have given up on HQueue long ago. It is a pain to set up. If you only need to render sequences or even do sims, I recommend Afanasy. It's free and has gotten a new version just recently.
It is set up and configured in minutes and you don't have to be an IT expert.
Your text to link here… [cgru.info]

jsmack
nah, it's fine

“Fine” seems to have varying definitions across the user base - probably depending much on the requirements of different fields of work or level of professionality or means of comparison.

goat
I can confirm, that after comparing H18.5 to H13 sneak peaks, that Houdini is indeed improving.

Houdini 13 Sneak Peek #1
https://vimeo.com/75805237 [vimeo.com]

On the upper end, yes. The lower ends is still lagging behind….

The first connect today took some time, yes.

goat
You should submit a bug via the Support menu above as it's always worked here on Linux.

SideFx support staff in general don't read these forums.

I will. I was hoping someone in the community might have an answer.

I have to bump this up.
I still have trouble playing a sequence of 140 frames as a camera background (loaded in the camera parameters)or as a viewport background set in the view options. Only a few frames play real time then Houdini starts reading from disk again. Houdini memory usage doesn't even increase during the playing of the timeline.

This is something I can easily do anywhere else. There must be a way to do it in Houdini, the most sophisticated DCC application today?

antc

OneBigTree
When I say cleaning up I do not even talk about cleaning up geometry. I talk about structuring the scene in a way that you can start working efficiently with the geo in the first place - quickly. I do not see any tools for that at all in Houdini.

I'm not disagreeing with you at all, but the devils in the details a bit … it'd be great if you could expand on what kinds of tasks you mean by “start working efficiently” since many of the previous posts sounded like asset prep/cleanup type workflows.

What I mean is for example grouping similar objects, restructuring hierarchies, turning copies into instances to reduce memory footprint, renaming objects from “part_297584_cd_VX-07” to “screw_iron” 1-250 with automatic numbering and so on. So you can quickly find and isolate any piece of geometry you want to work on.
Part of this is being able to see the most important properties of an object at a glance. In max, XSI, C4D and even blender you expand the tree and you can immediately see pointgroups, subsets of components, assigned materials etc. It helps you read a scene quickly before you even start working on it. A large scene does not necessary mean large scale but often one object containing a large number of parts. Being able to manage that in one centralized interface can speed up preparing a large scene significantly.