/houdini/

[Anonymous No.674086]

Houdini general
What are you working on?
Post questions here

[Anonymous No.674092]

>>674086
here's my demo reel:
https://www.youtube.com/watch?v=MIcUW9QFMLE&t=
But I know, this all could be done better and easier in Blender LMAO!

[Anonymous No.674109]

Good job on that filename, OP. Thread ruined.

[Anonymous No.674146]

>>674092
>>674109
SEETHING

[Anonymous No.674147]

>>674146
Not really. I expect of Houdini users to be mature enough to not enter into pointless software frays.

[Anonymous No.674161]

>>674092

each scene there took a lot time to finish. houdini id good software but blender is not famous for its simulations..

[Anonymous No.674181]

>>674086
Studying ragdolls.

[Anonymous No.674230]

>>674181
yeah mean soft bodies?

[Anonymous No.674232]

>>674161
blender isn't really famous for anything to be fair

[Anonymous No.674261]

>>674181
Maybe look into vellum soft constraints for the hands, it'd look a lot better if they weren't just intersecting

[Anonymous No.674262]

non color graded version of a river i've been working on

[Anonymous No.674311]

>>674230
No, it's crowds. Bullet/RBD.

>>674261
I can give soft constraints or spring constraints a shot. Mixing multiple solvers sounds like overkill.

>>674262
Color grading is going to differentiate wet rocks from dry rocks unless you hand-paint it. I like the moss.

[Anonymous No.674313]

>>674230
No, it's crowds. Bullet/RBD.

>>674261
I can give soft constraints or spring constraints a shot. Mixing multiple solvers sounds like overkill.

>>674262
Color grading isn't going to differentiate wet rocks on land from dry rocks underwater unless you hand-paint a mask. The color is currently all the same looking like dry rock. I like the moss.

[Anonymous No.674316]

>>674232
blenders fan-base is famous for being retarded rabid cultist that want to convert the whole industry into blender users.
A little bit similar to muslims desu

[Anonymous No.674360]

>>674313
Yeah wet maps are on my to do list, but at this point I'd rather just make a new sim altogether

[Anonymous No.674552]

Hours since last crash: 0.
Hours since last paycheck: 0.

[Anonymous No.675937]

i translated a vop network from a tutorial into vex and i feel like less of a shitter than I actually am
//sine ripple deformer
//controllable sine wave base formula
//sin((distance*frequncy) + (-time*speed)) * amplitude

//store position of target point on second input
vector target = point(1, 'P', 0);

//initialise and normalise normals
@N = normalize(@N);

//time variable with speed control
float timeMult = -@Time * ch('speed');

//calculate distance from points to origin
//float dist = distance(@P, {0,0,0});

//calculate distance form points to input 2
float dist = distance(@P, target);

//frequency control
float freqDist = dist * ch('frequency');


//sin of distance + negative @Time driving phase creating animation
float distSin = sin(freqDist + timeMult);

//amplitude control
float amp = distSin * ch('amplitude');


//amplitude multiplier to fade wave to edge
float decay = fit(dist, 0, 10, 1, 0);


//displace along normals
@P = @P + (@N * amp * decay);

[Anonymous No.675939]

>>675937
ps.
that last fit is shitty because of the hardcoded 10. that value is based on a 20x20 grid.

[Anonymous No.675940]

>>675937
>@N = normalize(@N);
No need to. You can do @N = @N; to make them explicit, but they are computed on demand if they weren't assigned before (as if you applied smooth shading). Also, unless you are computing normals in an unorthodox way, they are already normalized.

>@P = @P + (@N * amp * decay);
You can simplify this to @P += @N * amp * decay;

[Anonymous No.675941]

>>675940
tyvm

i know about that second one but i left it explicit because i'm a brainlet and i come back to vex after months long breaks so i thought i'd forget the next time. futureproofing against my own stupidity.

[Anonymous No.676029]

can anyone have a look at this file and tell me why the two methods exhibit such different results?

https://mega.nz/#!lw1C3A5I!WFTB6dNPYYhPF2u0ghgWXDEAiupGFxFxBRYW8EPoZwY

[Anonymous No.676059]

>>676029
The difference is caused by the trig functions. In VEX, they operate with radians, while the HScript expression functions work with degrees. If you rewrite your attribwrangle1 like this you'll get the same result from both graphs:

@P.x = sin(radians(ch('copies')));
@P.y = cos(radians(ch('copies')));

[Anonymous No.676064]

>>676059
bless you. do you know why there's such a massive performance penalty doing it via the wrangle?

i'm not sure i'd notice on my desktop machine, but on my ultrabook i actually have to wait a few seconds for the copystamp to cook.

[Anonymous No.676125]

>>676064
>do you know why there's such a massive performance penalty doing it via the wrangle?
Not sure. I did some profiling and isolated the cause to the copies parameter. The solution is to move it up to another node, such as the null in pic related. My guess is that the wrangle is possibly recompiling the code with each different stamp.

[Anonymous No.676171]

Is there pbr viewport support.

[Anonymous No.676175]

>>676171

https://www.sidefx.com/tutorials/game-tools-marmoset-toolbag-rop/

[Anonymous No.676199]

>>676125
thanks again.

[Anonymous No.676229]

>>676171
Native, with 17.5, using the Principled Shader and High Quality Lighting in the viewport. See https://player.vimeo.com/video/322512939

[Anonymous No.676441]

anybody done any rigging or character animation in houdini?

