Announcement

Collapse
No announcement yet.

Slow to kill

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

  • Slow to kill

    I am running the latest V-Ray with 3DS MAX 2015. Nothing special with my scene, however, all of a sudden it is taking 3-4 minutes to cancel a render. Typically, I cancel during the LC pass and usually it isn't an issue.
    Bobby Parker
    www.bobby-parker.com
    e-mail: info@bobby-parker.com
    phone: 2188206812

    My current hardware setup:
    • Ryzen 9 5900x CPU
    • 128gb Vengeance RGB Pro RAM
    • NVIDIA GeForce RTX 4090
    • ​Windows 11 Pro

  • #2
    more like 7-8 minutes to kill.... WTH!
    Bobby Parker
    www.bobby-parker.com
    e-mail: info@bobby-parker.com
    phone: 2188206812

    My current hardware setup:
    • Ryzen 9 5900x CPU
    • 128gb Vengeance RGB Pro RAM
    • NVIDIA GeForce RTX 4090
    • ​Windows 11 Pro

    Comment


    • #3
      displacement?

      Comment


      • #4
        Yep! When I globally disable it then the slow to kill goes away.
        Bobby Parker
        www.bobby-parker.com
        e-mail: info@bobby-parker.com
        phone: 2188206812

        My current hardware setup:
        • Ryzen 9 5900x CPU
        • 128gb Vengeance RGB Pro RAM
        • NVIDIA GeForce RTX 4090
        • ​Windows 11 Pro

        Comment


        • #5
          Actually, it was a Walls & Tiles shader that was causing havoc. I had to rebuild it. I won't get this 1/2 day back!
          Bobby Parker
          www.bobby-parker.com
          e-mail: info@bobby-parker.com
          phone: 2188206812

          My current hardware setup:
          • Ryzen 9 5900x CPU
          • 128gb Vengeance RGB Pro RAM
          • NVIDIA GeForce RTX 4090
          • ​Windows 11 Pro

          Comment


          • #6
            Originally posted by glorybound View Post
            Actually, it was a Walls & Tiles shader that was causing havoc. I had to rebuild it. I won't get this 1/2 day back!
            I have similar issues with W&T shaders.
            Especially after I upgraded to W&T 1.4. Probably something with the new licensing system.
            I installed both Floating License and a Node-Locked license and unfortunately W&T 1.4 performs bad and slow.

            After a long troubleshooting with VIZPARK support and trying out 1.4.1 beta and "special builds" of 1.4 I ended up installing 1.3.2 on Max 2016.
            So far so good.
            Now waiting for a proper 1.4
            This is a signature.

            Comment

            Working...
            X