Announcement

Collapse
No announcement yet.

Render node not using CPU with Hybrid CUDA Rendering

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

  • Render node not using CPU with Hybrid CUDA Rendering

    Hi guys,

    I've got a little issue with rendering via Backburner:

    I've set a couple of scenes to use CUDA GPU + CPU, when I send the scene to Backburner it uses both the CPU and GPU on my local PC, but on an identical render node PC it only seems to use the GPU, the CPU is ignored.

    Would anybody know why this may be?

    Both PCs are running windows 10, Maya 2018.6, and Vray Next 4.12.01

  • #2
    Have you enabled C++/CPU on the slave machines, in the Select devices for V-RayGPU rendering tool?
    Zdravko Keremidchiev | chaos.com
    Chaos Support Representative | contact us

    Comment


    • #3
      Ah, that did it! It wasn't enabled in the GPU options... Many thanks for the fix!

      Comment


      • #4
        You are welcome
        Zdravko Keremidchiev | chaos.com
        Chaos Support Representative | contact us

        Comment


        • #5
          Originally posted by Zdravko.Keremidchiev View Post
          You are welcome
          Hi, I seem to be having an issue with this again: My render slave PC has got both the CPU and the GPU (GTX 1060) set to render in the "Select Devices for V-Ray GPU Rendering" tool, but it isn't rendering on the CPU on the slave.

          I've attempted restarting and updating the graphics card drivers to the latest studio releases (matching on both identical PCs).

          Comment


          • #6
            ...I'm still having this error, despite having the CPU and GPU set to be used in the "Select Devices for V-Ray GPU Rendering" tool :/ Zdravko.Keremidchiev

            Comment


            • #7
              I'm sorry for the late reply. Would it be possible to send us an e-mail (support@chaosgroup.com) so we could arrange a team-viewer session and check thigs first hand. Please make sure to mention this thread in your e-mail.
              Zdravko Keremidchiev | chaos.com
              Chaos Support Representative | contact us

              Comment


              • #8
                Was there any resolution to this problem?

                I'm having the same issue with Vray 5 for Mays, the local machine uses CPU and GPU but my two render nodes only use their GPU's.


                Thanks
                THREADRIPPER 3970x │64 CORES | 256 GB RAM │MSI SUPRIM LIQUID RTX 4090 | 3 x 3090 Render Nodes │ MAYA 2022 │ VRay 6 | Win 10 PRO

                Comment


                • #9
                  Originally posted by GARY_ROYLANCE View Post
                  Was there any resolution to this problem?

                  I'm having the same issue with Vray 5 for Mays, the local machine uses CPU and GPU but my two render nodes only use their GPU's.


                  Thanks
                  I'm afraid I can't remember now, I guess you could try and make sure you've got identical versions of Vray on both your master and slave PCs, with the same version of the license server too. Sorry that I can't be of more help!

                  Comment


                  • #10
                    Originally posted by sebbiej View Post

                    I'm afraid I can't remember now, I guess you could try and make sure you've got identical versions of Vray on both your master and slave PCs, with the same version of the license server too. Sorry that I can't be of more help!
                    All the versions are identical, all Windows 10 Pro machine, network is 10Gbe, Nvidia Drivers all the same. Baffling as the Vray Next Benchmark uses the GPU and CPU at 100% on each.

                    Does yours work now?

                    Thanks
                    THREADRIPPER 3970x │64 CORES | 256 GB RAM │MSI SUPRIM LIQUID RTX 4090 | 3 x 3090 Render Nodes │ MAYA 2022 │ VRay 6 | Win 10 PRO

                    Comment


                    • #11
                      Did you double-check whether you have enabled C++/CPU on the slave machines, in the Select devices for V-RayGPU rendering tool? If that is not the case I would advise you to write us an e-mail so we could arrange a team-viewer meeting.
                      Zdravko Keremidchiev | chaos.com
                      Chaos Support Representative | contact us

                      Comment


                      • #12
                        Originally posted by Zdravko.Keremidchiev View Post
                        Did you double-check whether you have enabled C++/CPU on the slave machines, in the Select devices for V-RayGPU rendering tool? If that is not the case I would advise you to write us an e-mail so we could arrange a team-viewer meeting.
                        Hi,

                        Yes all setup to use GPU and CPU on each each slave and the local workstation.
                        THREADRIPPER 3970x │64 CORES | 256 GB RAM │MSI SUPRIM LIQUID RTX 4090 | 3 x 3090 Render Nodes │ MAYA 2022 │ VRay 6 | Win 10 PRO

                        Comment


                        • #13
                          Do you use NVLink and which V-Ray version is this?
                          Zdravko Keremidchiev | chaos.com
                          Chaos Support Representative | contact us

                          Comment


                          • #14
                            Originally posted by Zdravko.Keremidchiev View Post
                            Do you use NVLink and which V-Ray version is this?
                            I don't use NVLink and it is Vray 5 for Maya
                            THREADRIPPER 3970x │64 CORES | 256 GB RAM │MSI SUPRIM LIQUID RTX 4090 | 3 x 3090 Render Nodes │ MAYA 2022 │ VRay 6 | Win 10 PRO

                            Comment


                            • #15
                              In this case, please send us an e-mail to support at chaosgroup so we could arrange a Teamviewer session and check the issue first hand.
                              Zdravko Keremidchiev | chaos.com
                              Chaos Support Representative | contact us

                              Comment

                              Working...
                              X