Jump to content

FredDoes3D

Members
  • Content count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About FredDoes3D

  • Rank
    Peon
  • Birthday 09/20/1988

Personal Information

  • Name
    Frederik
  • Location
    Valencia,Spain
  • Interests
    Character Art
    Video Game Art
    Procedural Modeling and Animation
    VFX
    Dogs

Recent Profile Visitors

763 profile views
  1. Hi, i got the same problem right now, has this been resolved? Would love to know if you got this to work. Thanks!
  2. group by expression

    Cool! f1480187 thank you taking the time! Will try it when I get home. Cheers
  3. group by expression

    Anybody? Was hoping this would be an easy "this is how you do it in 2 easy steps..." for any veteran Best, Frederik
  4. group by expression

    Hi there, I am currently following the quite amazing tutorial by Jonah Hall called Creating Procedural Rigs and Controlling Motion in Houdini on Pluralsight. It has been released a few years back (2011 i think) so he is using an older version of houdini. Most of it can easily be recreated in H16 but 2/3 into the tutorial he groups points using the group node and the "point" expression and i am having troubles recreating the same effect in H16, the way grouping works has changed quite a bit from what i can tell with my limited experience and I'm a bit stuck. The expression he uses goes something like: point("../in,$PT,"step",0) < point("../in,$PT-1,"step",0) from what I understand he is comparing each point with its neighbor on the connected line ($PT-1) and groups based on the step attribute (step is created in chops based on earlier generated motion data) Could any of you point me in the right direction of how to approach this? Thank you! Frederik
  5. got it, thanks! actually used a bit of houdini today for the first time in an actual project at work, some procedural modeling to make my life a lot easier. so proud!
  6. just got home and got it to work right away! saved me a lot of heartache here Twan, thanks! gonna dig into some more complicated assets now! when you say: add things to native Houdini nodes, inside your otl, which you can then promote to the top layer, into the type properties could you explain that to me as if i were 7?
  7. additional question: do you recommend to always work in the Operator Type Properties or do you use the Parameter Interface when you dont plan to export it to a game engine? Are there drawbacks to the Type Properties? Also, do you know if there are limitations of what the houdini engine for unity can handle? aka nodes that arent supported? Thank you so much
  8. just had a quick look during my break, the interfaces really do look almost identical! can i still use drag and drop to place my parameters or do i have to make the link manually?
  9. Thank you Twan, that clears it up in theory! Gotta see if I can get it to work practically tonight Everything still is wondrous new terrain for me in Houdini. way cool
  10. Will give this a go tonight when i get home from work, thanks for the suggestion Geordie. I was just watching some tutorial on the subject and i believe i havent closed my asset yesterday "match current definition" not sure if that makes a difference. also i noted, the tutor created the gui the following way: create parameter in the parameter editor, copy, then paste relative reference into the asset. what i have been doing was: left click and drag from asset into the GUI editor. maybe that creates bad links? Usually while creating assets in houdini that is not a problem, right?
  11. Hi there, been trying out the houdini/unity integration lately. Very interesting stuff! I did run into the problem that when i export my digital assets as OTLs they show up fine in unity but as soon as i expose parameters in the GUI to be made available in engine (save asset again, reload in unity), the asset disappears from the unity viewport. Im not doign anything fancy, just exposing a boxes size attribute to keep the error margin to a minimum. This seems to be a bug as i had it working before with other assets and i kept trying it multiple times always resulting in the same issue. Anybody else having similar issues?
  12. dt procedural rigs and controlling motion problem

    I uploaded the hip file and sim data (read in halfway through) this should make it easier to see what i broke AutoRigBugsProject.rar
  13. Newbie Transform Node confusion

    great, ill have a play with bbox too, learned a bit about it a while back in class but i will definitely have to brush up on it
  14. dt procedural rigs and controlling motion problem

    Hi there , I know this is an old topic but I am following the same tutorial (which is really well done) and i am running into a different error. A bit later in the video he creates multiple channels in a chop-net and then references them in an attribute create node using chop("../bug_chops/F/step") which he later uses in a foreach loop to group certain points. my problem is that the referencing does not work (houdini 14). i thought i made an error copying what he does so i opened his scene file and i have the same error so i assume its in the referencing. i noticed that if i change chop("../bug_chops/F/step") to chop("../bug_chops/F/step$ID") or to a specific channel aka: chop("../bug_chops/F/step8") (just picking one of the many chanels randomly) i do get some data but its not the right one im fairly sure as the patterns do not co-relate with what they are meant to do. Has the attribute create node or the way things are referenced from/to chopnets changed drastically? i notice the node attributes look different from the ones in the video. maybe somebody knows a work around to access the data from the chop net? would be great if somebody knows whats up, would be a shame not being able to finish the tutorial thanks in advance
×