Announcement

Collapse
No announcement yet.

scaling problems between CM and M

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • scaling problems between CM and M

    I simmed a load of stuff in scenes with CM as system units but the main scene files we are assembling in are in M so when it gets bought in its all out of whack.
    any ideas how to get around this?

    alternatively what is the best way to cache full fluid sims with foam and splash intact? In the past I have done PRT for fluid stuff and that worked fine for fluid but didnt try with foam and splash, which I assume would require a resim to get particle age and scale...

  • #2
    Hey,

    If you are not simulating anymore, it's not a problem to just scale the container.

    Not sure I understand the second question correctly, but there's no reason to resim for extra particle channels - the PRT export will let you output exactly what you have in your AUR caches.

    Cheers!
    Svetlin Nikolov, Ex Phoenix team lead

    Comment


    • #3
      Ah thanks, that seems to work fine with the foam and splashes as well.

      I was asking what the best format is to 'cache' out the full water sim with foam and splash and if there was a best way to do it in one export (mesh? vray proxy? alemebic?) for rendering as dragging around a large number of phoenix grids is slow.

      Comment


      • #4
        Ah, right now I wouldn't say there is a complete single-file solution apart from AUR caches. We gotta upgrade the VDB version to 5 so we can store both grid and particle data in VDBs. Abc, X-Mesh and V-Ray Proxies do not get the Phoenix velocity at the moment AFAIK, so you won't have moblur with them...
        Svetlin Nikolov, Ex Phoenix team lead

        Comment


        • #5
          OK thanks for the update Svetlin!

          Comment

          Working...
          X