Announcement

Collapse
No announcement yet.

Ocean Mesh and PhoenixFDOceanTex

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

  • Ocean Mesh and PhoenixFDOceanTex

    Greetings,

    Testing latest nightly build 1606266837 with Max 2017 and Vray 3.40.02.
    It looks like the edge of the Ocean Mesh is very close to the edge of the camera frame. On occasion the Ocean Mesh edge is just short of the frame and background is made visible.
    Then add PhoenixFDOceanTex, and the edge of the mesh is pulled into the frame. How far it is pulled in seems to be related to the wave height at that particular time.
    See attached pictures.
    Is there a way I can increase the amount of the Ocean Mesh overlap to keep this from happening?
    I saw the same thing on previous nightlies and tried testing the newest version before posting this issue.

    Thanks!
    Ron Porter
    Attached Files

  • #2
    can you test the same scene with old build? there is a system that tests the displacement shift and produces verices outside the frustum until there are no holes. it's possible that the system is broken, or your scene may be hitting a special case that is not covered.
    if the first one is the case, the old builds should have no hole
    ______________________________________________
    VRScans developer

    Comment


    • #3
      It would actually be best if you could send the scene to support so we can investigate the issue.

      Is that a Physical camera you use? If so, most likely it is the cause of the issue.
      Svetlin Nikolov, Ex Phoenix team lead

      Comment


      • #4
        Here is a scene file and first rendered frame, where the ocean mesh is tearing into the frame a bit.
        Hope this is helpful.
        Ron

        Edit: Noticed that after rendering a frame with Physical camera, the edges pulled into the frame even farther.
        Attached Files
        Last edited by rporter8555; 27-06-2016, 05:54 PM.

        Comment


        • #5
          Thank you! Will check it and see what the problem is.
          Svetlin Nikolov, Ex Phoenix team lead

          Comment


          • #6
            Alright, so the issue is new - you could workaround it by reverting to a build from Jun 23 or older until the fix is ready. Will keep you posted.

            Cheers!
            Svetlin Nikolov, Ex Phoenix team lead

            Comment


            • #7
              Thank you for the rapid reply! I will do that.
              You guys are the best.

              Ron

              Comment


              • #8
                Nah, we're just guys making bugs The fix will be in tomorrow's nightly.

                Thanks for finding this!
                Svetlin Nikolov, Ex Phoenix team lead

                Comment


                • #9
                  Looks like you smashed the bug. Thanks Svetlin!

                  Comment

                  Working...
                  X