Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Andr1

  • Rank

Personal Information

  • Name
    A D
  1. 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
  2. how.pwd() on created otl

    UPDATE. kwargs['node'] is actually accepted inside a onLoaded event handler. I don't know why it was not working when I tried it the first time.. However it's not mentioned in the documentation of Hou17. ------- What's the reason for the 'node' key not being accepted in a onLoaded event handler script? http://www.sidefx.com/docs/houdini/hom/locations.html#node_event_kwargs I need to know what is the instance of the digital asset in the onLoaded script. If do something like hou.pwd() it would return "/"
  3. Access factory actions called by hotkeys

    Ohh, I'd like to know as well. In my case I'd like to know how to access the "Select Viewport" action, that you can run from viewport menu. Alternatively I'd like to know if you can run an hotkey with python. (In my case it would be "N", which is assigned by default to the 'Select Viewport' action)
  4. Convolution curve

    That's nice, but for my part, I'm more interested to learn about the method, than actually using that otl. I guess it's a blackboxed digital asset, right? cheers
  5. Hello guys, I'm sorry for the little teasing title, but haven't found a solution so far, after reading docs and searching through forums. So here my questions: 1) In case of a viewport layout split in 2 (or more), I would like to know on which of the 2 viewports the radial menu is over. If the radial menu is aware of which viewport is underneath, it could set specific settings or object isolations for that particular viewport (like the viewport isolator node). I'm using the following code in my radial menu script, but it is always returning the first viewport, even when the radial menu is over the second viewport. import toolutils activepane = toolutils.activePane(kwargs) print activepane.curViewport() 2) Given a double display setup, with two Scene View panels (one on each display), I would like to know on which sceneviewer() the mouse cursor is over, and most importantly what are the (x,y) mouse coordinates relative to the viewport of that sceneviewer. Do you know if this is possible at all? I guess I could do something with the Mouse CHOP node and mapFromMouseChop() function, but Mouse Chop seems to be registering only the position of the mouse in the main Display. Is it not aware of the second display? 3) Bonus question: do you know how to refresh the 'radial menu' menu, so that newly installed radial menu files are loaded without need to restart Hou? Ideally I would like to embed a radial menu file in the 'extra file' section of my Digital Asset. OnCreated(), the asset would then save the radial menu file in the user preferences directory, and I would like the user to be able to use the new radial menu right away, without restart. Thanks for any help!
  6. Convolution curve

    very interesting, would like to know as well!
  7. Houdini 18 Wishlist

    COPs seriously needs some love by SideFX, I keep hearing people lamenting about it. My limited experience with it is very frustrating. I've found it slow and much more prone to crash than any other context. Also, it would be useful to have some kind of Cop Wrangle Node to store attributes and do some quick computation. Instead of being forced to go to Sop and back to Cop (which make things very slow and unstable) That would be really useful. I can imagine using this feature a lot for overnight wedging: you set a cooking time threshold and as soon as the wedge iteration cooking goes past it, the wedger skips automatically to cook and render the next iteration. * Some volume sculpting tool with good performance would be super nice. I'm struggling these days to get the coordinates of the viewport when you have multiple sceneviewers and multiple displays.. I can't imagine that such a basic feature is not present in the hou module?
  8. H17.5 Launch Event March 7

    edit. wrong thread
  9. H17.5 Launch Event March 7

    I don't quite understand these LOPs. Would they allow the wedge node to cook and render in parallel multiple iterations?
  10. We're getting closer, but something is wrong.. If you stop at any frame, you can notice that every new extruded cube is being randomly scaled based on the iteration, but next frame it immediately loses the randomness. Dunno whats wrong polyextrude_solver_foreach_MHHH.hiplc