Jump to content

j00ey

Members
  • Content count

    235
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    3

j00ey last won the day on July 26 2018

j00ey had the most liked content!

Community Reputation

37 Excellent

1 Follower

About j00ey

  • Rank
    Initiate

Contact Methods

  • Website URL
    http://50percentgray.com

Personal Information

  • Name
    Tim
  • Location
    London

Recent Profile Visitors

3,899 profile views
  1. Easiest way is to promote your attribute to detail, set to maximum - set the new name to eg max_layer and don't delete original attribute - then do something like the following in a wrangle: [assuming it's a prim integer attribute called 'layer', set the wrangle to run over prims] if(i@layer == detail(0, "max_layer", 0)) removeprim(0, @primnum, 1);
  2. Nuke vs COPs

    There are things you can do in COPs very easily that are a real headache in Nuke and also many things you can't do at all I think, but I've been bitten a few times by relying on it and it then bugging out on me at the last minute.
  3. Create Crisp Edge Bevel Style look

    ok, here's a pure COPs method pattern_pure_COPs.hiplc
  4. Create Crisp Edge Bevel Style look

    Here's one way of doing it, though I imagine you probably mean a pure COPs method. If I get time I'll try and make you one. heightfield_to_COP.hiplc
  5. In case it's useful to anyone else, I figured out from imagemagick.org that I could just add -tile 4x1 to the command string in and it does exactly what I was after
  6. I am a newcomer to TOPs. I watched the 17.5 release videos a few months ago and a few tutorials but I haven't had chance or need to investigate properly until now.. I'm developing a system to render some scenes from 4 - 5 cameras, the output of which will play on 4 - 5 monitors so I thought an ideal way to do tests would be in TOPs - render all the cameras, partition the renders by frame and then put them through Image Magick, then FFMpeg to get an idea of all the content playing on the screens next to each other. The attached image shows my 4 camera set up inside of Houdini - I basically want to replicate that but as a movie I can watch in real time and send to people. I have hit a brick wall trying to get the Image Magick TOP to do the montage - I don't want the images in a grid, I want them in a row. Is this possible? Presumably with the right command string it is but I'm drawing a blank. Many thanks
  7. snap viewport image

    I always forget that!
  8. snap viewport image

    You can flipbook a single frame then in MPlay first do Render/New Sequence then go to Windows/Sequence List and you can toggle between multiple flipbooks. I've never actually needed that for stills but I use it all the time for comparing animations. There are various display options for comparison.
  9. Vellum strut setup

    I'm not a vellum expert but if you turn up the bend stiffness on the cloth constraint [as opposed to the struts] to say 50, the behaviour is similar
  10. find points and cut.

    This is a bit of a naive test but see if it helps chop_up_shape.hip
  11. inline vop

    I haven't looked at your scene but in the amended one of mine you've disconnected the enumerate SOP so there's no id attribute to bind, so it will always be zero and the conditions in the inline VOP always evaluate as false
  12. inline vop

    At a guess I'd say your loop isn't executing
  13. inline vop

    Also it's a good idea when you're testing things and figuring out what's going on in your shaders to work at the top level of a material network, not inside a material builder because you can assign anything as a material. What I usually do is make a null, call it 'test' and assign that as a material, then just plug things into that to test
  14. inline vop

    For a start you have id set as a vector output, and you're binding it as a vector too. It's an integer. I haven't really got time to try and unpick the logic of your for loop but it seems to me you're trying to run before you can walk. Houdini is telling you via the colour labels what's an int, float, vector etc. You need to be able to recognize them and know what data types you need to use to get what you're after. Don't overcomplicate with for loops, learn about basic stuff first like setting outputs in your inline VOP, writing to them, reading in geometry attributes, manipulating them and then outputting them.
  15. inline vop

    I hadn't actually read your code properly earlier but again you're setting a condition which can never be true. You initialise a variable id as zero, then you say if it's between 2 and 10 set the Cd variable, but it's always zero. For the id workflow I mentioned you need to read in the id from the geometry, in your sample scene you've set it as an output, and as a vector. Attached is a sample scene. inline_colour_by_id.hip
×