Announcement

Collapse
No announcement yet.

Foam Shader Rendering in Standalone Even When Turned Off in Max

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

  • Foam Shader Rendering in Standalone Even When Turned Off in Max

    I suppose this could have to do with vrscene export as well, but I was running into an issue where with a particular scene a Foam Shader was rendering foam particles even when the little Eye was turned off. I finally deleted the shader and it stopped rendering. It renders fine in Max, but not in Standalone... Same versions.

    I am collecting a scene send it via a support ticket (it's private), linking to this posting.

  • #2
    OK. Submitted the scene file under the ticket 95454

    Load that scene up. You may have to relink the textures (there is HDRI lighting). I probably could have gotten away without sending you those, but I don't know what is causing the issue.

    Relink the .aur files to the Phoenix node. There is a frame offset; so the three aur frames I sent actually correspond to 85, 86, 87 in the file.

    Then render frame 85 or 86 using standalone. I saw the issue with exporting from the VRay Menu option, or exporting the vrscene using Deadline.

    You should see the particles render even though the foam shader is turned off in Max. (There is a render mask on- the frame is anamorphic as well. )

    Note Max 2023.
    VRay is vray_adv_60021_max2023_x64_31945
    PHX is phoenixFD_adv_51001_max2023_vray6_x64_31862

    Comment


    • #3
      Yess, got the scene, thank you!
      Svetlin Nikolov, Ex Phoenix team lead

      Comment


      • #4
        Cool! I assume the ticket system shows you the conversation I have been having with Tashko​.

        It seems to be related to the vrscene exporter and multimatte include/excludes. I have not tested yet, but disabling that was offered as a workaround. I think it was useless anyway, as I was not using geometry mode for the particle shader. (Even slower of course)

        I need to do some more testing, but that scene was taking about 12-24 hours per frame when rendering with Max via deadline. But when exported to standalone it was only 3-4 hours. But standalone was having some seemingly random big bubbles showing up that I had to paint out. I think those were likely this multimatte issue.

        I know in one version I had issues with a rising speed that was much too high causing all kinds of flickering and crazy motion blur above the water surface. I recognized this, and a resim seems to have fixed that. The schedule on this was insane, and there was no time to troubleshoot.

        Thanks.

        Comment


        • #5
          I am starting to look at this issue right now...
          Svetlin Nikolov, Ex Phoenix team lead

          Comment


          • #6
            Alrighty, caught it! As you guessed, it was in the V-Ray for 3ds Max vrscene exporter. Once the fix makes it into the V-Ray stable nightlies, I will ping you to get a latest V-Ray.

            Cheers!
            Svetlin Nikolov, Ex Phoenix team lead

            Comment


            • #7
              Thank you, and everyone there for figuring this out.

              Comment


              • #8
                Thank YOU for reporting this! The fix will be in tomorrow's V-Ray stable nightlies for 3ds Max here: https://nightlies.chaos.com/#/vrayma...ble/stable_6.1, in the 20230318 folder.

                Cheers and thanks again!
                Svetlin Nikolov, Ex Phoenix team lead

                Comment

                Working...
                X