Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Community Reputation

3 Neutral

About Andr1

  • Rank

Personal Information

  • Name
    A D
  1. Collisions in Vellum

    This came handy thanks! But for some reason the hitnum attrib never update, and remains at 0. Do you know why?
  2. I don't have experience with sims, but I constantly finding myself falling in the following traps when developing some tool: 1- focus on efficiency in the first stages (wrong) 2- aiming at a 101% procedural solution (wronger) 3- fighting against Houdini's poor parameters UI and control, with the goal in mind to produce a good user experience (lot of python trickery involved) These obsessions are very time consuming, and sucks much energy and motivation from the greater creative goal.
  3. Hide parameters through python

    just so you know and go crazy like I did, one issue with doing that with python is that parms hidden won't stay hidden across sessions. This is also the case with disabled parms. This issue is never going to be fixed. A workaround is to create a hidden toggle for driving the expressions 'Disable When' and 'Hide When' for each parm you need to hide/disable. I really don't like this workaround, but it seems the only option if you really need consistency across sessions? Quoting from the Support:
  4. Rename label in multiparm list.

    sorry for the gravedig, do you know any way to set different labels to the different instances of the same multiparm parameter? Example for a multiparmblock parameter "myParm#": I want "myParm1" and "myParm2" instances to be labelled "Bingo", while "myParm3" instance should be labelled "Bongo". Is this even possible to do? cheers
  5. Triggering a top cook from hda interface

    Hi, as I mentioned I yet have to test this workflow, but isn't dirtyTasks() function what you need for it?
  6. Read a TOPs attributes from SOP

    did u managed eventually?
  7. Triggering a top cook from hda interface

    Hi, it seems that you have looked into the pdg api, but probably you want to use the hou.TopNode class instead and more precisely the executeGraph() function https://www.sidefx.com/docs/houdini/hom/hou/TopNode.html let me know if you succeed as I'll have to do the same soon (cook topnet from hda) cheers
  8. about parallel processing in VEX

    Thanks for pointing this out. Very interesting. I don't quite understand the last post, when the he's addressing the idea of procedurally assign the Thread Size, so that each thread has the same number of iterations to deal with. To me it's seems a very good practice.. Why this should be dangerous? If I run 1000 iterations and I have a 10 threads machine, it seems obvious to me that I want to have a Thread Size of 100, and no other number. Could anybody clear this, please? thanks
  9. This is only guess work, as I'm not an hardware expert, but I'm in a similar situation of the op: very tempted by the new ryzens. New ryzen mobos should have more lanes, If I'm correct, so maybe you would have a little bit more expansion room than previous gen. Also, you can actually put 128GB of Ram in the new ryzens, as some x570 mobos support up to 128GB like every threadripper mobo does. To consider: 1) It would be only dual channel memory, vs quad channel of threadripper; dual vs quad channel, how much it matters for Houdini workload? 2) You would be force to buy 32GB sticks, which I guess are expensive as hell, and maybe also rare to find. 3) Also, said x570 mobos with 128GB support could cost a premium. At this point, if you need 128GB of ram, maybe it's worth investing in a threadripper? They say new threadripper are coming in october.. but who really knows..
  10. Houdini 18 Wishlist

    edit. ot
  11. Houdini 18 Wishlist

    SideFX it's time to to show some love for COPs . It would be nice to have fixed the instability and the slowness of COPs, and also have some nice low level tools. COPs could easily compete with Substance Designer for procedural texture creation, especially when Allegortmic is not caring at all about their substance plugin for Houdini. There's opportunity here. Also, it would much welcome to have better parameters UI. There are lots small improvements to do in this regard: like being able to decide how to justify the parameters, unified alignment, better labeling systems, etc I want the controls of my Digital Assets to feel modern and to be space-efficient.
  12. I found a solution for my case: I wanted a python node to destroy a specific node. I created a parameter button on another node, with a callback script that would destroy the node on button press. Then I called the parm button inside the python node and invoked .pressButton() Every time the python cook it will try to press the button. It seems to be important to have both nodes (python and button node) disconnected from each other, otherwise it would trigger again the same error. See attached file, maybe can help you Cheers python_destroyItem.hiplc
  13. I happen to have the same issue. Did your eventually find a fix? cheers
  14. I would like to know as well. It seems that for a Digital Asset instance you should register the event callback inside the OnLoaded event handler script. Am I right? Indeed, I'm currently registering an event callback (flag change) for a Digital Asset inside an onLoaded script. My issue is that the callback function is being run twice. Do you happen to know the reason? This is the code I'm using inside the onLoaded script: node = hou.node("/obj/geo1/flagchanged1") def flagChanged(event_type, **kwargs): if node.isGenericFlagSet(hou.nodeFlag.Display) == 1: print("display flag is set") node.addEventCallback((hou.nodeEventType.FlagChanged,), flagChanged) --------------------------------- --------------------------------- UPDATE. For anybody that might face the same issue in the future: I believe I understand what's going on: it runs two times because when you change the Display Flag on a node with the left mouse button you would automatically set the render flag as well. So you are actually setting two flags with one click, that's why the event .FlagChanged is being triggered 2 times. Indeed, If you try to use the combination alt+LMB to exclusively set the display flag (and leave the render flag in place), the event callback is triggered only 1 time. I guess that you can't really avoid this behavior and, in order to trigger 1 single event callback when the display flag is changed, you should write some conditional and use some toggle parameter to write to and check against it every time the event callback is triggered. ------------------------------- Q_onLoaded_checkFlag.hiplc