Announcement

Collapse
No announcement yet.

V-Ray Next for SketchUp, hotfix 1 is now available!

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

  • V-Ray Next for SketchUp, hotfix 1 is now available!

    V-Ray Next for SketchUp, hotfix 1 is now available!

    It can be download here:
    download.chaosgroup.com

    After installation, you will find more detailed info about the changes in the 'VRayForSketchUpReleaseNotes' and the 'changelog' files:
    ./Chaos Group/V-Ray/V-Ray for SketchUp/extension/VRayForSketchUpReleaseNotes.html
    ./Chaos Group/V-Ray/V-Ray for SketchUp/extension/changelog.txt

    Best regards,
    Konstantin

  • #2
    Installation & Licensing

    • The Chaos Group License Server is updated to version 5.2.2
    • The installer now properly sets and displays a primary remote server IP address and port number - 127.0.0.1:30304
    Workflow Improvements

    • The entire asset management system is optimized and made more reliable. This affects asset creation, renaming, deletion, referencing, etc. The optimizations are most obvious in heavy scenes with big number of assets and complex shading networks
    • Render element assets are no longer deleted when the category is active and the Purge function is used. Use the multi-selection functionality to quickly delete a batch of elements
    • The Z Depth render element ‘Depth from Camera’ parameter is removed
    • The VFB Render Progress window now receives and can display log messages that have been sent before its first initialization
    Other Changes & Bug Fixes

    • Saving and loading projects no longer resets the Color Space of all textures to the default sRGB option. Using the File Path Editor no longer changes the color space either
    • The asset preview render process can now be restarted if it stops responding. Make sure to stop and restart the interactive preview (using its toolbar stop/start button) in the unlikely event this happens
    • The fresnel opacity of newly created Reflection material layers is now correctly displayed in the asset preview swatch
    • Invalid material or texture references can now be successfully cleared from the slot's context menu
    • Creating a proxy from big number of SketchUp components or component instances now shows accurate progress in the Export Proxy window
    • An issue with a Water textures used in a bump slot is resolved. Negative texture values are now properly handled
    • All V-Ray taskbar processes are grouped and displayed under the SketchUp Windows taskbar icon. This applies to the Asset Editor and the V-Ray Frame Buffer window
    • VRscan materials are now correctly sized and properly affected by the SketchUp material scale. A helper texture is displayed in the viewport to ensure this. Texture Placement parameters are now listed for every VRscan in it’s Asset Editor properties panel
    • The way VFB Color Corrections are saved within SketchUp projects is updated and made more reliable
    • A number of issues related to V-Ray 3 scenes loading and upgrading are resolved
    • A number of issues related to .vropt (render settings) files loading are resolved
    • The Purge Unused Assets function no longer causes issues on MacOS
    • Materials incorrectly saved with older V-Ray versions no longer cause issues when loaded in Next
    • A number of issues related to complex texture hierarchy manipulation and deletion are resolved
    • The Batch Cloud rendering functionality is temporarily disabled. Once a Chaos Cloud platform-side update is implemented, the feature will be re-enabled. Our main goal is to provide a system that warns users for possible issues with their batch cloud jobs(like missing external file assets, for example), letting them resolve the problem before the rendering starts
    • Images imported through the SketchUp native Import no longer produce problematic V-Ray materials. Scenes containing such images saved with previous V-Ray version no longer cause issues when rendered in Next
    • A number of issues with badly serialized V-Ray component data are resolved. A more detailed error message is displayed and a better log file is created, letting us easily identify any further problems
    • Deleting Fur, Clipper or Mesh Light widgets from a group is now reliably handled during Interactive Rendering
    • A number of issues preventing the V-Ray Asset Editor from being populated with assets on specific scene load are resolved
    • The V-Ray Scene Importer now reliably imports models using multi materials exported from 3ds Max. The material ID assignment in 3ds Max results in a single object group in SketchUp with different materials applied to the corresponding faces
    • The Scene Interaction Tool now works reliably with obstructed light widgets
    • Deleting multiple materials at once no longer produces Ruby errors and warnings
    • Using the Scene Interaction Tool before the previous action is completed no longer prints Ruby errors
    • Skatter Proxy geometry materials render correctly when using the ‘Render only’ mode. Regeneration no longer causes Ruby errors
    • A geometry instancing optimization is implemented for Skatter objects with the ‘Render only’ mode enabled. This ensures that rendering a big number of instances is done in the most memory-efficient way
    • The way the SketchUp default material is handled by V-Ray is improved preventing incorrect lighting in specific situations
    • Activating Material Override during Interactive rendering now reliably affects all scene materials that have their ‘Can Be Overridden’ option enabled
    • Changing the SketchUp material Opacity value automatically disables the synchronization with the V-Ray material refraction. This allows for custom opacity manipulations in the viewport without affecting the rendered result
    • V-Ray material refraction no longer resets in specific situations when the SketchUp scene is saved and reloaded
    • The Z Depth render element tooltips are fixed
    • All Smoke texture parameters are now properly named
    • Repathing files with a Windows path on MacOS no longer causes issues
    • The migration (gamma management) of render elements from scenes saved with V-Ray 3 is improved

    Comment


    • #3
      hey gang, just a heads up that the hotfix is broken. I downloaded around 7PM EST last night and none of our projects load the asset editor running the hotfix (both upgraded and clean installs). We're rolling back now and can provide info, but we have to get some deadlines out the door first.

      Comment


      • #4
        Hi delineator ,

        Could you please share one such project so we can investigate in detail? If this is alright, please send us an archived copy (Extensions > V-Ray > Pack Project) via email or a file-sharing service of your choice to support@chaosgroup.com
        Last edited by georgi.georgiev; 19-04-2019, 08:22 AM.

        Comment


        • #5
          Originally posted by delineator View Post
          hey gang, just a heads up that the hotfix is broken. I downloaded around 7PM EST last night and none of our projects load the asset editor running the hotfix (both upgraded and clean installs). We're rolling back now and can provide info, but we have to get some deadlines out the door first.
          Confirmed, I am able to reproduce the issue with the scene you've shared.
          We'll fix that as soon as possible.
          Thank you for the feedback and sorry for the inconvenience.

          Comment


          • #6
            Just to clarify - it was 100% of our project scenes (I tested maybe 10 and then stopped after I discovered the issue, none of them work with the hotfix). Brand new scenes and small "staging scenes" (ie ones we might build a piece of furniture in and then copy into the master file) seemed to work OK, but not the masters. If there is something we are doing to create this situation, I'd love to know, but for us, this isn't small issue affecting some of our projects

            Comment


            • #7
              Hi delineator,

              Actually the issue has to do with a legacy texture that you've used in some materials - NoiseASGVIS
              We'll patch this quickly so that the legacy textures still work - I'll let you know when the patched version is available for download.
              On the other hand, the ideal long term solution for this would be to implement a migration of this legacy texture to one of the current procedural noise textures we use.

              Konstantin

              Comment

              Working...
              X