Houdini transition pdf by Jordi Bares

[Pooby]

I don't see why you'd need to retopo a mesh fusion mesh if it's hard surface and non deforming. They don't seem that bad You just need it to have decent UVs and not be an enormous poly count.

[Nizar]

agree, but are usually messed topology, it make hard to do a good UV

[origin]

Im pretty impressed by Houdini so far.
As usual you need a day or two to get used to some things and relearn few shortcuts.
Selection model is really weird. I barely scratched the houdini surface but first impression is that it isnt as visual as ICe, lots of expressions/attributes.


and meshfusion and uvs...

auto-uvs -> mari -> profit!

[Pooby]

Im pretty impressed by Houdini so far.
As usual you need a day or two to get used to some things and relearn few shortcuts.
Selection model is really weird. I barely scratched the houdini surface but first impression is that it isnt as visual as ICe, lots of expressions/attributes.

My impression too and slightly disappointed about that part. I guess it's just a different way of working.

[mc_axe]

[dirtydog]

Because whilst dynamesh is great, (Amazing in fact. )for hard surface clean models, zremesher which you need to get a smallish mesh, let's it down a little.
Also, dynamesh doesn't have control over the smoothness of the mesh Boolean transitions as mesh fusion does. and it is destructive whereas MF allows change after the fact.
Dynamesh and zremesher can get a good result but not an astoundingly good result. Sometimes you want that.

I seen a webcast by Paul Gadbury of Pixolpgic, who said they are working on a hard surface zremesher in future releases.

[Bullit]

Great showing: Fixed in tomorrow build

http://www.sidefx.com/index.php?option= ... 834b9686bf

[MauricioPC]

Posted: Thu Mar 20, 2014 11:02 pm Post subject: Reply with quote
Fixed in tomorrow's build.

Come on! That is simply amazing.


I need to laid me laziness away and start learning Houdini and Cinema 4D and get out of this AD bandwagon. At least Mudbox is cheap and I can continue to use it (yeah, I like Mudbox).

[Mathaeus]

I have to admit that I love MauricioPC's posts. He sounds like entire studio, not one man. I mean, always at least two 3d apps in the pool .
Don't want to break party, but here's one that can't be fixed tomorrow, I'm afraid. That is, user experienced about 15 times slower playback than in Maya, on something that looks like a mid-level rig. It's confirmed by developer, later. It seems they are planning to improve the playback thing in next version - so, $$$$ for hope in next version. Well, not bad.....

[MauricioPC]

They said that it's fixed but it's only coming out in the next version, right? Or I understood wrong?

As for apps, yeah, I try more than I actually use. I guess that's related to when I was an editor and lost jobs because I didn't know Final Cut. I were an Avid editor and DS user. That didn't panned out well.

I did used 3ds Max for motion graphics back in 2006 but later I left to work in sales (made more money than as a editor). Now I was returning learning Softimage. Didn't work out so well. Tried Maya, C4D and Modo and by being dumb, I haven't decide on one and so here we are. I guess I'm afraid to chose wrong again.

Well, sorry for the off topic.

[angus_davidson]

Houdini has a daily build you can download. No need to wait for the next release ;)

[Mathaeus]

They said that it's fixed but it's only coming out in the next version, right? Or I understood wrong?

most likely, this means, that playback and scene evaluation power, well known from SI and Maya, simply does not exist in Houdini. It can't be "fixed", because there is nothing to fix. I'm pretty sure, nothing related to this available for download too, daily or hourly.
And... by the way, how many daily fixes can be done by such team, in reality. Who's request has priority. By large company or by small team.

[halfdan]

They said that it's fixed but it's only coming out in the next version, right? Or I understood wrong?

most likely, this means, that playback and scene evaluation power, well known from SI and Maya, simply does not exist in Houdini. It can't be "fixed", because there is nothing to fix. I'm pretty sure, nothing related to this available for download too, daily or hourly.
And... by the way, how many daily fixes can be done by such team, in reality. Who's request has priority. By large company or by small team.

Nope. It's actually fixed. The changes are just too extensive to back-port to the 13.0 daily build.

No-one gets a preferential treatment for the daily bug fixes. If they are show-stoppers, we drop other things and work on them, unless they're really unfixable without breaking compatibility, in which case we will do what we can to provide you with a workaround.

If you're curious, you can have a look at the logs for the daily builds and judge for yourself.