Jump to content

j00ey

Members
  • Content count

    238
  • 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

38 Excellent

1 Follower

About j00ey

  • Rank
    Initiate

Contact Methods

  • Website URL
    http://50percentgray.com

Personal Information

  • Name
    Tim
  • Location
    London

Recent Profile Visitors

3,964 profile views
  1. Thanks very much Geoff - I can't believe I didn't think of that myself!
  2. Hi Jiri Thanks for the note. I'll try other drivers and see if that changes anything. I'm currently using 6.3.17-3 and I'm also on Windows 10, H18.0.287 I just opened an old scene and I can pan but not zoom so something's definitely been switched around... I just tried the stroke SOP and I'm also getting constant 1.0 pressure - stroke_angle is constant 0.0 and stroke_tilt is constant 90.0. Likewise H17.5 works as expected
  3. Does anyone else have a problem panning in the viewport with H18 using a Wacom? I have an Intuos 5 Touch and my buttons are set correctly as per normal but when I try to pan it tumbles instead. I've deleted my prefs in case that was the problem but it's not... Thanks
  4. 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);
  5. 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.
  6. Create Crisp Edge Bevel Style look

    ok, here's a pure COPs method pattern_pure_COPs.hiplc
  7. 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
  8. 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
  9. 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
  10. snap viewport image

    I always forget that!
  11. 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.
  12. 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
  13. find points and cut.

    This is a bit of a naive test but see if it helps chop_up_shape.hip
  14. 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
  15. inline vop

    At a guess I'd say your loop isn't executing
×