PointsFromVolume will do it.
Here's Rohan's Vellum intro video that covers approximately what you're asking for.
https://www.youtube.com/watch?time_continue=1381&v=frTdG_FJFlQ [www.youtube.com]
Found 15 posts.
Search results Show results as topic list.
Houdini Indie and Apprentice » Instances into grains
- Zoot
- 15 posts
- Offline
Houdini Indie and Apprentice » [Solved] OpenCL setup for 17?
- Zoot
- 15 posts
- Offline
Ok, I managed to get it working (yay).
The problem was that there's a configuration for your choice of OpenCL device squirreled away at Edit->Preferences->Miscellaneous, and it was defaulting to the first OpenCL provider which was the Intel 630 Integrated graphics.
Combined with this, all the environment variables support suggested to override the behavior were apparently insufficient to override that Misc setting, and setting the Misc selection works when the env vars were not. So the complete solution was:
1) Set Miscellaneous preferences OpenCL to GPU and the appropriate Nvidia device.
2) Remove any and all extra OCL related environment variables from Houdini.env EXCEPT for:
HOUDINI_USE_HFS_OCL=0
which is still needed at least on my system to get it to load correctly.
Now OpenCL initializes successfully and vellum is successfully heating up the GPU. Woot.
The problem was that there's a configuration for your choice of OpenCL device squirreled away at Edit->Preferences->Miscellaneous, and it was defaulting to the first OpenCL provider which was the Intel 630 Integrated graphics.
Combined with this, all the environment variables support suggested to override the behavior were apparently insufficient to override that Misc setting, and setting the Misc selection works when the env vars were not. So the complete solution was:
1) Set Miscellaneous preferences OpenCL to GPU and the appropriate Nvidia device.
2) Remove any and all extra OCL related environment variables from Houdini.env EXCEPT for:
HOUDINI_USE_HFS_OCL=0
which is still needed at least on my system to get it to load correctly.
Now OpenCL initializes successfully and vellum is successfully heating up the GPU. Woot.
Houdini Indie and Apprentice » [Solved] OpenCL setup for 17?
- Zoot
- 15 posts
- Offline
I've been working with support and trying different things with no luck so far.
I'm suspicious that it's related to the fact that this system has both Intel and Nvidia OpenCL, and perhaps Houdini has an issue such as that described in:
https://stackoverflow.com/questions/19140989/how-to-remove-cl-invalid-platform-error-in-opencl-code [stackoverflow.com]
Anyone running H17 successfully on a hybrid system with both Intel and Nvidia graphics?
I get -32 (invalid platform) or -33 (invalid device) generally in the console when it tries to initialize OpenCL. I can force it back to CPU only and that is successful using:
HOUDINI_OCL_DEVICETYPE=CPU
HOUDINI_USE_HFS_OCL=0
But every other permutation fails.
I'm suspicious that it's related to the fact that this system has both Intel and Nvidia OpenCL, and perhaps Houdini has an issue such as that described in:
https://stackoverflow.com/questions/19140989/how-to-remove-cl-invalid-platform-error-in-opencl-code [stackoverflow.com]
Anyone running H17 successfully on a hybrid system with both Intel and Nvidia graphics?
I get -32 (invalid platform) or -33 (invalid device) generally in the console when it tries to initialize OpenCL. I can force it back to CPU only and that is successful using:
HOUDINI_OCL_DEVICETYPE=CPU
HOUDINI_USE_HFS_OCL=0
But every other permutation fails.
Houdini Indie and Apprentice » [Solved] OpenCL setup for 17?
- Zoot
- 15 posts
- Offline
Still no luck with OpenCL. I upgraded from 39x to 416 Nvidia drivers for my 1060 without any effect.
I have various ENV variables in Windows 10 related to the CUDA toolkits being used for Tensorflow and Pytorch, and I suspect perhaps that or the CUDA version(s) installed are preventing H from seeing what it needs.
PATH=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0\libnvvp;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1\libnvvp;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\libnvvp;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\cuda\bin;"
No Configured OpenCL Device
Environment:
CUDA_PATH C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0
CUDA_PATH_V8_0 C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0
CUDA_PATH_V9_0 C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0
CUDA_PATH_V9_1 C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1
NVCUDASAMPLES8_0_ROOT C:\ProgramData\NVIDIA Corporation\CUDA Samples\v8.0
NVCUDASAMPLES9_0_ROOT C:\ProgramData\NVIDIA Corporation\CUDA Samples\v9.0
NVCUDASAMPLES9_1_ROOT C:\ProgramData\NVIDIA Corporation\CUDA Samples\v9.1
NVCUDASAMPLES_ROOT C:\ProgramData\NVIDIA Corporation\CUDA Samples\v9.0
NVTOOLSEXT_PATH C:\Program Files\NVIDIA Corporation\NvToolsExt\
I have various ENV variables in Windows 10 related to the CUDA toolkits being used for Tensorflow and Pytorch, and I suspect perhaps that or the CUDA version(s) installed are preventing H from seeing what it needs.
PATH=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0\libnvvp;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1\libnvvp;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\libnvvp;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\cuda\bin;"
No Configured OpenCL Device
Environment:
CUDA_PATH C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0
CUDA_PATH_V8_0 C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0
CUDA_PATH_V9_0 C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.0
CUDA_PATH_V9_1 C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1
NVCUDASAMPLES8_0_ROOT C:\ProgramData\NVIDIA Corporation\CUDA Samples\v8.0
NVCUDASAMPLES9_0_ROOT C:\ProgramData\NVIDIA Corporation\CUDA Samples\v9.0
NVCUDASAMPLES9_1_ROOT C:\ProgramData\NVIDIA Corporation\CUDA Samples\v9.1
NVCUDASAMPLES_ROOT C:\ProgramData\NVIDIA Corporation\CUDA Samples\v9.0
NVTOOLSEXT_PATH C:\Program Files\NVIDIA Corporation\NvToolsExt\
Houdini Indie and Apprentice » Houdini 17
- Zoot
- 15 posts
- Offline
It ran fine in Apprentice mode for me on Windows while I was waiting for the license server to get around to delivering my Indie licenses.
Houdini Indie and Apprentice » [Solved] OpenCL setup for 17?
- Zoot
- 15 posts
- Offline
I have recent Nvidia drivers (with CUDA 9.2) installed and working for other applications.
Is there something else I need to install to get OpenCL working for Houdini 17? I thought it all came with the base driver and/or the CUDA stuff.
Or are there ENV vars I have to manually set up to explain it to H?
I looked through the documentation without any luck.
Help->About Houdini pops up a console window saying:
Unable to load HFS OpenCL platform.
OpenCL Exception: €EË{ (-1)
And the About, Show Details says “No OpenCL Provider” in it.
Is there something else I need to install to get OpenCL working for Houdini 17? I thought it all came with the base driver and/or the CUDA stuff.
Or are there ENV vars I have to manually set up to explain it to H?
I looked through the documentation without any luck.
Help->About Houdini pops up a console window saying:
Unable to load HFS OpenCL platform.
OpenCL Exception: €EË{ (-1)
And the About, Show Details says “No OpenCL Provider” in it.
Edited by Zoot - 2018年10月15日 22:42:40
Houdini Lounge » Siggraph 2018
- Zoot
- 15 posts
- Offline
gfxfx1pm Thursday on the SideFX Siggraph schedule linked in the third post above.
can some the links to it “H17 Sneak Peek” session on PolyDraw 1.0, as well as the numerous TBD sessions?”
typing “PolyDraw” in google does not help me at all
So maybe we won't get a full H17 peek, but there's at least this which sounds like something new and interesting in the modeling world.
Houdini Lounge » Siggraph 2018
- Zoot
- 15 posts
- Offline
You perhaps missed the “H17 Sneak Peek” session on PolyDraw 1.0, as well as the numerous TBD sessions?
Houdini Indie and Apprentice » Will disk drive replacement affect Indie license?
- Zoot
- 15 posts
- Offline
Thanks to $150 1TB SSDs from Prime Day, I'm going to shortly be doing a drive upgrade on my Win 10 laptop that has my first Indie license on it. Is this likely to be painless, or can I expect to have to jump through licensing hoops afterwards? I'll be doing a drive clone rather than a clean install.
Tnx!
Tnx!
Houdini Learning Materials » HOUDINI FOUNDATIONS | GDC 2018 EDITION
- Zoot
- 15 posts
- Offline
This is like the best thing ever!!
It seems to render incorrectly in some cases in Chrome on Windows 10, but on my Chromebook it looks OK so I don't know.
But I have been going through this and it's WONDERFUL! Thanks SideFx!
It seems to render incorrectly in some cases in Chrome on Windows 10, but on my Chromebook it looks OK so I don't know.
But I have been going through this and it's WONDERFUL! Thanks SideFx!
Technical Discussion » H16 performance broken for me (fixed, was video driver)
- Zoot
- 15 posts
- Offline
twodIt was a 376.something but I don't seem to have the install files for it any more so I don't know the exact version, sorry.
Do you recall the Nvidia driver you were using before?
Technical Discussion » H16 performance broken for me (fixed, was video driver)
- Zoot
- 15 posts
- Offline
twodGeforce 860M with driver 378.66 is now working fine.
I believe this has to do with Qt5 and Nvidia consumer drivers. You may want to try the Qt4 build.
Z.
Technical Discussion » H16 performance broken for me (fixed, was video driver)
- Zoot
- 15 posts
- Offline
Artye
Sounds like the infamous win10 GPU weekend update - if it is, you need to reinstall the GPU drivers.
Bingo. Thanks, that fixed it.
Z.
Technical Discussion » H16 performance broken for me (fixed, was video driver)
- Zoot
- 15 posts
- Offline
Switched to localLicensing, no effect.
Every Torus is 45 seconds. Actually CPU utilization runs around 17% while trying to create a Torus.
Sometimes it seems to go out to lunch even more, to the point that the status line elapsed timer stops elapsing. But this is less common. 45 second Tori are very consistent.
Z.
Every Torus is 45 seconds. Actually CPU utilization runs around 17% while trying to create a Torus.
Sometimes it seems to go out to lunch even more, to the point that the status line elapsed timer stops elapsing. But this is less common. 45 second Tori are very consistent.
Z.
Technical Discussion » H16 performance broken for me (fixed, was video driver)
- Zoot
- 15 posts
- Offline
I'm sure this is just something related to my system, possibly the fact that I have the latest Anaconda Python installed, but after installing H16 Indie today, I find that any operation that creates a node is taking between 40 seconds and four minutes to complete, during which it's showing progress messages like “Evaluating python”, “Run Hscript command”, “Updating Exports”, etc.
During this, there's no disk activity, memory usage is a mild 400MB, and even more oddly, CPU utilization is between 0 and 2%, with no network activity (or none large enough to register in Task Manager.
Gonna reboot…
Update: Reinstalling Nvidia drivers solved the problem.
During this, there's no disk activity, memory usage is a mild 400MB, and even more oddly, CPU utilization is between 0 and 2%, with no network activity (or none large enough to register in Task Manager.
Gonna reboot…
Update: Reinstalling Nvidia drivers solved the problem.
Edited by Zoot - 2017年2月21日 16:39:12
-
- Quick Links