Announcement

Collapse
No announcement yet.

Help GPU Render Slows

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

  • Help GPU Render Slows

    I'm using 3D Studio 2016 with V-Ray 3.2 under Windows 10 Pro x64.
    I recently bought a nVidia Quadro K2200 with 4 GB of RAM and when I choose V-Ray RT CUDA / OpenCL the console detects the CUDA Device but my scene can may take nearly 3 hours to be finished when CPU takes only 1-2 minutes.
    What could be happening?
    I tested these versions of nVidia Drivers:
    347.52
    350.xx
    355.xx
    With the 347 and 350 versions console V-Ray does not detect the CUDA or OpenCL device.
    Recently with the 355 (last week), the console detects the CUDA device but the rendering is very slow.

  • #2
    Can you show us some samples from the CPU and GPU rendering along their settings.
    If you could send the scene over that would be great.

    Let us also know the exact version of V-Ray since this is important: 3.20.01 / 3.20.02 / 3.20.03
    Last edited by Svetlozar Draganov; 30-09-2015, 06:28 AM.
    Svetlozar Draganov | Senior Manager 3D Support | contact us
    Chaos & Enscape & Cylindo are now one!

    Comment


    • #3
      Hi Svetlozar Draganov.
      I am attaching a picture with the parameters and comparative I was doing.
      If you are interested to send the file to the scene I do.
      (I have to review the textures and its location but do)

      Color note: both textures and 3D Studio files are in an SSD Hard Drive

      I'm open to suggestions.
      Thank you.

      Comment


      • #4
        Hi Svetlozar Draganov.
        I am attaching a picture with the parameters and comparative I was doing.
        If you are interested to send the file to the scene I do.
        (I have to review the textures and its location but do)

        Color note: both textures and 3D Studio files are in an SSD Hard Drive

        I'm open to suggestions.
        Thank you.

        SORRY I UPLOAD A NON FINISHED IMAGE

        Thes are the real times:

        Comment


        • #5
          Thank you for the update.
          I think it will be best if you could send us the scene and the assets to support@chaosgroup.com so we could investigate the issue further.
          Zdravko Keremidchiev | chaos.com
          Chaos Support Representative | contact us

          Comment


          • #6
            you have your noise threshold set to 0 in RT, this will lead to excessive rendertimes. im not sure if this is your only issue, since your times seem excessive even considering that.

            but try changing it to a sensible value such as 0.005.

            chaos: why is the noise threshold 0 by default? its a really odd default value.

            Comment


            • #7
              Originally posted by super gnu View Post
              you have your noise threshold set to 0 in RT, this will lead to excessive rendertimes. im not sure if this is your only issue, since your times seem excessive even considering that.

              but try changing it to a sensible value such as 0.005.

              chaos: why is the noise threshold 0 by default? its a really odd default value.
              When RT is set as production render and all values are = 0, the moment you hit render, max paths/pixel will be changed to 100000 automatically exactly to eliminate a never ending render scenarios.

              So this is the exact problem here - rsaccone you are waiting for a 100000 paths which is actually a lot
              If it was that easy, it would have already been done

              Peter Matanov
              Chaos

              Comment

              Working...
              X