Announcement

Collapse
No announcement yet.

envFog - textures

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

  • envFog - textures

    So what am I missing? When I apply a 3d or 2d texture to the density of an envFog node, the fog doesn't render volumetrically... only the sides of the mesh (cube) render with fog affecting it's sides like a texture. No volume inside... This is unlike the examples in the 3dsmax envFog examples where 2d and 3d textures affected the volume of the fog, not just the sides. I'm sure I'm missing some toggle, or it's just not working yet, but I'd like to know

    Andrew
    Attached Files

  • #2
    Could be the mapping type set in the material. Is the mapping set to object xyz, instead of world xyz?
    Brendan Coyle | www.brendancoyle.com

    Comment


    • #3
      Yep, we have a bug there, the 3d textures will be computed only for the surface of the mesh. I noticed it a couple of days ago, but we still need to figure out how to fix it without breaking some other stuff. I'll write back here when it is fixed in the nightly builds.

      Greetings,
      Vladimir Nedev
      Vantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help

      Comment


      • #4
        Thanks, Glad I'm not insane Does that mean that an untextured fog (cube) is also only calculating the surface as well? That would explain some other odd renders I've been getting with envFog. It's just hard to tell visually unless the density is textured.

        Andrew

        Comment


        • #5
          The 3d texture sampling is fixed now for tomorrow's nightly build (2010-04-24). Have in mind that you won't achieve a volumetric effect when using a 2d texture ( like the texture checker in your screen-shot). You'll need to use a 3d texture like marble, leather, etc.

          The problem was specifically when sampling the 3d textures for the fog, so the fog should work ok if no textures are applied. You can post a screenshot and a scene if you still suspect a bug in that regard.

          Greetings,
          Vladimir Nedev
          Vantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help

          Comment


          • #6
            Awesome, I'll give it a try! Thanks for the specifics.

            Comment


            • #7
              yep its working! cool! been waiting for this.
              What about Mayas 3d textures, which is supported these days?
              I dont seem to get anything out of the cloud 3d texture for instance.

              Comment


              • #8
                You can check the supported textures here : http://www.spot3d.com/vray/help/maya...ender_maya.htm
                Cloud is one of the textures that is mapped to perlin noise, so the results in V-Ray are very different compared to Maya.

                Greetings,
                Vladimir Nedev
                Vantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help

                Comment


                • #9
                  ok , thanks!

                  Comment


                  • #10
                    Think I found a bug...
                    smoke TEX from "create texture from vray plugin" leaves miscolored buckets while distributing render to Mac slaves

                    Comment


                    • #11
                      Are the buckets totally black or just a different color compared to the ones rendered on the client machine ?

                      Greetings,
                      Vladimir Nedev
                      Vantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help

                      Comment


                      • #12
                        The texture is there, just a shift in brightness, almost as if the Mac slaves use a different gamma .
                        Pc slaves render exactly the same.
                        Last edited by timdog; 13-05-2010, 03:02 PM.

                        Comment

                        Working...
                        X