Announcement

Collapse
No announcement yet.

V-Ray RT CUDA and rendering manager

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

  • V-Ray RT CUDA and rendering manager

    Hey,

    I'm checking out alternatives to Backburner at the moment and I'm having a bit of hard time for some reason with rendering effectively with RT CUDA. As it's very fast, I feel that we're loosing a lot of time on loading scene etc.

    While backburner somehow manages to not unload the scene from RT, keeping the link at all times it lacks functionality of multi-slave rendering or support for multi-user management.

    That's why I'm testing Deadline 7 on 30 days trial, but there is something wrong. As long as it manages to keep 3ds max opened between tasks, every-time frame changes its closing DR session and sends it again to RT from start. That's very ineffective especially with bigger scenes. I know that this is probably issue with deadline and I have to check with them as well, but maybe there is some other solution to the problem from V-Ray side.

    Best,
    @wyszolmirski | Dabarti | FB | BE

  • #2
    We are actually working on rendering with RT directly inside of 3ds Max, so all of these issues will go away eventually. It won't be for the service pack next month as there is not enough time to properly test it, but it will go into the nightly builds soon.

    Rendering directly inside of 3ds Max will cut down the translation time and will allow us to reuse loaded textures. It will also make rendering a bit faster as the results won't have to be sent from one process to another.

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

    Comment


    • #3
      That would be really good actually. But still, that leaves us with only Backburner as use-able solution at the moment, unless I will start testing other solutions. I just love how it manages to just update frame number, start it, send update to VRay.exe and render it smoothly without restarting the process - http://wyszolmirski.home.pl/screen/s...04-10_1336.png .

      With deadline after each frame i see 'closing DR session' . But I think that's Deadline issue. It's talking with max differently I think. Backburner uses named pipe and somehow manages work better. It's just a shame I can't run 2 jobs at the same slave via BB.

      Anyway. Thanks for the quick response. I will try to find a good solution.

      Best,
      @wyszolmirski | Dabarti | FB | BE

      Comment


      • #4
        I've just setup this free manager cgru.info and it does work quite well so far. In batches of 10 frames it will reset max/vray_RT once every 1 hour for most of the scenes. So this isn't so bad.

        This lets us render quite effectively on GPU (CGRU) and CPU (BB) at the same time. It's a bit of hustle to set it up at first but after initial battle it just works.

        Best,
        @wyszolmirski | Dabarti | FB | BE

        Comment


        • #5
          Originally posted by vlado View Post
          ...Rendering directly inside of 3ds Max will cut down the translation time and will allow us to reuse loaded textures. It will also make rendering a bit faster as the results won't have to be sent from one process to another.

          Best regards,
          Vlado
          Sounds fantastic...

          -Alan

          Comment


          • #6
            Hi all,

            I'm having no luck rendering a simple chalk teapot using VRay RT as a production renderer with Backburner.

            Is there something Im missing?

            The scene renders fine on my workstation using Quadro 4000 but when I send exactly the same file as a network job using Backburner, the job launches but VRFB is black and the rgb render also black. Alpha is there.

            I'd really like to use RT to produce animations, using mulitple machines so I don't have to lock up my workstation during the day.

            I only have 1 max licence so can't leave it running on another machine.

            Any suggestions very welcome!

            Many thanks, Thomas
            Director, Flowstorm Ltd

            www.flowstorm.co.uk

            Comment


            • #7
              Is backburner running as a service on your render slaves? Does it work if you do a quick test with CPU RT?

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

              Comment


              • #8
                Hi Vlado,

                Thanks for your quick reply.
                In this case I was just closing down max on my workstation and starting the 'server' application on the same workstation.
                (Backburner Manager and Monitor also both running on my workstation just to test the workflow).

                I just tried both CPU and CUDA from within max and they rendered fine - but when sending as a Backburner network job, the frame buffer opens, shuts down quickly (I see the progress bar move much faster than normal), then the render job stops and saves a load of black frames for each render element.

                The scene is simple - teapot on a plane, chalk override material, 1x vray plane light
                I am using Max Design 2014 with vray 3.00.05 - Win 7 x64
                i7 3930K (not overclocked) Quadro 4000

                Thanks for any suggestions / assitance,
                Thomas
                Director, Flowstorm Ltd

                www.flowstorm.co.uk

                Comment


                • #9
                  Ok, right after this happens, can you send me the file %temp%\vraylog.txt to vlado@chaosgroup.com ? It would help to figure out what's going on.

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

                  Comment


                  • #10
                    Hi Vlado,

                    I have just sent you the vraylog file
                    Many thanks again -
                    Thomas
                    Director, Flowstorm Ltd

                    www.flowstorm.co.uk

                    Comment


                    • #11
                      Hi,

                      Now updated to Vray 3.10.03 but am still having the same problem when using Backburner for network rendering.

                      I am using Max Design 2014 with Backburner 2015.0.1 --- (Max 2015 is installed but I don't currently use it as I cant stand the new interface.)

                      Anyone had the same problem / found a solution to this?

                      Many thanks, Thomas
                      Director, Flowstorm Ltd

                      www.flowstorm.co.uk

                      Comment


                      • #12
                        Would it be possible to send the scene for investigation even if it is very simple one?
                        Let us know also what steps we must follow in order to reproduce the issue the same way as you did in your environment.
                        We've done a couple of test here but we couldn't reproduce the bug into our environment.
                        Svetlozar Draganov | Senior Manager 3D Support | contact us
                        Chaos & Enscape & Cylindo are now one!

                        Comment


                        • #13
                          Hi,

                          Thanks for your help.

                          Open the .max file
                          Render the camera viewport locally within max using RT either CPU or CUDA -- works fine.
                          Send exactly the same render using Backburner -- renders black

                          Using Max Design 2014 SP5 with Backburner 2015 (since 2015 is installed it overwrote Backburner 2014)

                          Many thanks, Thomas
                          Attached Files
                          Director, Flowstorm Ltd

                          www.flowstorm.co.uk

                          Comment


                          • #14
                            Thank you very much for the attached scene - it helped us a lot to find where the issue lies.
                            It seems that there is an issue with the Standard Camera when rendering with RT via BackBurner, V-Ray Physical Camera works fine fortunately.

                            I have added a new camera to the scene - please render via V-Ray Physical Cam and let us know if it works or not in your environment.
                            http://ftp.chaosgroup.com/support/scenes/GPU_test05.max
                            Svetlozar Draganov | Senior Manager 3D Support | contact us
                            Chaos & Enscape & Cylindo are now one!

                            Comment


                            • #15
                              Hi Svetlozar,

                              Thanks for your help.

                              Almost there ! -- using the VRay cam has solved the issue when rendering to my workstation.
                              BUT - when rendering using the render slave I get the following issue:

                              RenderSlave, using RT with CPU (Sent as a Backburner network render) - first time the render starts (I see the teapot in the vr framebuffer) but does not complete and Backburner server 'hangs'
                              I then restart Backburner server, the network job starts again and it renders fine !?


                              RenderSlave, using RT with CUDA (Sent as a Backburner network render) -vr frame buffer remains black (max launches ok, vray starts but nothing happens)

                              The render slave is basically the same as my workstation- i7 3930K with a Quadro 4000

                              I remember reading somewhere about vray DR not liking Remote desktop (which I am using to view the render slaves) - could that be the problem?
                              IF it is - how do you suggest I log in to my slaves?
                              Many thanks again, Thomas
                              Director, Flowstorm Ltd

                              www.flowstorm.co.uk

                              Comment

                              Working...
                              X