Jump to content

friedasparagus

Members
  • Content count

    21
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

3 Neutral

About friedasparagus

  • Rank
    Peon

Personal Information

  • Name
    Henry
  • Location
    London

Recent Profile Visitors

754 profile views
  1. Setting a Data Parm

    Thanks Tom I will have to go that way after all, storing the geo via HOM is fine in the callback, but querying the stored HOU_Geometry data on every frame is more than likely too expensive for my budget! Unless I do something funky querying the stashed geo via HOM and caching the results. Which is also possible... Back to tinkering
  2. Setting a Data Parm

    Hello, I'm getting my knickers in a right old twist trying to set a Data Parameter. Does anyone have any insight on how to go about this? Also, is it possible to use them to store arbitrary data? Thanks! EDIT: Ended up going through HOM which made things pretty straightforward... still curious is there's another way though
  3. MSS_SingleOpState render shaded 'guides'

    Hey! Sorry for the super late reply, and thanks for pointing me in the RE_Geometry direction. Unfortunately I haven't had much time to finish this one off, but hopefully I'll be able to put the advice into practice soon!
  4. MSS_SingleOpState render shaded 'guides'

    Hi again! Thanks very much for the reply. Here's a look at what I was driving at (built against 16.5.536). It's still very raw and unfortunately change of target version has introduced a crash in the node which I haven't had a chance to chase down, hence the very paired down example file. If you did feel like taking a look, hopefully it will give you a better idea though! (NB. Turning primitive snapping on helps replicate the feel I was aiming for) In the attached scene I've created persistent handles for each of the 'positions' on the two fa_edgeloop nodes. The idea is to be able to interact with the positions to create seams along the shortest edge loop extending from the nearest point to each position. What I'd like the state to render is just a sphere per position that can be dragged over the surface, would also be nice to provide colour feedback on the state of each position (i.e. did it succeed in finding a valid loop, is it set to only return closed loops?... etc). Having used SOP_NodeVerb and all the nice goodies that come with that, I was hesitant to add a cookMyGuide to the node for this purpose, and it seemed like the rendering of these guides really did belong with the accompanying state. Hopefully that makes some kind of sense. This is my first foray in rendering anything in the viewport directly! FA_Edgeloop.dll edgeloop_test_demo.hiplc
  5. Hello again, I've been digging around trying to find a way of rendering some shaded geometry within the doRender() method of a viewport state. The only example I could find was in MSS_CustomBrushState via DM_Detail which only has as renderWire() method. Looked into the idea of rendering a set of GT_PrimSphere objects, but wanted to check to see if anyone had tried something similar and if this was the right way to go, or if there was a more straightforward way of handling this. Any help very much appreciated! Thanks, Henry
  6. Caching Data between cooks

    Ah, thanks MrScienceOfficer! I think I've looked at the same thing for too long and stopped actually seeing... That does indeed look like what I was looking for.
  7. Hello out there, I've been taking a good hard look at the SOP_NodeVerb API, and was wondering whether anyone had any pointers on best practices for calling certain functions only when the input geometry has changed. In my case this building a GEO_PointTree and a GEO_DetachedHedgeInterface, the result of which I've been storing in the subclassed SOP_NodeCache. I managed to get something working using COOK_GENERIC and DEP_MicroNode to check when the input node had last been visited to decide whether or not to run cookInputs() and update the cache. But it feels hacky and horrible There's a strong possibility that I've over-complicated things here, and just wanted to reach out in case anyone had any 'patterns' to hand for this before I go down any other blind alleys Cheers! Henry
  8. HDK 16.5 How to generate *.proto.h

    Hello! Just wanted to jump on this one, as I'm struggling to work out how to create multiparms via a DS file/string. Does anyone have a working example to go from? So far I'm really enjoying the approach, but this has me proper stumped :/ Many thanks, Henry EDIT: Don't know what was going on before, but I obviously managed to do something squiffy... maybe I missed a '#'. Turns out the following is just fine { name parameters multiparm { name "locations" parm { name "enable#" label "Enable#" type toggle default { "0" } joinnext } parm { name "pos#" label "Position#" type vector size 3 default { "0" "0" "0" } } } }
  9. Follow path auto-bank (the new H16 constraints)

    Hi again... Just had a little play with moving more of that method into CHOPs... It is not finished by any means (try moving part of the path off the ground plane and watch the polyframe go mental!) but maybe it might give you some ideas... Another note is that the channel wrangle in the chopnet is completely unnecessary, it just felt cleaner to me that two math nodes and a slope! I'll certainly be revisiting this, I'll let you know if I get anywhere Cheers, Henry follow_path_chops.hiplc
  10. Follow path auto-bank (the new H16 constraints)

    Hey ikoon, That fourth input on the Follow Path CHOP is a funny one... it seems to accept channels named "roll0" and "pos0" and will use them to override the position on the curve and the roll. Either one can be present or not and the other will still work (i.e. one channel named "pos0" will still work without accompanying "roll0" channel)
  11. Bake texture ROP outputs black...

    Hi Matthew, that is an interesting one. I'll be sure to keep an eye out for that in future. It always seemed strange though, that the other maps 'normal etc', would generate fine, but displacement was a no show. Thanks for the heads up though!
  12. Handles in Digital Asset

    This one is super old now, but if anyone if out there, I'd love to know if this one got solved somehow, somewhere... Thanks!
  13. Bake texture ROP outputs black...

    Erm... yes, maybe a bit fast of the mark... I haven't actually been as glued to the changelog as it might seem :/ The mantra thing is a bit of a mystery, the bake exports node is in there, it's just not returning anything anymore, and even in the principled shader the displacement channel in the bake exports just seems to be unfinished. If you crack open the bake exports, the inline vex responsible for exporting the 'Ds' channel doesn't refer to the uvobject at all. It only runs if there's some displacement being performed on the high res object and then it only returns the difference between the original highres mesh and the result of the displacement. Ah well, I'm sure it'll be taken care of. I was up for having a debug, but the other mystery is why the baking stops working (on all channels) when you unlock the principled shader, it made the job a little bigger than I had time for :/
  14. Bake texture ROP outputs black...

    Hi guys, Just a heads up that there is movement on the bake texture ROP. Build 15.5.539 has tangent normals working perfectly... :o) (Displacement still a mystery, hopefully that's on the way too) EDIT: May have gotten a bit excited, it works with the principled shader but not with a Mantra Surface... still having a poke
  15. Bake texture ROP outputs black...

    Hi again Johann, Yes, no word here either. I've also been hunting through the daily builds with wide-eyed hope and expectation... Please do let us know if you hear anything, Cheers, Henry
×