Jump to content

anicg

Members
  • Content count

    180
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by anicg


  1. I've started learning, trying to remember its name, yes MentalRay, with Maya, Before I'm done there was Arnold, stoped MentalRay, started a bit in Arnold with Maya (started on Renderman as well)), then I moved to Houdini and found Mantra, started on Mantra, then I see people using Redshift, they say it's way faster. Now I can confidently say I do not know how to use one single rendered properly, I've been jumping from one to another, like following fashion.

    Before I jump to Redshift, not knowing enough about Mantra or any other renderer (Oh by the way, Mantra will go away, there is Karma coming), I'd like to know if it makes any sense at all for a laptop user with only one video card: Nvidia (GeForce GTX 675MX, 4GB)?

     


  2. is it just adding the extension .sim instead of .bgeo.sc inthe file name? And most importantly does it know where it stopped or do I need to know where it stopped. Why am I asking this question? I've used E-on Vue, and there is a resume render button, you don't care where it has stopped because it knows where it has stopped, you just click one button. So for Houdini, do I need to go to the folder where the sim saved, check the last file number (frame number) and make note of the next one, type it in the file cache starting frame and then press "save to disk in background". In short: Does houdini know where it stopped or does it need me to type it?


  3. Thank you. I've fixed that part you showed. But for the "going crazy" part of the flip simulation, that can't be due to the fact that it's moving very fast, because it's moving very fast in both cases (with and without collision).

    Without collision, the fluid looks very smooth, yes there is a lot of movement but it looks calm. However with collision, the fluid is shooting up in the air, there are particles shooting all over the place, the same set up just added the collision. Here is a second version of the flip books and a hip file attached (after correcting what you've highlighted):

    Without collision v2:

    https://streamable.com/m2mpq 

    With collision v2:

    https://streamable.com/v4cs5

    I have the same problem in another simulation (rbd) as well. Is there something wrong in the collision? I'm dong this for the first time, I must be doing something wrong.

    all over the place.PNG

    all over the place 2.PNG

    Very calm.PNG

    Issue with FLIP simulation v2.hiplc


  4. I (beginner in FLIP Fluid) have a FLIP simulation that gets crazy when I add a collision (static object)

    I use the test geometry shaderball, used 2 spheres with mountain sop, boolean with front and back of the shaderball. The two deformed spheres are the source. The rest (boolean difference) of the shaderball is the collision.

    Flipbook Without collision

    https://streamable.com/qkh2p

    Flipbook With collision

    https://streamable.com/922a6

    Ii feel it has something to do with possible intersection between particles and collision geo, so I reduced the size of the sphere to leave a gap with the collision geo but the flip sim is still going crazy.

    Any idea?

    Issue with FLIP simulation.hiplc

    shaderball.PNG


  5. Thanks.

    I think the colour thief creates a colour palete. But the main point is to have Houdini ramp parameter populated by these colours. 

    Making a colour palette is dead easy, it can be done in color.adobe.com, or even faster in Davinci resolve. It’s not about the colour palette, it’s about populating the ramp parameter in Houdini, and being able to change one’s mind and repopulate it within a couple of seconds with another palette.

    If i use 7 colours (sometimes it can be 34 or more) i don’t want to waste time selecting each triangle in the ramp, click on the colour picker set one colour, and repeat it again, and again and again even of I’m selecting from a colour palette.

    i don’t know python, and i don’t think i will learn it fast enough to code this myself.


  6. Houdini, the mother of proceduralism, expects colour values to be set manually in the ramp parameter. Right?

    i came across a feature in substance designer in gradient map called “pick gradient” that samples colour values from any part of an image you select with colour picker and it automatically populates the ramp/gradient with all the values it found. It gives a rich ramp. Don’t like the ramp values? Just click a different area, you get a different ramp (colours). Like the colours but not the ramp distribution? Just move a few colours around. This is procedural.

    is there in Houdini (rightfully expected from a procedural software) a way to do something similar? At least not create colour by colour.


  7. After voronoi fracture, each piece has a name and can be coloured differently based on the name (color node, random from attribute: name).

    After the vdb, and vdb convert to polygon, the name is still there but not for every piece, it’s one name one colour for the whole thing, all the pieces get the same colour.

    how do i “smuggle” the name attribute through vdb and still get it after i convert vdb to polygon?


  8. To be able to use bake by mesh name in Substance Painter, I need to prepare the model in Houdini by giving names to subparts for both high and low resolution mesh, as he explains in the first 2 minutes in video below. How do I create named subparts in Houdini, it doesn't work with groups, (he shows it for Maya, e.g. top_high, top_low)

     

     

×