Jump to content

michaelb-01

Members
  • Content count

    144
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    1

michaelb-01 last won the day on January 5 2015

michaelb-01 had the most liked content!

Community Reputation

15 Good

About michaelb-01

  • Rank
    Initiate

Personal Information

  • Name
    Michael
  • Location
    United Kingdom

Recent Profile Visitors

3,534 profile views
  1. Transform packed fragments at render time

    I never did unfortunately.. Let me know if you do!
  2. I am working on a big destruction job and I’m trying to optimise our workflow as much as possible. my usual workflow: - cache a single frame of my fractured geo as packed fragments - import rbd sim and create point per rbd piece (dop import) then lighting would import these two caches and use transform pieces. This works well since we only cache a single frame of the fractured geo, and the cache for the rbd points is very small. however the geo is still written into the ifd file every frame, which can be quite large. So, is it possible to specify the geo needed for the whole sequence and then have mantra transform the geo at render time (the same as transform pieces). This would make the ifd’s tiny an alternative method is to write each fractured piece out as a separate file then copy empty packed disk primitves to the rbd points then use the unexpandfilename intrinsic to expand it at render time. This makes tiny and fast ifd files which is great but seems quite slow to render - probably because it has to pull so many files from disk (1000s of pieces).. is it possible to do the render time transform pieces approach or does anybody have a better method? (The two I’ve mentioned are fine I’m just trying to optimise it!)
  3. Get full path to paneTab

    Sorry I thought pane.pwd() was just returning a string but I think its actually the hou.node so I can just do hou.pwd().path()
  4. Get full path to paneTab

    I'm trying to get the full path to the parent node in the current paneTab under the users mouse. I'm currently doing the following to return the paneTab: pane = hou.ui.paneTabUnderCursor() I can get the current parent node with: pane.pwd() So if i'm in /obj/geo1/subnet1 this will return subnet1 but how do I get the full path? (/obj/geo1/subnet1)
  5. I'm trying to add pop forces to ragdolls so they flail their limbs a bit however my pop force seems to have no effect (though gravity does..). I've attached a simple scene falling_mlb_v001.hiplc
  6. Speed up Mantra IPR

    Unified noise seems to be much worse than a turbulent noise. When rendering a unified noise the scene takes 3 or 4 seconds to generate, however with turbulent noise its milliseconds. Obviously unified noise is a much more complex noise but i'm surprised its that slow..
  7. Speed up Mantra IPR

    I'm having the same issue. Usually I render in Arnold and i'm used to very fast start and refresh times. I'm developing my material at the top level (in /mat) then i'm going to collapse it into a material later. This way I can drag shading nodes directly onto geo in the ipr and it will make me a temporary material and render just that shading node - this doesn't seem to work if you are inside a material builder.. So i've isolate a small patch of my geometry, i'm rendering a very small region of the IPR and i'm rendering a unified noise just to tweak the parameters, but every time I make a change on the noise it re-generates the scene which takes a few seconds. It makes look dev very painful... Anyway to prevent mantra from re-generating the scene (only refresh the materials..?)
  8. Ocean - no displacement with Deadline

    Probably a stupid question but i'm not a mantra user... I'm currently rendering an ocean in Mantra on our farm with Deadline. I've written out the ocean spectra, foam etc and everything renders correctly on my box. I'm then submitting an IFD generation job and a mantra job (frame dependent on the IFDs) however it renders without any displacement on the ocean...
  9. Show curve thickness in viewport

    Perfect, thanks all!
  10. Houdini's hairgen node displays the hair polygon lines with thickness defined by the width point attribute. How can I visualise this in the viewport on normal curves/polygon lines?
  11. Flip Splash - Grid Scale Optimisation

    I'm doing a flip sim of a splash. My particle separation is 0.006 which produces 14mil particles so pretty low. However because its quite a big splash the bounding box of the sim gets quite large so by the end of the sim I have 600mil voxels in the surface volume and 115mil voxels in the vel volume. So this is crashing my machine (which has 128GB ram)... My grid scale is the default of 2 but the vast majority of those voxels will be wasted since there are no particles in most of the bounding box. Is there any way to optimise this? The obvious way would be to use sparse volumes in dynamics instead of Houdini's native volumes but I imagine that would be creating a flip solver from scratch.. Or can I increase the grid scale without it negatively affecting the sim too much (i'm going to test this now..) I've attached a flip book of the sim https://drive.google.com/open?id=1k3Kexf-DJ5_ULPLt6dpsfx5f9LtW2OVz
  12. Default autosave

    I'm trying to set this up for the whole studio, I have it working in my 456.py with: hou.hscript('autosave on') But autosave defaults to save every 1 minute, how can I change this (through the 456.py or some other method) to every 10 minutes for example? I can't find anything relevant in hscript or hou..
  13. FLIP Viscosity - Collision object grid stepping artifacts

    Hey Dave, I know this is quite old now but I've had problems with collisions when using viscosity in the past too. I've found I need to increase the exterior band voxels on my collision vdb to greater or equal than the surface extrapolation on the flip solver (default of 0.5). I wonder if this could fix your problem too?
  14. Grains cloth - bend resistance

    Thanks for your reply Jamie. Yes thats similar to what I had in mind but would be a fair amount of work.. Obviously cloth does all this but its much much slower and I always revert to nCloth instead.. But when you have very high res cloth geometry and collision meshes (especially animated) Houdini's cloth is too slow and nCloth can't handle that amount of geo so i've been looking for workarounds. I had thought of adding another layer of grains but not ideal as it will slow it down a lot and there is not much control..
  15. Grains cloth - bend resistance

    Hi Chris, That makes sense, I suppose thats the best approach for getting bend resistance with grains, thanks for looking into it!
×