Announcement

Collapse
No announcement yet.

PhoenixFD and Backburner problem

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

  • PhoenixFD and Backburner problem

    Hi guys, I write here because I do not have access to the PhoenixFD section problems. I have a problem with backburner and phoenixFD 3.04 in 3dsMax 2017. When I send the computer simulation to "Run just the simulation and do not render". I write the output path for each simulator and leave the exit path for the render as I indicated it would not render. However, computers on the network, after finishing the simulations, open the framebuffer at a resolution of 2x2 pixels and start the render. I can not understand how it can be. Has this happened to any of you? Thanks so much.

  • #2
    Hey,

    If you can't post in any of the forum sections, drop a mail to "Support at ChaosGroup dot com" and they will grant you access in case you have a full Phoenix license.

    The thing with Backburner is that it's designed to do renders and is not particularly customizable, so the Phoenix simulation runs as a render pre-process, and after it finishes, Backburner still has to render something - we've just minimized the time impact of the render by reducing the resolution and limiting the sequence to a single frame. What happens with your BB job is expected, but currently I am not sure how we could work around it in a different way without losing other functions of the submission.

    Cheers!
    Svetlin Nikolov, Ex Phoenix team lead

    Comment


    • #3
      Originally posted by Svetlin.Nikolov View Post
      Hey,

      If you can't post in any of the forum sections, drop a mail to "Support at ChaosGroup dot com" and they will grant you access in case you have a full Phoenix license.

      The thing with Backburner is that it's designed to do renders and is not particularly customizable, so the Phoenix simulation runs as a render pre-process, and after it finishes, Backburner still has to render something - we've just minimized the time impact of the render by reducing the resolution and limiting the sequence to a single frame. What happens with your BB job is expected, but currently I am not sure how we could work around it in a different way without losing other functions of the submission.

      Cheers!
      Thank you very much Svetin for your response and for dedicating your time.
      All the best for You.

      Comment


      • #4
        I have not tested BB-Simulation, but does it send frames for every backup-Intervall? So it could pick up the simulation if something happens of someone decides to use the mashine for rendering...
        Kind regards, Wolf S./K.
        www.faber-courtial.de

        Comment


        • #5
          Hey,

          It does not technically send frames - the simulating machine automatically saves Phoenix caches where the output directory is, like a regular Phoenix sim does, so if something stops the sim, the caches will be available for Restore.

          So you could resume simulations with Backburner as if you were simulating locally and you hit Restore

          Cheers!
          Svetlin Nikolov, Ex Phoenix team lead

          Comment

          Working...
          X