Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


ThomasPara last won the day on February 3

ThomasPara had the most liked content!

Community Reputation

100 Excellent


About ThomasPara

  • Rank

Contact Methods

  • Website URL

Personal Information

  • Name
  • Location

Recent Profile Visitors

1,184 profile views
  1. You could "object merge" inn a null and use that as a reference. Simplest i can think of now.
  2. Studio Workstation

    I would have gone for a watercooler instead of the fan. I have a 3900x at home with a "nxzt kraken x62" cooler in a "fractal design define r6" case. Not satisfied with the temperatures, goes into the high 80's. Have a i9 9900k at work with a x72, and have never seen it above 50c. I can accept the temperatures at home, but i dont think it would last long as a workmachine. Another thing is that it boosts for everything, and with a fan it would ramp up and down all the time.
  3. or you could use a fuse and get your centers from that. CenterOfEachColoni_01_fix.hiplc
  4. wrangle - string reference in vex from spare parameter

    Your attribute is already a string, so dont use the quotation marks. point(s@mystring,"Cd",@ptnum);
  5. Advecting curves help

    Its differential growth, so its not that complex realy. Theres a thread on this forum about it. Basicly its pointrelax set to 3d space, noise in pscale and a resample inside a solver. I think Entagma also has a tutorial about it.
  6. Align card with vector

    In general i avoid "for-each" networks, it usualy becomes to slow. And when things get slow, art directing and creativity get worse. You can make hda's of your vex setups and then it gets as easy to use as a node. You can get a long way with learning how to use vectors, matrixes and quaternions.
  7. swirly lines catching object moving

    My knowledge comes from other people sharing their knowledge. And odforce is a place where i have gained alot of knowledge, and i hope people will continue to share their stuff so i can learn more.
  8. swirly lines catching object moving

    Its more in how people use the tool, since its werry complex and maybe not that intuitive i want the ability to update the tool. I also want to present it in a way that people can see how its used. When it comes to the code, i offcourse loose all control, unless its a blackbox, but thats kinda unfair. But i have made an example using pops that can be further built on, and that have the same core principals. popcurves_01.hiplc
  9. Stiffness, vellum vs wire solver

    Its basicly stacked packed rbd primitives, connected with conetwist constraints. Then you transform/rebuild your curves based on thoose rbds. If you dont want destruction its pretty straight forward, if you want to break it or even want slow motion, its alot more. Heres a basic setup. TreeSystem_rbd.hiplc
  10. Align card with vector

    Same setup with your feathers, and with uniform scale. Mystique_02.hipnc
  11. swirly lines catching object moving

    I have the tool you need, my problem is how and where to share this kinds of things. Not that eager to just drop the hda in a place where i have no controll over it.
  12. Align card with vector

    Heres an example of how you can set it up. mystique_01.hip
  13. Stiffness, vellum vs wire solver

    Thanks, had my hopes up for vellum aswell, since this was pre 17. But never made it work out as i wanted. Also tried pop-grains without any luck.
  14. Stiffness, vellum vs wire solver

    Seems about right. Did some rnd on this, and went with rbds. Easier to interact with other objects and get stiff branches. Downside is the amount off setup.
  15. Removing Points on corners

    instead you can use a pointwrangle, input your points in the first input, and your cornerpoints in the second. int nearpt = nearpoint(1,@P,0.0001); if(nearpt >= 0){ i@group_corners = 1; }