Announcement

Collapse
No announcement yet.

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

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

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

    Hello, V-Ray 3.50.04 is available for download. This is an update of the 3.50 official release, containing bug-fixes and improvements. The changelog follows:

    Build 3.50.04 (official) (03 March 2017)
    ==============

    Modified features:
    (*) V-Ray/V-Ray RT: Optimize compiling geometry for scenes with displacement on machines with many cores;
    (*) V-Ray IPR: Add settings rollout "IPR options" whether to track changes to the VFB size and whether to always use progressive sampling;
    (*) V-Ray RT: Add an option to only render the visible part of image for OpenVR and Oculus renders (Follow VR headset);
    (*) V-Ray GPU: Do not consider Intel GPUs for V-Ray GPU;
    (*) V-Ray GPU: Take the adaptive lights number of lights into account;
    (*) VRayDirt: Make unoccluded sub-texmap slot default when keeping replaced texture as subtexmap;
    (*) VRayMDLMtl: Show MDL enum parameters as combo boxes instead of spinners;
    (*) img2tiledexr: img2tiledexr should store its version and build date into the converted OpenEXR files;

    Bug fixes:
    (*) V-Ray: Animated Noise in VRayLightMtl with Direct Illumination On slows down the rendering drastically;
    (*) V-Ray: Artifacts with Adaptive Lights in certain scenes;
    (*) V-Ray: Deep image result is overwritten when post effects are enabled;
    (*) V-Ray: Distributed rendering with no "Use local host" requires additional license;
    (*) V-Ray: Improve saving time of progressive resumable files to a network location;
    (*) V-Ray: Log flood with "Invalid normal index found on face" with specific geometry;
    (*) V-Ray: Saving to raw images with non-ANSI names fails when post effects are present;
    (*) V-Ray: The main thread hangs when some of the license servers are offline;
    (*) V-Ray: Very slow "compile geometry" phase on particular scenes;
    (*) V-Ray: Wrong VRayZDepth with "use camera clip boundaries" enabled and the physical camera's clipping planes disabled;
    (*) V-Ray IPR: Constant refresh with VRayPhysicalCamera and V-Ray Exposure Control;
    (*) V-Ray IPR: Crash when adding a render element during IPR;
    (*) V-Ray IPR: Crash when using adaptive lights and a new light is added to the scene;
    (*) V-Ray IPR: Rendering hangs and 3ds Max 2017 UI freezes when Physical camera Lens Shift is modified;
    (*) V-Ray RT: Export display sRGB parameter to .vrscene;
    (*) V-Ray RT: Some machines can't load IFL files when accessing them from shared location;
    (*) V-Ray RT: Unhandled exception when rendering scenes with Ornatrix feathers and displacement in production rendering mode;
    (*) V-Ray GPU: Black regions with Projections;
    (*) V-Ray GPU: Different results with VRayClipper and "Camera rays only" option enabled;
    (*) V-Ray GPU: Adaptive Lights are not updated after change in region/resolution during ActiveShade;
    (*) V-Ray GPU: "Compensate camera exposure" of VRayLightMtl is not working;
    (*) V-Ray GPU: CUDA error 719 with specific scene;
    (*) V-Ray GPU: Fix potential crash with unsupported render elements;
    (*) V-Ray GPU: Alpha pixels missing with matte/shadow plane;
    (*) V-Ray GPU: Overexposed lighting when rendering with V-Ray GPU;
    (*) V-Ray GPU: The specular contribution does not get adjusted by the fog attenuation;
    (*) VFB: Denoiser hardware acceleration type is not updated at render end;
    (*) VFB: Denoiser is not applied progressively when rendering with V-Ray RT;
    (*) VFB: Do not apply denoiser on load from history;
    (*) VFB: Lens effects hardware acceleration mode doesn't work;
    (*) VFB: Selecting a point in the curves color correction window causes the point to move;
    (*) VFB: The curves color correction in the VFB should be applied after the exposure;
    (*) VFB: Turning off the "Select object" mode during ActiveShade leaves the wrong cursor;
    (*) VRayDenoiser: Denoiser is calculated every time before V-Ray RT rendering start if it was used before;
    (*) VRayDenoiser: The option "Only generate render elements" is producing corrupt file;
    (*) VRayFur: Not properly generated with Bitmap texmaps;
    (*) VRayGLSLMtl/VRayGLSLTex: Materials are transparent in BRDF mode;
    (*) VRayGLSLMtl/VRayMDLMtl/VRayOSLMtl: None of the 'General' shader properties are accessible through MAXScript;
    (*) VRayOSLMtl/VRayOSLTex: Crash with 1000+ shader nodes;
    (*) VRayOSLMtl/VRayOSLTex: Exporting OSL materials with unconnected textures for V-Ray RT produces broken scenes;
    (*) VRayProxy: Crash with Alembic file with containing incorrect UVW mapping indices in V-Ray RT;
    (*) VRayProxy: Custom attributes for alembic files are lost in "Show whole mesh" display mode;
    (*) VRayToon: "Active" checkbox not exported for V-Ray RT;
    (*) VRayToon: Add render element export for V-Ray RT;
    (*) VRayToon: Missing toon effect with 3ds Max standard cameras;
    (*) VRayMDLMtl: Crash when loading an .mdl while V-Ray RT is running and then stopping it;
    (*) VRayMDLMtl: Exporting empty MDL materials fails;
    (*) VRayMDLMtl: Merging light cache passes is very slow when rendering scene with missing MDL resource files;
    (*) VRayMDLMtl: Shows as incompatible when V-Ray RT is set as production render engine;
    (*) VRayMDLMtl: Spinners reject negative parameter values;
    (*) VRayMDLMtl: Treat df::bsdf() as black diffuse;
    (*) VRayMDLMtl: Wrong rendering of MDL texture with bump on geometry with incorrect tangents;
    (*) VRayScatterVolumeMtl: NaN pixels occur;
    (*) VRayScene: Animation is not working for V-Ray RT;
    (*) VRayScene: Missing objects from imported vrscene when rendered with V-Ray RT;
    (*) VRayScene: Snippet override with wildcards doesn't work on Windows 7;
    (*) V-Ray scene converter: Broken lights instances after conversion;
    (*) img2tiledexr: Fails to convert files properly after 3.50.03;

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

  • #2
    Does this release fix the Vray edgetex and noise problem on the GPU by any chance? It's the last thing I need before I can start using the GPU in production

    Cheers.

    Comment


    • #3
      Originally posted by chadstevens View Post
      Does this release fix the Vray edgetex and noise problem on the GPU by any chance? It's the last thing I need before I can start using the GPU in production
      I'm not sure. Which problem was it?

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

      Comment


      • #4
        Hi Vlado

        I've posted the problem in this thread

        http://forums.chaosgroup.com/showthr...e-for-download No. #16

        I said "This is amazing.

        I did however notice that the procedural maps work in the new beta, but it seems that they do not work in conjunction with vrayedgetex when plugged into a composite map and then into the bump? is this a known problem?

        Cheers.
        "

        Alexander replied to my post asking for information which I gave, but I fear I did so too late

        Cheers.

        Comment


        • #5
          Hi Vlado,
          I just wanted to double-check...

          The stand alone denoiser still cannot take into account the lens effects passes into the denoised result yet...correct?

          Comment


          • #6
            Originally posted by biochemical_animations View Post
            The stand alone denoiser still cannot take into account the lens effects passes into the denoised result yet...correct?
            Yeah, I haven't figured out what to do with this just yet. I hope to have some kind of solution soon.

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

            Comment


            • #7
              Nevermind thought it was in reply to my post haha

              Comment


              • #8
                Originally posted by chadstevens View Post
                Nevermind thought it was in reply to my post haha
                I forwarded it to our GPU guys, they will be able to provide more info.

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

                Comment


                • #9
                  Originally posted by vlado View Post
                  Yeah, I haven't figured out what to do with this just yet. I hope to have some kind of solution soon.

                  Best regards,
                  Vlado
                  OK, thanks...I understand.

                  Comment


                  • #10
                    Originally posted by chadstevens View Post
                    Hi Vlado

                    I've posted the problem in this thread

                    http://forums.chaosgroup.com/showthr...e-for-download No. #16

                    I said "This is amazing.

                    I did however notice that the procedural maps work in the new beta, but it seems that they do not work in conjunction with vrayedgetex when plugged into a composite map and then into the bump? is this a known problem?

                    Cheers.
                    "

                    Alexander replied to my post asking for information which I gave, but I fear I did so too late

                    Cheers.
                    See here:
                    http://forums.chaosgroup.com/showthr...828#post728828

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

                    Comment


                    • #11
                      Originally posted by vlado View Post
                      Yeah, I haven't figured out what to do with this just yet. I hope to have some kind of solution soon.

                      Best regards,
                      Vlado
                      I'm not sure if it's any help...but the way the VFB includes the lens effects passes into the denoised results works great.

                      If you can do this same thing with the stand alone denoiser...for animations, along with the frame blend feature, that would be it. You probably already know this, but I thought I would just mention it, just in case.

                      Comment


                      • #12
                        Probably a dumb question but is it safe to use 3.50.04 on files that are saved/ open/ rendered with 3.50.03 on other computers or will I get inconsistencies between buckets/ results ?

                        I know it's better to use the same version everywhere but I've just upgraded all the machines & nodes on week ago and I just need to use IES in RT on one workstation (I believe 3.50.04 correct this bug)
                        Philippe Steels
                        Pixelab - Blog - Flickr

                        Comment


                        • #13
                          04 seems to fix an error that is not in the changelog. I had a scene with lots of multiscatter and displacement. It took way to much memory during the IR calculation. Went up to 13-14 GB. With 04 it now takes roughly 7gb. very nice.

                          Comment

                          Working...
                          X