IslandI'm using osx with a lot of software including Houdini, Maya and C4d. ZERO ISSUEs
Houdini rarely officially supports Apple graphics cards that currently come with laptops and desktops. I learned this with purchasing a Mac Pro. If I were to do it over again, I wouldn't purchase Apple products for serious 3d work. Apple's phones and laptops are pretty reliable but I have had to replace almost everything for defects in my recent Mac Pro. At least it was under warranty.
Found 7 posts.
Search results Show results as topic list.
Houdini Lounge » Houdini for Mac OS X Users
- ClaudioFerroni
- 7 posts
- Offline
Houdini Lounge » What holds yourself/studio from adopting Houdini more?
- ClaudioFerroni
- 7 posts
- Offline
I've not so huge experience in 3D world but after playing for a long while whit C4D and Houdini I can say that if you open a huge C4D scene with a lot of objects, Xpresso rules, tags, and so on let me say that it is easier an equivalent complex scene in Houdini where following the path between the nodes you can understand better and faster. So, for me, Houdini is not more complex than other 3D applications. Somewhere I read that Houdini is just a fast and powerful tool that handles a huge matrix number (its spreadsheet) by applying mathematics rules. As well as all other 3D software. Fortunately, in Houdini this is visible/accessible and you can see it and use it also as a debugger or control.
I don't have issues using Vex (after spending years in C programming, vex is like a toy for me) but absolutely for me is crazy using Vop or any other tentative to replace programming with some horrible block logic.
The interface needs a refresh, for me, but because you can customize this is my last issue.
I'm trying to understand Solaris but let me say that it is not easy.
Ciao
Claudio
I don't have issues using Vex (after spending years in C programming, vex is like a toy for me) but absolutely for me is crazy using Vop or any other tentative to replace programming with some horrible block logic.
The interface needs a refresh, for me, but because you can customize this is my last issue.
I'm trying to understand Solaris but let me say that it is not easy.
Ciao
Claudio
Houdini Learning Materials » Rotate object attached to null?? I'm stuck
- ClaudioFerroni
- 7 posts
- Offline
In any case, are you sure that the multiply *3,414 is correct? Should be pi-greco that's 3,14 and not 3,41
Houdini Lounge » Line+Sweep vs Grid
- ClaudioFerroni
- 7 posts
- Offline
Technical Discussion » CopyToPoint with Polydraw node as source and grid as Target
- ClaudioFerroni
- 7 posts
- Offline
Yes! Thanks a lot :-) ... it works ... now I can solve similar future issues even if I didn't understand WHY! For witch internal reasons Houdini needs this "Move centroid to origin" (not documented on the online manual) in a transform node after a PolyDraw and not for a Circle, Cube, Sphere o other nodes.
I'd like to understand.
Ciao
Claudio
I'd like to understand.
Ciao
Claudio
Technical Discussion » CopyToPoint with Polydraw node as source and grid as Target
- ClaudioFerroni
- 7 posts
- Offline
Dear,
I read everything and tried a lot of test but i don't understand the follow behavior:
1) CopyToPoint with a Circle as Source and a Grid as Target.
The result is perfect, the circles as replicated to each points of the grid
2) CopyToPoint with a PolyDraw as Source and a Grid as Target.
The CopyToPoint node correctly replicate the Polydraw to each points of the Grid but on a difference position of the scene. WHY?
I don't undertsand what I missing. The Houdini manual doesn't mention that I need to set something (attribute, for instance) when I want to use a PolyDraw as source of CopyToPoint.
Where am I wrong?
Thanks for the help.
Claudio
I read everything and tried a lot of test but i don't understand the follow behavior:
1) CopyToPoint with a Circle as Source and a Grid as Target.
The result is perfect, the circles as replicated to each points of the grid
2) CopyToPoint with a PolyDraw as Source and a Grid as Target.
The CopyToPoint node correctly replicate the Polydraw to each points of the Grid but on a difference position of the scene. WHY?
I don't undertsand what I missing. The Houdini manual doesn't mention that I need to set something (attribute, for instance) when I want to use a PolyDraw as source of CopyToPoint.
Where am I wrong?
Thanks for the help.
Claudio
Houdini Lounge » Line+Sweep vs Grid
- ClaudioFerroni
- 7 posts
- Offline
Dear all,
this is my first topic after a while using with Houdini.
My question is simple.
Playing with the combination nodes LINE+SWEEP, where the LINE is connected to both SWEEP input and in SWEEP I set the "second input as crossfade", i create a grid.
I know, I can have the same result using the simple GRID node :-) but my question is: from core Houdini point of view what is better? The simple GRID or the LINE+SWEEP?
I put this question because I realized that the SWEEP node has been implemented a lot and you could create a lot of model playing with all the SWEEP parameter and, for example, the ramp-scale. So, that's means the SWEEP will have an important role in the future?
That's all .. I'm curious to see your notes.
Ciao from Italy
Claudio
this is my first topic after a while using with Houdini.
My question is simple.
Playing with the combination nodes LINE+SWEEP, where the LINE is connected to both SWEEP input and in SWEEP I set the "second input as crossfade", i create a grid.
I know, I can have the same result using the simple GRID node :-) but my question is: from core Houdini point of view what is better? The simple GRID or the LINE+SWEEP?
I put this question because I realized that the SWEEP node has been implemented a lot and you could create a lot of model playing with all the SWEEP parameter and, for example, the ramp-scale. So, that's means the SWEEP will have an important role in the future?
That's all .. I'm curious to see your notes.
Ciao from Italy
Claudio
-
- Quick Links