Announcement

Collapse
No announcement yet.

V-Ray 3.40.02 for 3ds Max is available for download

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

  • V-Ray 3.40.02 for 3ds Max is available for download

    Hello all,

    There is a small update for V-Ray 3.40, here is the change log:

    Build 3.40.02 (official) (14 June 2016)
    ==============

    Modified features:
    (*) VRayDenoiser: Prevent the denoiser render elements from saving as separate files;
    (*) VRayOSLMtl/VRayOSLTex: Speed up texture sampling;
    (*) vdenoise.exe: Add "-abortOnOpenCLError" to stop hardware accelerated denoising on errors;
    (*) vdenoise.exe: Add "-frames" option that allows to specify the frames to process;
    (*) vdenoise.exe: Add "-verboseLevel" option;

    Bug fixes:
    (*) V-Ray: Materials with self-illumination enabled render incorrectly when light cache is secondary GI engine;
    (*) V-Ray: Fixed problems with light cache "Store direct light" when using IR+LC after V-Ray 3.40.01;
    (*) V-Ray RT: "Elements active" option in Render Elements tab is not working;
    (*) VRay RT GPU: Fireflies appear on scene with VRayFastSSS2;
    (*) VRay RT GPU: Highlight glossiness still renders when Trace reflections option is disabled;
    (*) VFB: Clicking on the white area of the scroll bar in the color corrections window scrolls by just one pixel;
    (*) VFB: Image messes up when scrolling in the window;
    (*) VFB: Toolbar icons are not stretched over the entire buttons when screen dpi is changed;
    (*) VRayDenoiser: Denoising artifact appears on images with fireflies;
    (*) VRayDenoiser: Hardware accelerated denoiser messes up the progress bar during progressive rendering;
    (*) VRayDenoiser: Returns black result on some computers when hardware accelerated;
    (*) VRayGLSLMtl/VRayGLSLTex: The __color keyword is not respected;
    (*) VRayGLSLMtl/VRayGLSLTex: Bool uniforms with initializers get random values;
    (*) VRayHDRI: Lag when switching between Shaded and Wireframe viewport modes;
    (*) VRayOSLMtl/VRayOSLTex: Empty texmap inputs lead to input parameters after them to be skipped;
    (*) VRayStereoscopic: Fixed artifacts in the render;
    (*) VRayTriplanarTex: Crash when connected to a bump slot and has VRayNormalMap;
    (*) vdenoise.exe: Doesn't work with network paths for input files;

    Best regards,
    Alexander
    Alexander Kazandzhiev
    V-Ray for 3ds Max developer

  • #2
    Seems with the release of 3.4 your servers really start sweating
    Splendid update and fast as always! Nice.
    Software:
    Windows 7 Ultimate x64 SP1
    3ds Max 2016 SP4
    V-Ray Adv 3.60.04


    Hardware:
    Intel Core i7-4930K @ 3.40 GHz
    NVIDIA GeForce GTX 780 (4096MB RAM)
    64GB RAM


    DxDiag

    Comment


    • #3
      thank you for the update

      Comment


      • #4
        (*) VRayHDRI: Lag when switching between Shaded and Wireframe viewport modes;

        Awesome sauce.
        A.

        ---------------------
        www.digitaltwins.be

        Comment


        • #5
          Hi, do you plan to release this and further updates for max2011 as well?
          Kind regards
          Aleksander
          Last edited by DONT_PANIC; 16-06-2016, 08:20 AM.

          Comment


          • #6
            Fast new release, but 2 issue not fixed

            OPENCL and a mysterious black line
            http://forums.chaosgroup.com/showthr...ous-black-line

            And one other issue when exporting vrscene, ActiveShade (old Interactive render) setting is exported instead of Product Render setting into vrscene file.
            (I'm remember contact vlado for that)

            Comment


            • #7
              Originally posted by Raph4 View Post
              This is actually fixed in the nightly builds, but the fix did not make into the stable 3.40 branch yet as it needs more testing.

              And one other issue when exporting vrscene, ActiveShade (old Interactive render) setting is exported instead of Product Render setting into vrscene file. (I'm remember contact vlado for that)
              We found out that this is a 3ds Max bug. Unfortunately there is nothing that we can do about it now. When we rework the regular V-Ray to be usable as interactive renderer, we won't be using ActiveShade - that approach basically sucks.

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

              Comment


              • #8
                (*) VRayDenoiser: Prevent the denoiser render elements from saving as separate files;

                So this means the file sizes have reduced?
                Brendan Coyle | www.brendancoyle.com

                Comment

                Working...
                X