[Anonymous No.676442]

>>676441
I'm not into masochism, thanks

[Anonymous No.676447]

>>676442
i miss softimage

[Anonymous No.676453]

>>676441
I did the Goldfarb tutorial series. My impression is it's slightly better than Blender, but far worse than Maya. It's like they tried to rip off how Maya does things but didn't get the ergonomics right. Rigs are also single-threaded so don't expect fast playback of anything complex.

[Anonymous No.676458]

>>676447
Me too, but it's not coming back.

[Anonymous No.676459]

>>676447
ok THAT'S masochism

[Anonymous No.676514]

>>676459
Zip it kiddo, you probably never had the joy of working with XSI

[Anonymous No.676530]

Making some comfy houdini rocks

[Anonymous No.676667]

>>674086
How easy is it to take the hair/fur made in Houdini and use it on a model in Maya?

[Anonymous No.676669]

>>676514
I actually did for two years, and it was atrocious
kiddo

[Anonymous No.677372]

is there a way to use vray in 17.5? the beta install script doesn't seem to work for it and i'm not sure how to change it.

[Anonymous No.677376]

some nice set ups here:
https://www.richlord.com/tools

i guess this is what happens when gaben doesn't actually let you make videogames.

[Anonymous No.677397]

>>676530
Add an ocean, a beach HDRI, and hand paint some seagulls and you've got yourself an Instagram daily

[Anonymous No.677400]

>>677397
Fuck Instagram dailies.

[Anonymous No.679909]

>>674262
Non-Houdini user here.

How good does your hardware have to be for simulations like this and how long does it take to render?

[Anonymous No.679947]

every time i try to turn on advanced viewport shading it crashes what do?

[Anonymous No.679954]

>>679909
Other anon here.
You can never have enough power and it always takes too long.

[Anonymous No.679957]

>>679909
hq fluid sims are pretty compute intensive

render times depend on renderer. houdin's own mantra is slow as fuck.

[Anonymous No.679963]

>>679947
Submit a bug report.

[Anonymous No.681286]

It's finally out, peeps.

[Anonymous No.681635]

https://vimeo.com/332447363

Holy moly, Simon holmedal still shitting down the throats of everyone else who uses Houdini.

[Anonymous No.682084]

>>681635
>some flow sim with colors

I was expecting something more interesting desu

[Anonymous No.682118]

>>682084
it's a lot more than just a flow sim


https://youtu.be/4TiMo5Ish34?t=1615
https://youtu.be/4TiMo5Ish34?t=3067

[Anonymous No.682193]

>>674086
Do i need all of this "patches" if i want to learn and work with pirated 3ds, maya, zbrush and Autodesk?

[Anonymous No.682205]

>>682193
What?

[Anonymous No.682308]

>tfw brainlet and don't grasp vector mathematics so just try different operations until i get the result that i need

[Anonymous No.682310]

>>682118
he's using vops instead of vex!!!

[Anonymous No.682313]

>>682310
It's almost the same, practically.

[Anonymous No.682497]

>look up something on google
>find the perfect solution posted by this guy every single time

matt is a treasure

[Anonymous No.682509]

>>682313
should someone still learn vex or not?

[Anonymous No.682527]

>>682509
Vex is far more important. Vops are best for certain cases when you want to wire up a few predefined functions and get a graphical controls. When you need any custom code, you're back to vex.

[Anonymous No.682529]

>>682509
vops are basically a node base gui for vex and you can do most things you'd want to do in there. iirc almost all vex functions are available as vop nodes:

http://www.sidefx.com/docs/houdini/vex/functions/index.html

once you've wired up a vop it'll actually produce vex code (you can bring this up by right clicking the vop and viewing the generated code)

there are few downsides to vops, however:
the vex code they spit out is not particularly elegant or optimised so you suffer a small performance penalty. however, unless you're dealing with massive number of points/voxels etc you probably won't feel this.

i'm also not sure it's possible to write your own custom vop function (which you'd be doing in vex anyway).

plus sides to vops:
you don't have to deal with the vex documentation

vex functions can be barebones e.g. the noises. so adding curlnoise with a ui to @P in vex in vex would look something like:

@P += curlnoise(@P * chf('freq') + chv('offset'));

and that's just two parameters. in vops it's a couple of wires.

that said, vops can be clunky when doing logic operations and more complicated stuff. e.g. here's some code for a broken ass supershape creator in vex:
https://pastebin.com/Abpwi2qq

i don't even want to think about doing that in a vop even though you could if you really wanted.

now someone help me fix my broken ass supershape please.

[Anonymous No.682530]

>>682529
this should read:
>@P += curlnoise(@P * chf('freq')) + chv('offset');

[Anonymous No.682543]

this thing's still kinda neat desu.

anyhow, i'm just going to watch a tutorial about this.

[Anonymous No.684191]

made a container yard generator yesterday (it can take any geo, so really it's just a random stack generator), but ran into a problem when i wanted to delete random points + all the points directly above those points.

is there a point equivalent of the intersect function?

https://www.sidefx.com/docs/houdini/vex/functions/intersect.html

i'm assuming rays don't actually intersect points.

solved the problem by putting deleted points into an array and running position checks against that, but can't help but think there's a better way to do this / just useful to have a ray based point intersection checker.

excuse the placeholder assets

[Anonymous No.684860]

>>679909
Redshift renderer supposedly saves 30% on average. Haven't tried it myself though as I am still getting used to Mantra