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

0 Neutral

About cupoftea

  • Rank

Personal Information

  • Name
    Cup of

Recent Profile Visitors

810 profile views
  1. transfer Cd with CopyToPoints

    ah. this clarifies things. thank you, much appreciated! still, final question. remains unclear: in above example of atom: color sop set to points, it IS working. in above example of my initial screenshot: Cd set to points, it is NOT working. so, both are technically the same. arent they?? (only diff is: Color SOP vs AttribRandomize SOP. both with Cd. both on points. one is working. one not?)
  2. transfer Cd with CopyToPoints

    true. and understood. hence my initial question: why is it then seeing pscale? whats the diff between an attribute like pscale (working) and Cd (not working). i expected both or none to be "visible"
  3. transfer Cd with CopyToPoints

    interesting. i actually had both of the "Attrib Randomize" SOPs to run over points. thanks anyway, Atom
  4. transfer Cd with CopyToPoints

    ok i see thanks. but why is pscale transferred and Cd not? should it not be possible to transfer any attrib to prim spheres (or points)?
  5. hello. anyone knows why when using CopyToPoints in "pack and instance" mode, Cd attrib is being transferred to PolySpheres but not to PimitiveSpheres? whereas pscale for example is always transferred?
  6. hello , running houdini 19.0.383 on linux i cant open the shell from Menu -> Windows -> Shell it simply does nothing. does anyone know how to solve this?
  7. hello i have a working pyro sim. i want to grab the fuel field to scatter points in there. i managed to use a SOPSolver inside the dopnet, and scatter points where density (volumewrangle binds to density by default) is. but how to scatter to only where fuel is? so, the main question is: how can i grab the fuel field (without binding it to density)? the scatter SOP uses density to scatter. couldnt figure out to tell it to use fuel instead. thanks a bunch
  8. is there any general guideline/rules of what kind of tasks or operations are (mostly) multithreaded and what are not?
  9. gasbuildrelationshipmask microsolver

    thx again, Alejandro can you give a practical example of what you would use it for? just an example for me (still houdini new) to understand what you would use it for? thank you
  10. gasbuildrelationshipmask microsolver

    or let me ask differently: i checked your file and think i understand, but since it is "static" (non-simulatued, since no solver), i have no idea what would it look like when simulated? thanks a lot again
  11. gasbuildrelationshipmask microsolver

    thanks again Pazuzu. so that means in this case: the (green) sphere acts as a mask for the smoke? correct?
  12. gasbuildrelationshipmask microsolver

    great such detail explanation from you as always Thank you. i checked the file. looking at the green "source relationship" nodes and reading the documentation, merge says "affected (right) will use affectors (left) for creating density". so the smokeobject (right input) uses green sphere object (left input) as a density source, and the green "gasbuildrealtionshipmask__source" node is a mask? right? if right, what object or field does the "gasbuildrealtionshipmask__source" use as a mask? it says "mask field source" and "reference field density". but how can the source at the same time be the source for density and mask for density? no? thank you again
  13. hello. i am trying to understand the "gasbuildrelationshipmask" DOP-microsolver. i read the documentation multiple times but i still cant figure out what it is doing or at least what can be done with it exactly. as far as i understood it (can) go in conjunction with the source relationship DOP but also here, dont know how to use it ecxactly. thanks in advance!
  14. when to set P or velocity or force explicitly?

    thanx for answer. but isnt force the same as acceleration, yes? that means that when you set force explicitly, the particles keep increasing their speed constantly, right? so they get faster and faster (like gravtiation force for example), no? dont you think that therefore force is harder to control than v? thx
  15. hey guys, as an ex-3dsMax user, i have a decent knowledge of maths/vectors/integrations. but being new to houdini, when doing POPVOPs, i often dont know when to explicitly set P or v or force. i understand that force is integrated to v and that to P. but then i see other forum hip files where people set P or set force (in VOPs). and i dont know why? so when do i set v, and when P or force? are there special rules? thx