I am simulating some fluid inside a jar/can. The can moves around and the fluid remains inside. I have a fairly high voxel count, 65million. But when it comes to surfacing the fluid, it looks really fake. There are too many long strands and not enough full surface.
How can I get better surfacing of fluid in this scenario?
Found 1698 posts.
Search results Show results as topic list.
Technical Discussion » Less Spaghetti Like Fluid Surfacing?
-
- Enivob
- 1699 posts
- Offline
Houdini Indie and Apprentice » Renderman for houdini apprentice
-
- Enivob
- 1699 posts
- Offline
You can install it, but 3rd party rendering is not supported by Apprentice. You need an Indie license or better.
Technical Discussion » releasing cloth from animated geo
-
- Enivob
- 1699 posts
- Offline
I think you just have a typo in an attribute name.
You have.
You need.
You have.
f@targetstrenght=f@attach;
You need.
f@targetstrength=f@attach;
Edited by Enivob - July 11, 2018 14:45:54
Technical Discussion » H16: Houdini displays geometry even with none visualized
-
- Enivob
- 1699 posts
- Offline
Yes, the Houdini viewport does display things wrong quite often. I have encountered a similar problem where I have all my Display flags turned off and objects are still displayed in the viewport. My bad viewport experience typically involves instancing.
Houdini Indie and Apprentice » Exporting vdb sequence
-
- Enivob
- 1699 posts
- Offline
There is a global $Fx token you can place inside the filename field of the FileCache or File node, where x is the zero padding amount for the frame number.
Try this…
Should produce a filename for each frame named like my_filename_0001.vdb, my_filename_0002.vdb etc…
Put the File node in Write mode and simply play the timeline one time. Or click the Save To Disk button with the required frame range set.
Try this…
my_filename_$F4.vdb
Put the File node in Write mode and simply play the timeline one time. Or click the Save To Disk button with the required frame range set.
Edited by Enivob - June 26, 2018 09:29:09
Houdini Indie and Apprentice » Color based on position/varying color based on velocity and pos
-
- Enivob
- 1699 posts
- Offline
Technical Discussion » activate time shift at any frame
-
- Enivob
- 1699 posts
- Offline
I think I would just sim them all out at normal speed, as a .bgeo.sc sequence. Then use a File node, followed by a TimeWarp to control the slow down.
You should be able to animate the time scale on the solver. Have you tried that?
You should be able to animate the time scale on the solver. Have you tried that?
Edited by Enivob - June 25, 2018 12:17:54
Technical Discussion » Viewport Instancing Is Broken In Houdini 16.5.495
-
- Enivob
- 1699 posts
- Offline
Yep, SESI reported the same thing. However, when I substitute actual mesh based corridor geometry, I get intermittent drop out of certain pieces. If I try to instance a deforming FBX I often get outright crashes.
It is logged as a bug now, so hopefully, some improvements are on the way.
It is logged as a bug now, so hopefully, some improvements are on the way.
Technical Discussion » Viewport Instancing Is Broken In Houdini 16.5.495
-
- Enivob
- 1699 posts
- Offline
I have a set of points, which are generated by a python script. Each point has the s@instance attribute set to either /obj/geo_BOX or /obj/geo_SPHERE. The points are object merged into an instance node.
When I revise the point set in the python script, only the BOX geometry is correctly revised. For some reason the SPHERE objects remain “stuck” at an old location. If you toggle the Instance node display flag on and off, the spheres finally update to the correct location.
I have tested on a Windows 7 system using a nVdia 660gtx and on an Ubuntu 18.04 using a nVdia 1070gtx. I get the same broken result on each machine.
Can someone test my scene on their system?
I feel like this is a bug but it would be nice to know if anyone else experiences the same issue.
To test, open the HIP file and move the sliders.
When I revise the point set in the python script, only the BOX geometry is correctly revised. For some reason the SPHERE objects remain “stuck” at an old location. If you toggle the Instance node display flag on and off, the spheres finally update to the correct location.
I have tested on a Windows 7 system using a nVdia 660gtx and on an Ubuntu 18.04 using a nVdia 1070gtx. I get the same broken result on each machine.
Can someone test my scene on their system?
I feel like this is a bug but it would be nice to know if anyone else experiences the same issue.
To test, open the HIP file and move the sliders.
Edited by Enivob - June 19, 2018 10:45:27
Technical Discussion » 2nd HD not showing in Houdini installed in Linux
-
- Enivob
- 1699 posts
- Offline
Yeah, I run into the same problem with USB drives I plug in.
What you need to do is navigate to your root_drive/media/username and any mounted drives will be listed there.
Once you are there, you can select a folder and click the + button to add it to your sidebar.
What you need to do is navigate to your root_drive/media/username and any mounted drives will be listed there.
Once you are there, you can select a folder and click the + button to add it to your sidebar.
Edited by Enivob - June 14, 2018 17:12:52
Technical Discussion » replicating C4D cloner Follow Position force
Houdini Indie and Apprentice » gravitational singularity
-
- Enivob
- 1699 posts
- Offline
Technical Discussion » Houdini on Ubuntu
-
- Enivob
- 1699 posts
- Offline
My issue was a 3rd party render system, Redshift was not compatible with the .496 release. Once I upgraded my Redshift to the latest version, which is matched to the H16.5.496 API, and altered my houdini.env to point to the new plug-in Houdini launched just fine.
This API mis-match could be an issue for Arnold users as well.
This API mis-match could be an issue for Arnold users as well.
Technical Discussion » Houdini on Ubuntu
-
- Enivob
- 1699 posts
- Offline
I just installed Houdini 16.5.496 on Ubuntu 18.04 and I get a crash on launch.
I can still launch and use H16.5.378 just fine.
Any tips on how to get past a “HOM_OperationFailed” error?
I can still launch and use H16.5.378 just fine.
Any tips on how to get past a “HOM_OperationFailed” error?
Edited by Enivob - June 12, 2018 12:27:57
Technical Discussion » Poly Subdivide but Leave UV's Alone?
-
- Enivob
- 1699 posts
- Offline
You could try an attribute copy or attribute transfer from the original source. Place it after your subdivide node.
Edited by Enivob - June 12, 2018 11:16:03
Technical Discussion » Loading certain assets, then instance them
-
- Enivob
- 1699 posts
- Offline
I noticed this same technique was not working consistently using H16.5.378.
I think it is just a bug in Houdini. Instancing and the viewport is certainly flaky.
I am waiting for Redshift to be compatible with the latest H16.5.496 release then I'll test again.
One thing to review, which has got me a few times, is the Display/Render flags inside the Instance node. Make sure you have the Pink color on the .rs proxy and the Blue color on the swap file extension.
I think it is just a bug in Houdini. Instancing and the viewport is certainly flaky.
I am waiting for Redshift to be compatible with the latest H16.5.496 release then I'll test again.
One thing to review, which has got me a few times, is the Display/Render flags inside the Instance node. Make sure you have the Pink color on the .rs proxy and the Blue color on the swap file extension.
Technical Discussion » Need to select Groups for applying materials
-
- Enivob
- 1699 posts
- Offline
Drop down a Material node, connect it in and any groups that already exist on your geometry should be shown in the drop down list. Select a group from the list then choose the material for that group. You can add multiple materials on a single Material node so you only need one.
Technical Discussion » Can not get rid of the black plane comes with the ground plane or static object
-
- Enivob
- 1699 posts
- Offline
Technical Discussion » Unable to resolve crashes in Houdini crahes with in 10-30 seconds
-
- Enivob
- 1699 posts
- Offline
It is probably just your computer hardware.
It looks like that laptop contains two video cards, the Intel CPU internal (which does not meet Houdini minimum requirements to run) and the nVidia card which does meet Houdini specs to run.
So there may be a conflict between the two cards, or Houdini is detecting the Intel and trying to run on that one instead of the nVidia.
There is an environment variable you can specify in the houdini.env to force Houdini to use a specific GPU. You might have to look that up and try installing that setting. Ask support about that.
Another thing you might try is to boot into the laptop BIOS and see if there is some setting where you can just disable the Intel graphics all together. This may force hardware re-detection once you jump back into your OS, however.
It looks like that laptop contains two video cards, the Intel CPU internal (which does not meet Houdini minimum requirements to run) and the nVidia card which does meet Houdini specs to run.
So there may be a conflict between the two cards, or Houdini is detecting the Intel and trying to run on that one instead of the nVidia.
There is an environment variable you can specify in the houdini.env to force Houdini to use a specific GPU. You might have to look that up and try installing that setting. Ask support about that.
Another thing you might try is to boot into the laptop BIOS and see if there is some setting where you can just disable the Intel graphics all together. This may force hardware re-detection once you jump back into your OS, however.
Technical Discussion » Can not get rid of the black plane comes with the ground plane or static object
-
- Enivob
- 1699 posts
- Offline
More than likely you are including the ground plane when you fetch the result from your AutoDopNetwork contained inside geo1. You can filter what you import using ^groundplane1 to exclude the ground plane from being fetched back into your SOP network. Also try turning off the Proxy display of the groundplane itself, inside the DOP network.
-
- Quick Links