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.]]

Everything posted by k2p8

  1. copying Matrix

    primintrinsic transform is a matrix3. You binded it as a matrix which is matrix4 in houdini by default. Just write matrix3 m3 = primintrinsic(1, "transform", pt); instead of matrix m3 = primintrinsic(1, "transform", pt);
  2. Load sequences with TOPs

    Hi all :), I am trying to load two sequences of vdbs on my disk, for example : cluster0.$F4.vdb cluster1.$F4.vdb with a geometry import in a top network but it does not work so far. I have tryed to load them with the filerange / filepattern node and partition them into 2 work items, cluster0 and cluster1, but i got all frames at once or nothing in the geometry import. I also tryed to create a @path attribut with a $F4 but the top network does not seem to update the frames so i only have the first frame of each cluster.
  3. Pop orbit object [Tutorial]

    Hi all ! I did a simple vex scene with particules orbiting an object. The main challenge is to avoid particules to exit their orbit by computing an vector that correct their distance to the surface object from an iso value. Hope you like it. Update : Added the gradient of geodesic distance as axis of rotation for the particules. Usefull if you want to rotate along each element of a geometry, like arms, legs, tentacles, etc. pop_orbit_001_odforce.hiplc
  4. attribute weighting for pop advect by volumes

    If you unlock the popadvect node you will find a popvop inside. You can acces inputs in there and modify the popvop to match your desired effect.
  5. Volume Slice to Texture

    There is a game tool that does it. You can bake/render slice of your volume. It works for any kind of data on your volume. https://www.sidefx.com/tutorials/channel-packing-pyro-data-using-the-texture-sheets-rop/?collection=50
  6. Hi folks ! A tutorial about recursive backtracker in vex to create mazes. The idea is simple : You get your adjacent neighbours and check if they are not visited, if not, you randomly choose one and move to it. If no valid neighbours, you backtrack the stack of your previous positions and check if there is a valid neighbour until you find one. If the stack is empty no valid cells are left so the maze is done. recursive_backtracking_001.hiplc
  7. Hi folks ! I am cooking a pdg network, simple setup. I just split a cache by a @cluster attribut to save each cluster independantly and run a pdg over that. But i randomly have an error i don't understand : '__pdg_preframe' is invalid or already exists' Do someone know what does it mean ?
  8. generate to fill up wire curves in tube meshes

    May be you can compute a vector field with a direction along the tube and some noises to create point trails procedural_roots_000.hiplc
  9. Hi all I am posting a simple procedural desintegration that is very fun to build, as always, with quaternions and vex. Vex is annoted, Hope you will like it. There is a line in vex where i remap a random quaternion [0, 1] to [-0.7, 0.7]. It roughly removes the random overlapped orientations. If you disable it you can see that orientations are a bit biased because of the 0 - 1 range. Update : Now with RBDs lego_desintegration_RBD_001.hiplc
  10. Hi folks ! Is ACEScg rendering usefull for volume rendering ? I was reading more about ACEScg in general (still abstract for me at this point) : https://chrisbrejon.com/cg-cinematography/chapter-1-5-academy-color-encoding-system-aces/ And it seems, from the article, to give good results in color saturation and GI so i am planning to implement aces in htoa to do some tests. Have you guys already tested ACEScg in houdini, especially for volumes ?
  11. Directionally orient grid

    if you are a fan of quaternions and matrices you can do a spherical interpolation (slerp) of 2 quaternions which represent the local orient of the leaf and the global orientation to the sun orient_leaf.hiplc
  12. Hi @eunchae, The basic principle of an upres is to make a new simulation with a pre-existing velocity grid that you use to drive a new dye (density / temperature). Your new simulation should have smaller voxels and parameters close to the lowres (like temperature diffusion, flame amount, time step) if you want this new version to be close to the lowres. You then copy the lowres velocity and simply advect the upres by it. This way you only perform heavy computation like divergent free velocity (ensure the conservation of the mass of the fluid) and the boundary collision on the lowres, the upres solver only has an advect for the density / temperature / ect. all other nodes relative to velocity enforcement / computation are deseabled which allow you to quiclky compute the upres and skip all the heavy parts. Then you can add a little amount of noise with an add operation to the copyed lowres velocity to give more details to your upres. This small amount is almost divergent free on a large scale so it should not be a problem. You can add any forces at this process in the upres, but, the divergent free velocity node being desabled, only already divergent free forces should be added. Otherwise your smoke will compress into itself. And you should only add forces that do not push your upres smoke to far from the lowres, since you simply copy the lowres velocity, no new velocity will be computed outside of this bounds. So, for example, adding a wind, which is divergent free, is not a good option since your smoke will crash into the bounds of the lowres. There is some parameters that do not scale well with the upres, usually it is all parameters or operations that need neighbours voxels to be performed, like temperature diffusion. Since you change the size of the voxels, those operations have an overall result which is generaly not the same as the lowres. You could correct that by sampling the lowres version of the simulation and modify the output value, but you lose a lot of details by doing so. So in this case, it is better to slightly twik the upres simulation to perform better, by increasing or reducing the corresponding parameters.
  13. ACES Rendering output

    ACES pipeline is sometimes applying slight tone mapping before the output which they call RRT (Reference Rendering Transform), and then, your output transform sRGB / Rec.709 is applyed. So you can have slightly different outputs if you are using Utility - sRGB - Texture or output_sRGB or Output - sRGB. I don't know exactly all the slight differences between all those transforms but i dont think sRGB - Texture is a usefull transform to export your pictures. This is in the Arnold ROP. You must choose your render color space (Properties > Device > Color management ) and render output (Properties > Output > Color Space) in the Arnold Rop to know which color space is used. Theoricly if you want to use ACEScg it should be ACES : ACEScg for the render engine and a linear sRGB / ACEScg for the output then you will need to convert this linear ACEScg/sRGB to an sRGB space with an gamma 2.2 or sRGB / Rec.709 transfert function applyed to be able to display the picture on a sRGB Monitor. If you want some docs about ACES there is this articles which is a good start and the ACEScentral forum : https://chrisbrejon.com/cg-cinematography/chapter-1-5-academy-color-encoding-system-aces/ https://community.acescentral.com/ PS : And Of course you must install OCIO to manage all those color spaces / transform PS2 : If you are using Arnold be sure to convert your tx and houdini color node to the correct space. If you are using ACEScg and you generate TX textures they will have a ACEScg space applyed so you can't use them for sRGB anymore and the opposite is true too. Same thing for color node in houdini, if you enter a (1,0,0) it will be for sRGB so you need to convert your color node to an ACEScg with an OCIO transform other wise you are not sending the correct color to Arnold.
  14. Bullet and Constraints learning ressources?

    if you want to know more about bullet constraints themselves there is Tokeru website : https://www.tokeru.com/cgwiki/index.php?title=ConstraintNetworks he explains in details attributs on prim / points with examples
  15. Sparse Pyro Upres H18

    @Atom What does it means 'in other DDC packages' ? If you want to match a pyro look to an other pyro you can look at the volvis_ attributs created by the post process of the pyro. You will need density / flame / temperature fields and the values of the ambiant / reference temperatures in kelvin of the pyro solver. If you match all those values you should have an identical result. If you re importing smokes simulations from an other software you might need to fitrange / scale the fields first i think.
  16. Sparse Pyro Upres H18

    Hi everyone ! I have been working on a sparse pyro upres recently and did a video to test it. You can find the hda here : https://drive.google.com/drive/folders/1H4Y0HNELDJ6lmHsM43eEI_lRgNuCEaxX?usp=sharing More details about the solver : The sparse upres solver is a deeply modified sparse pyro that allow the user to quickly upres a smoke simulation from simple inputs. The core idea for the upres is to bypass every nodes related to velocity update in the smoke solver, like the project non divergent, vel advection, collision mask, ect. and replace the upres vel field by a copy of the low resolution velocity. One can then advect any dyes needed through that vel field to create an upres. In order to keep the pipeline as simple as possible i splitted the process in 2 nodes, a 'configure_inputs' which precompute some lowres fields and normalize inputs and the upres solver itself. The sparse solver needs to match the parameters of the lowres simulation to work properly (like dissipation, flame amount, temperature diffusion, ect.). To quickly set up the upres solver i added a python script, that copy and paste all relevant parameters of a lowres pyro to the upres solver. You just need to select which pyro solver to use as reference to match the parameters. The sparse solver itself has some simples parameters like noise / random that allow the user to inject details in the lowres vel field. Noises and randomness are stored on an separated field, 'noise', to be conserved through time since vel is simply copied from the lowres. That allow the noise field to be advected by the vel and then merge with it to advect other fields like density, flames, ect. Which create a more complex pattern than a noise directly merge with the vel. Color can be added at the upres stage if the source contains a Cd and Alpha volumes. Those fields will simply be advected by the upres solver like any other fields resulting in a colored smoke. Your lowres simulation needs no color. Retime can be perform by interpolating the source and scaling parts of the upres solver. The process is automated from a tab in the sparse solver. However, it can vary if you animate the retime or set it to low (especially with flame). The upres solver does not need any modification of the velocity other than small disturbance / turbulance details. If you add strong changes in the vel field your upres dye will deviate far away from the lowres vel field. Every major modifications of the vel field like wind or buoyancy need to be added in the lowres simulation. A fake divergence can be added through the process by computing the negative gradient of the density added to the velocity. Since pressure projection has been bypassed, important amount of this 'divergence' will result in compression in the vel field creating artefacts in the smoke. However, it can be usefull to break the sharp edges of an upres smoke if needed. At last, one can force the upres to match the lowres fields by simply removing parts of the simulation which are outside the lowres smoke by taking the lowres density field as reference. If the lowres is below a threshold value, the upres smoke is multiply by amount less than 1. This can be usefull is you have strong noises and need to dissipate them to stay in the bounds of the lowres.
  17. Sparse Pyro Upres H18

    Yes my bad, i tought it could be a nice idea to post the solver here since it s finished now :V
  18. Sparse Pyro Upres H18

    Hi @Noobini, i have a AMD Ryzen Threadripper 1950x (16cores) 3.40GHz, 64GB ram with windows 10, 64bits
  19. You're welcome I updated a bit the solver and did a video to test it here is the link with the updated solver (it's the same as the previous one) https://drive.google.com/drive/folders/1H4Y0HNELDJ6lmHsM43eEI_lRgNuCEaxX?usp=sharing
  20. Hi folks, I am actually coding some basic operators like divergence, gradient in vex and python to demistify them and wanted to share the file with you. Feel free to update or correct the file since i might not be sure of some operators. it contains : - Divergence (voxel and points) - Gradient (voxel and points) - Curl (voxel) : the curl seems to not have the same order as vdb curl so still in wip - Laplacian (voxel) : The computed laplacian is somehow less precise than vdb laplacian - Covariance matrix and eigen vectors (points) : It works but the scale is normalize - Laplacian matrix of a mesh (python) - Bernstein polynomials basic_operators_001.hiplc
  21. Expand Vel Field ( don't want use divergence )

    You may try to tweak the gasresizefluiddynamic. If you dive in, you ll find a sopsolver with ResizeBounds data. Inside merge a bound of your velfield from sop with the out node (don't forget to tag the merge node as display). It some sort of a minimum of the 2 bounds so your sim will expand of the vel field at the next frame.
  22. Each x th iteration

    you can try a modulo (%) to execute instructions every x iterations if your variable is an integer like : if(integer%30 == 0, 1, 0) in that case it will execute instruction every 30 iterations
  23. Gas turbulence to not affect near emitter

    by default the gas resize only resize legacy field of the pyro solver like density, temperature. If you are adding a personnal field you need to tell houdini to resize it as well. Either it will be a 1x1x1 cube. The +1 frame starts to resize the sim after the sourcing. So you source first then you resize. Either your fields will collapse because there is no density in the simulation.
  24. Gas turbulence to not affect near emitter

    hi, i checked your file. Uncheck track by object it will expand to much your domain then u can add your field as you did. It s better to work at sop level for this kind of smoke by putting your dop object directly in your object rather than outside. Also you need to set a size and center for your smoke object to initialize it. controlField_v002.hiplc
  25. Hi folks ! I am working on a sparse pyro upres on my 'sparse' time (lol). I tryed to automate as much as possible the process by normalizing inputs and coding a python script that copy and paste all the params of the lowres simulation to the upres node. So the only thing to work with after matching params from the script is the noise / dissipation of the upres. I added a hip with hda in the link. The hip is annoted to guide you through the process. https://drive.google.com/drive/folders/1H4Y0HNELDJ6lmHsM43eEI_lRgNuCEaxX?usp=sharing the pipeline is fairly simple : 1. add a configure input node, it will merge all inputs from low res sim and source to normalize and rename fields 2. add the sparse pyro upres node 3. In the tab match properties of the upres node drag the lowres pyro and click match properties 4. enjoy The sparse solver itself is a deeply modified sparse pyro where you basicly cancel all nodes relatives to vel advection / projection and import the vel from the lowres in copy mode. Then you can add your sources (without the vel or v sourcing since it has already been calculated in the lowres) and add some noise. Since vel is in copy your noise won't last in the sim so i created a noise channel in the smoke object that is advected by the vel and merge to the vel. You can also simulate your low res without color and add color to your upres source and simulate an upres with color, it only needs a Cd and Alpha channel.