Jump to content

Search the Community

Showing results for tags 'popwrangle'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Lounge/General chat
    • Education
    • Jobs
    • Marketplace
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering + Solaris!
    • Compositing
    • Games
    • Tools (HDA's etc.)
  • Coders Corner
    • HDK : Houdini Development Kit
    • Scripting
    • Shaders
  • Art and Challenges
    • Finished Work
    • Work in Progress
    • VFX Challenge
    • Effects Challenge Archive
  • Systems and Other Applications
    • Other 3d Packages
    • Operating Systems
    • Hardware
    • Pipeline
  • od|force
    • Feedback, Suggestions, Bugs

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Name


Location


Interests

Found 2 results

  1. Hello Houdini Magicians, This little bit of code is, according to the performance monitor and some debugging, slowing down my simulation... alot. Specially with a high number of particles. The nPt comes from the nearpoint function. I analyzed the performance impact of the nearpoint function with many particles and it is not significant. Its the conditions and moving/removing particles from groups. What is the optimal way to do this?
  2. Hi, I am basically at lost trying to figure out how to record the time when a certain condition is met in a simulation. I am using pop wrangle in this case. The basic problem is that once I set the value to @Time. the attribute get linked to the global time attribute, basically the clock is still running. I know is pretty logical but presents me with a problem... how can I record the exact time when a condition is met. You can take a look at the file for an example and if you see the attributes in the geometry spreadsheet you will see how state and time all start appropriately but time_start remains running even after state changes. i@state = 0; f@time_start = 0; if (dist < outRadius && @state == 0 ) { @time_start = @Time; @state = 1; } timer.hiplc
×
×
  • Create New...