Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


haggi last won the day on November 17 2016

haggi had the most liked content!

Community Reputation

26 Excellent

About haggi

  • Rank

Contact Methods

  • Website URL

Personal Information

  • Name

Recent Profile Visitors

3,672 profile views
  1. Happy 10th Birthday Od[force]

    Happy birthday. It is incredible how helpful the community here is. Thank you.
  2. You create a surface vdb which creates necessary data on the surface only by definition. But to simplify the process you could use a fluidSource sop which seems to fill the interior.
  3. Hi, during the work with my maya alembic reader, I discovered a problem with alembic files written by houdini. Obviously Houdini exports an additional point geometry together with my mesh. If I load the alembic in Maya, I get a mesh shape and a particle shape. In houdini I can see two packed objects in the alembic sop. This only happens in certain situations. e.g. if I create a box and deform it, only one packed object is created in the alebic export. Only if I export my flip mesh an additional packed point geometry is exported and I get a warning in the exporter: "Renaming node to /geo1/file3_1 to resolve collision". Does anyone know what's going on here? It seems not to be a new phenomenon, it happens the same way with H16.
  4. But it is helpful to keep in mind that 10 nodes in a vop can sometimes be replaced by one line of code. I just followed a Jeff Wagner flip fluid webinar where he combines some vop operators in a dop node and even if it is not very complicated, the network grows fast and most of the time you are moving the viewport to check where all the connections go. So with two lines of code I was able to do the same thing what results in a very much better overview and less nodes.
  5. Particles from Houdini to Maya

    Okay, did you really try it? In the source code you can see: data["bhclassic"]=readBGEO; What means, bhclassic should be handled as bgeo. But maybe the code on github is newer than the plugins.
  6. Particles from Houdini to Maya

    There is no need to rename it as begeo, partio should be able to read bhclassic directly.
  7. Continue simulation from a certain frame

    You are mixing two completely different things here. Usually you do a sim and save only the result of the sim without all additional sim data which is needed for simulation (e.g. collision geometry, additional fields). So your final simulation result contains (in your case) some fields like temperature, velocity, density etc. These can be saved in the dopIO as bgeo, bgeo.sc or other formats. If you want to continue a simulation you will have to save the .sim files out of your dop network (as much as I know) what happens during simulation. You cannot convert the result of a simulation into a .sim file, you will have to do the simulation again.
  8. Continue simulation from a certain frame

    To continue the simulation at a certain frame you need a sim file for this frame. Sim files can be exported from the dop network. I prefer to use a file node in the dop network to write sim files to disk. Then you can use the last sim file as inital state in the dop network - of course you will have to set the sim start to your new start frame.
  9. render EXR colorspace

    If you mean the RenderView tab in Houdini, you can see what it does by simply showing the ColorCorrection bar. There you can see which gamma is used to display the image, applying the same gamma in Nuke should result in the same image. And if you did not change the output gamma value in your mantra render node, the rendered image is linear (gamma of 1.0). BTW.: You should not change the gamma before compositing, but at the end and only set the view in Nuke to the appropriate settings. The result is a better quality in most cases.
  10. No, not really as much as I know. For Houdini I was able to find these commandline switches: houdini.16xxxx.exe /S /MainApp=Yes /InstallDir=whereeveryouwant /AcceptEula=yes /ApprenticeLicensing=No /DesktopIcon=No /FileAssociations=No /HoudiniServer=No /HQueueServer=No /EngineMaya=Yes /HQueueClient=Yes /IndustryFileAssociations=No /LicenseServer=No /Registry=No /StartMenu=whatnameever For the setup of a maya deployment you can use: Setup.exe /qb /i path_to_deployment\Img\Maya2018.ini /language en-US We then call a loop and check if setup.exe is still running and continue as soon as it has terminated.
  11. We use bat files to install all needed software. Because we need bat files anyway for starting Maya, because our maya is heavily customized, we extended the system to all programs we use. In the batch file it simply calls all needed other programs install bat files and finally start the application. Where needed Maya is installed from a deployment setup.exe. The install file of houdini can use a whole bunch of options as well. Other programs can be simply copied locally and work fine. This procedure works really fine, at least on Win7. We added an archive of the software, simply packed everything in the programs folder. This way we can simply delete the local install directory in case we screwed someting up or files are lost (what indeed happens from time to time), and the archive is extracted locally and everything runs again. Drawbacks of this procedure is that you have to find a way to install everything with admin rights if you have limited user rights. Another small problem with this procedure is that you the Setup.exe of a Maya deployment does not block the execution of the bat file. So you will have to find a wait procedure until it is done. On the pro side: You do not need extra software, only the software which is actually needed is installed, it is easy to extend or add environment variables.
  12. So are you sure that renaming/removing the folder: C:/Users/tom/Documents/houdini16.0 does not help? At least here on my machine, it is recreated automatically.
  13. Need some advice about cloudfx

    Your cloud does not look bad. To be honest I'm not sure which cloud noise I use most, I simply play around until I get the result I want, or at least as close as possible.
  14. Need some advice about cloudfx

    I usually first build a simple geometry of the shape. Then I add a cloud sop node where you can set density and the shape like structures and finally I add a cloud noise sop which creates a very nice noise. Try to increase the amplitude and play around with element size. To answer your questions: Yes a cat shaped geometry as input should work fine. Do you have an example what you want to archive and why the built in clouds noises do not work for you?
  15. render EXR colorspace

    I suppose that's because the output gamma is 1.0. Mplay sets the gamma to 2.2 per default. Linear is usually the way to go and only change color space in compositing and final output.