Announcement

Collapse
No announcement yet.

Demo Limitations

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

  • Demo Limitations

    Hello,

    I'm trying to understand the demo limitations and how they apply to what I'm trying to do.

    *******
    Phoenix FD for 3DS Max Demo Limitations
    - Simulations are restricted to 2 000 000 cells per grid
    - Maximum 10 000 particles for foam and splashes
    - Warning on every 30 sec
    ******

    I want to create a single ocean image at about 4096x3277 for around 11x14 output.
    - What are "cells per grid"? Right now my grid is 50000m x 50000m with 1000 Length and 1000 Width segments for a total of 2 000 000 faces. Is that the same thing?
    - I'm don't know how you do foam or splashes, so I think I'm okay there
    - I'm not animating, so I wouldn't expect any sort of warning.

    Is the size that I'm trying to create within the parameters of the 2016 max demo?

    Also, when I try a render using DBR, I can see there there is variation between my workstation and the render node for each bucket so there are noticeable squares (buckets) in the ocean texture. Is DBR not possible? I'm not able to attach anything in this forum to show you what I mean
    David Anderson
    www.DavidAnderson.tv

    Software:
    Windows 10 Pro
    3ds Max 2024.2.1 Update
    V-Ray GPU 6 Update 2.1


    Hardware:
    Puget Systems
    TRX40 EATX
    AMD Ryzen Threadripper 3970X 32-Core 3.69GHz
    2X NVIDIA GeForce RTX 3090
    128GB RAM

  • #2
    - the cells are not directly corresponding to the physical size, in the grid panel you have info "Total cells:..." that shows the cell count, if this number is above 2 000 000, the simulation will refuse to start.
    - the foam/splash particles are produced in the simulation, but you can use any particle system and render it as foam, for example you can use particle flow
    - the warning is during the simulation, if you just render static ocean surface with no simulation this warning will not appear.
    as i understand you need just ocean surface without simulation, right? you can use a small dummy simulator, simulate few frames and render it in ocean mode, or use a plane displaced by the vray displacement modifier.
    about the distributed rendering can you show the image? can't say nothing for now
    ______________________________________________
    VRScans developer

    Comment


    • #3
      - I using a plane displaced by vray displacement modifier. How do I see what the total cells of the grid panel is? I have statistics turned on but don't see anything that says "cells".
      - I don't have permission to post any attachments in the Phoenix forums. Perhaps its because I don't own the product?

      I've uploaded the image here.
      David Anderson
      www.DavidAnderson.tv

      Software:
      Windows 10 Pro
      3ds Max 2024.2.1 Update
      V-Ray GPU 6 Update 2.1


      Hardware:
      Puget Systems
      TRX40 EATX
      AMD Ryzen Threadripper 3970X 32-Core 3.69GHz
      2X NVIDIA GeForce RTX 3090
      128GB RAM

      Comment


      • #4
        you have no simulator at all, you are not affected in any way by the demo restrictions
        about the dr issue, not sure what it can be. few days ago we caught a similar bug, it's quite possible to be the same, but i'm a bit skeptical, the bug was quite specific.
        do you have equal phoenix versions installed on the machines?
        how many dr stations you have? can you share some system info about them, the most important the cpu type
        ______________________________________________
        VRScans developer

        Comment


        • #5
          You might be on to something with cpu type

          I have max 2016 / VR 3.2 on my workstation and two render nodes. The workstation is an AMD Phenom II x6 1090T and the two workstations each have an i7-3930K.

          If I run DBR from the workstation to have all three working on the scene, I get the box issue. But if I pass the scene off to BB for only the two nodes to work on, it doesn't happen. So I suspect there's an issue with mixing AMD and Intel?
          David Anderson
          www.DavidAnderson.tv

          Software:
          Windows 10 Pro
          3ds Max 2024.2.1 Update
          V-Ray GPU 6 Update 2.1


          Hardware:
          Puget Systems
          TRX40 EATX
          AMD Ryzen Threadripper 3970X 32-Core 3.69GHz
          2X NVIDIA GeForce RTX 3090
          128GB RAM

          Comment


          • #6
            I meant that the each node is running an i7-3930K. Not sure why I'm not allowed to edit my posts in this group.
            David Anderson
            www.DavidAnderson.tv

            Software:
            Windows 10 Pro
            3ds Max 2024.2.1 Update
            V-Ray GPU 6 Update 2.1


            Hardware:
            Puget Systems
            TRX40 EATX
            AMD Ryzen Threadripper 3970X 32-Core 3.69GHz
            2X NVIDIA GeForce RTX 3090
            128GB RAM

            Comment


            • #7
              well, this makes very plausible that the above mentioned bug is causing the issue, we observed it as difference between 32 and 64 bit processors, but it's quite possible that it appears when mixing intel and amd, almost 100% sure that it's the same bug.
              ______________________________________________
              VRScans developer

              Comment


              • #8
                This could be caused by the Embree feature being on. Embree, as far as I'm aware is only used for intel CPU's and does not support AMD so this might be causing the discrepancy you see in your renders.

                Comment


                • #9
                  Originally posted by chadstevens View Post
                  This could be caused by the Embree feature being on. Embree, as far as I'm aware is only used for intel CPU's and does not support AMD so this might be causing the discrepancy you see in your renders.
                  I'm not really sure that Embree has anything to do with it; it does work on AMD CPUs though.

                  Best regards,
                  Vlado
                  I only act like I know everything, Rogers.

                  Comment


                  • #10
                    Originally posted by vlado View Post
                    I'm not really sure that Embree has anything to do with it; it does work on AMD CPUs though.

                    Best regards,
                    Vlado
                    Are you saying that Vray supports AMD ( Which of course it does ) OR that it now supports Embree for AMD?

                    Cheers.

                    Comment


                    • #11
                      Originally posted by chadstevens View Post
                      Are you saying that Vray supports AMD ( Which of course it does ) OR that it now supports Embree for AMD?
                      Embree has been working on AMD machines for a few service packs now.

                      Best regards,
                      Vlado
                      I only act like I know everything, Rogers.

                      Comment


                      • #12
                        Originally posted by vlado View Post
                        Embree has been working on AMD machines for a few service packs now.

                        Best regards,
                        Vlado
                        Oh wow, Did not know that. That's Excellent.

                        Cheers.

                        Comment

                        Working...
                        X