I'm on a 2016 MBP with the Radeon Pro 455 card.
In general, I find things to be quite stable. I do seem to always crash Houdini when I exit the program, but that doesn't affect my work in any way.
And for context, I'm doing mostly VEX and motion graphics stuff, as well as getting into modelling, rigging and animation. Basically sticking to the Houdini Core features and occasional particles. So I can't talk about the stability of any large-production dynamics, fluids, etc. I'm not even doing very much rendering yet.
If I want to do those things more in the future, I'll be investigating using a workstation or a cloud solution. But for now I'm very happy with the experience.
Edit: I'm also just reading up on the fact that official external GPU support is coming to Macos High Sierra. So that might help things in the future as well.
Found 5 posts.
Search results Show results as topic list.
Technical Discussion » 2017 MacBook Pro and Houdini?!?!
- chrislesage
- 5 posts
- Offline
Technical Discussion » Recreating Processing in Houdini
- chrislesage
- 5 posts
- Offline
For things where you want the state to change over time, the solver does work perfectly and you can control sub-steps too. But often, your attributes and geometry can simply evolve over time, or be driven by a single parameter, and then you can just use frames or time or a parameter to measure instead.
Here is a very simple bouncing ball “Hello World” I did using the solver sop. When it reaches a certain value it bounces and reverses direction in that axis. Dive into the solver sop to see the VEX code.
Also, man I love that bees-bombs thread!
Here is a very simple bouncing ball “Hello World” I did using the solver sop. When it reaches a certain value it bounces and reverses direction in that axis. Dive into the solver sop to see the VEX code.
Also, man I love that bees-bombs thread!
Technical Discussion » Macbook Pro, Iris Pro and external monitor
- chrislesage
- 5 posts
- Offline
Hi alexpi,
I am using a Macbook Air from 2012. It works just fine, but as I posted in another thread, I run into heat issues when I am running PointWrangles on 100x100 to 200x200 grids, after about a minute of playback. So I just have to stop playback occasionally.
I was able to get through the CGWorkshop “Vex in Houdini” and all of the example projects ran just fine on my Air. (Heat issues aside.)
Rendering is also very slow, but I'll be looking into network rendering if I get serious into Houdini.
I am quite new to Houdini, but I think to successfully use laptops, you'll want to take advantage of disk caching and clever optimizations as much as possible.
I also sculpt in 3D-Coat with millions of voxels and develop basic games in Unity3D with very little issue on the Air.
Are you planning on doing any real-time work like performances?
I am using a Macbook Air from 2012. It works just fine, but as I posted in another thread, I run into heat issues when I am running PointWrangles on 100x100 to 200x200 grids, after about a minute of playback. So I just have to stop playback occasionally.
I was able to get through the CGWorkshop “Vex in Houdini” and all of the example projects ran just fine on my Air. (Heat issues aside.)
Rendering is also very slow, but I'll be looking into network rendering if I get serious into Houdini.
I am quite new to Houdini, but I think to successfully use laptops, you'll want to take advantage of disk caching and clever optimizations as much as possible.
I also sculpt in 3D-Coat with millions of voxels and develop basic games in Unity3D with very little issue on the Air.
Are you planning on doing any real-time work like performances?
Technical Discussion » Throttling CPU usage down
- chrislesage
- 5 posts
- Offline
Thanks Mark, I'll give that a try and see what effect it has.
Thanks tinyparticle. I imagine you are right and it will still cause issues for me.
Unfortunately, I travel a lot and a laptop is all I have. I am coming from Maya where I've gotten by with scripting and rigging and my computer has more than sufficed. Now in Houdini, I am often doing light work as well, but I've been going through the CGWorkshop “Vex in Houdini” and some of the pointWrangles and simulations are driving my computer crazy. I'm concerned about heat and damage more than noise. But Houdini is just too fun. I'll have to take frequent breaks or look into cooling pads.
Thanks again,
Chris
Thanks tinyparticle. I imagine you are right and it will still cause issues for me.
Unfortunately, I travel a lot and a laptop is all I have. I am coming from Maya where I've gotten by with scripting and rigging and my computer has more than sufficed. Now in Houdini, I am often doing light work as well, but I've been going through the CGWorkshop “Vex in Houdini” and some of the pointWrangles and simulations are driving my computer crazy. I'm concerned about heat and damage more than noise. But Houdini is just too fun. I'll have to take frequent breaks or look into cooling pads.
Thanks again,
Chris
Technical Discussion » Throttling CPU usage down
- chrislesage
- 5 posts
- Offline
Hi everyone,
Is there a way to manage the CPU usage of Houdini? Specifically, I'd like to throttle it back. I'm working on a laptop, and I can easily get to a point where I'm overheating and my fan is going crazy.
I'd like to sacrifice performance to keep my laptop below a burnout threshold. Typical things I'm doing are point wrangles, coloring and deforming points and animating it.
I've tried searching for an answer, but this is a bit of a difficult search phrase. Pardon me if there is an obvious preference somewhere.
Thanks,
Chris
Is there a way to manage the CPU usage of Houdini? Specifically, I'd like to throttle it back. I'm working on a laptop, and I can easily get to a point where I'm overheating and my fan is going crazy.
I'd like to sacrifice performance to keep my laptop below a burnout threshold. Typical things I'm doing are point wrangles, coloring and deforming points and animating it.
I've tried searching for an answer, but this is a bit of a difficult search phrase. Pardon me if there is an obvious preference somewhere.
Thanks,
Chris
-
- Quick Links