Announcement

Collapse
No announcement yet.

test scene

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

  • ASUS ENGTX570 DCII/2DIS/1280MD5 - Driver 295.73
    3m 32.3s
    Click image for larger version

Name:	vrrt.jpg
Views:	1
Size:	344.0 KB
ID:	845094

    Comment


    • 4 x GeForce GTX 580 @ 925/1850/2125 (295.73) - 45.8 seconds...

      Click image for larger version

Name:	4_x_GTX_580_at_925_1850_2125.jpg
Views:	1
Size:	343.1 KB
ID:	845110
      Ivan Tiunov
      Red Screw + Production

      Comment


      • More hardware, more tests.

        The GTX 580 Classified is apparently overclocked at the factory. The GPU and Shader clock are both significantly faster.

        GTX 580 -------------------- 512 cores - 290.36 Drivers - 3min 6.0 sec
        GTX 580 Classified ---------- 512 cores - 290.36 Drivers - 2 min 50.4 sec
        GTX 580 + GTX 580 Classified 1024 cores - 290.36 Drivers - 1min 29.7 sec

        -Alan

        Comment


        • Sorry to be a pain in the butt, how do I add on the time it's taken and do I just leave it running or does it stop/finish/stamp itself to an image?
          This is using the standalone RT that came with the Maya version.

          Comment


          • Add the following options on the command line:
            Code:
            -rtengine=3 -rtsamplelevel=500
            This will cause the rendering to stop after 512 iterations - you can then check the render time in the output from the standalone.

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

            Comment


            • Does anyone know if the amount of memory on a card effects the render speed much? 1.5GB vs 3Gb on a GTX 580 for example?

              Looking at buying:
              http://www.scan.co.uk/shop/computer-...28512-cores%29
              Simon Askham - http://www.supercreative3d.com Rendering with Threadripper 2990WX Asus Prime X399 36GB DDR4

              Comment


              • Originally posted by vlado View Post
                Add the following options on the command line:
                Code:
                -rtengine=3 -rtsamplelevel=500
                This will cause the rendering to stop after 512 iterations - you can then check the render time in the output from the standalone.

                Best regards,
                Vlado

                Ahh fantastic, many thanks Vlado !
                I left it for about 40 mins and guessed I needed to add something else to it

                Comment


                • ... one of the reasons a 680 GTX is not making any sense.

                  Click image for larger version

Name:	RTtest_Indoorscene_680-GTX_800x450_2min12sec_NV301.10.jpg
Views:	1
Size:	321.8 KB
ID:	845543
                  680-GTX_800x450 2min23sec NV301.10


                  Click image for larger version

Name:	RTtest_Indoorscene_580-GTX_800x450_2min12sec_NV301.10.jpg
Views:	1
Size:	321.8 KB
ID:	845542
                  580-GTX_800x450 2min12sec NV301.10


                  Click image for larger version

Name:	RTtest_Indoorscene_580+680-GTX_800x450_2min12sec_NV301.10.jpg
Views:	1
Size:	321.8 KB
ID:	845540
                  580+680-GTX_800x450 1min11sec NV301.10

                  Click image for larger version

Name:	RTtest_Indoorscene_580+680-GTX_1080p_6min45sec_NV301.10_crippled.jpg
Views:	1
Size:	493.9 KB
ID:	845541
                  580+680-GTX_1080p 6min45sec NV301.10_crippled

                  I dont know why... havent tried a second attemp, but somehow this one sadlygot crippled.
                  It was in the first steps working fine, and also the KPaths/s made sense (roundabout 2900) then this...
                  after that I was no more able to rerender this until I was restarting MAX.


                  ... just for Information purpose:
                  Click image for larger version

Name:	GPU-Shark_Screenshot_580+680-GTX.JPG
Views:	1
Size:	142.0 KB
ID:	845539
                  GPU-Shark_Screenshot_580+680-GTX


                  cheers guys!

                  Comment


                  • Originally posted by caypiranha View Post
                    [ATTACH=CONFIG]...

                    [ATTACH=CONFIG]10012[/ATTACH]
                    580+680-GTX_1080p 6min45sec NV301.10_crippled

                    I dont know why... havent tried a second attemp, but somehow this one sadlygot crippled.
                    It was in the first steps working fine, and also the KPaths/s made sense (roundabout 2900) then this...
                    after that I was no more able to rerender this until I was restarting MAX.


                    ...
                    I've the same problem as your last crippled test.
                    I've a GTS450 (for now) and with this test scene only with drivers until 275.33 it's ok, but with newer driver i've this problem.
                    Any tips?
                    www.kodocreation.com

                    Comment


                    • You can try switching between the CUDA/OpenCL engines; also look for any errors in the output from the V-Ray RT render server.

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

                      Comment


                      • I've already tried, but nothing!
                        vray have an error similar to:"driver api error"
                        www.kodocreation.com

                        Comment


                        • Originally posted by 3DKodo View Post
                          I've already tried, but nothing!
                          vray have an error similar to:"driver api error"
                          That is quite something What is the number after the error?

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

                          Comment


                          • Ok, vray version 2.30.02 and nvidia driver 301.42

                            OpenCL test: after few minutes the monitor goes black for some seconds, and after vray rt returns this error

                            Error Invalid command queue (-36) at line 224 , in file ./src/ocl_tracedevice.cp
                            p !!!
                            Error Invalid command queue (-36) at line 651 , in file ./src/ocl_tracedevice.cp
                            p !!!
                            Error Invalid command queue (-36) at line 1120 , in file ./src/ocl_tracedevice.c
                            pp !!!



                            Windows error details:
                            Firma problema:
                            Nome evento problema: APPCRASH
                            Nome applicazione: vray.exe
                            Versione applicazione: 1.0.0.1
                            Timestamp applicazione: 4fa1ebdd
                            Nome modulo con errori: nvcuda.dll
                            Versione modulo con errori: 8.17.13.142
                            Timestamp modulo con errori: 4fb2030d
                            Codice eccezione: c0000005
                            Offset eccezione: 00000000001170d8
                            Versione SO: 6.1.7601.2.1.0.256.48
                            ID impostazioni locali: 1040
                            Informazioni aggiuntive 1: a82f
                            Ulteriori informazioni 2: a82f7330b0c6da0847fb4d98d143073a
                            Ulteriori informazioni 3: 8c6e
                            Ulteriori informazioni 4: 8c6e8aa3419f99d3c8e6d2dfacb7ea63


                            Cuda test: after few minutes the monitor goes black for some seconds, and after vray rt returns this error

                            ./src/ocl_tracedevice.cpp<1120> : Driver API error : 999
                            ./src/ocl_tracedevice.cpp<655> : Driver API error : 999
                            ./src/ocl_tracedevice.cpp<224> : Driver API error : 999
                            ./src/ocl_tracedevice.cpp<224> : Driver API error : 999


                            Windows error details:
                            Firma problema:
                            Nome evento problema: APPCRASH
                            Nome applicazione: vray.exe
                            Versione applicazione: 1.0.0.1
                            Timestamp applicazione: 4fa1ebdd
                            Nome modulo con errori: KERNELBASE.dll
                            Versione modulo con errori: 6.1.7601.17651
                            Timestamp modulo con errori: 4e21213c
                            Codice eccezione: 80000003
                            Offset eccezione: 0000000000033172
                            Versione SO: 6.1.7601.2.1.0.256.48
                            ID impostazioni locali: 1040
                            Informazioni aggiuntive 1: 05f6
                            Ulteriori informazioni 2: 05f65b1fbb913c6b9f1d05cef9ac366b
                            Ulteriori informazioni 3: a68b
                            Ulteriori informazioni 4: a68b91e5e34e5a61f4ee320beeb2cc3b


                            these are all informations i've found!
                            I hope you can help me....we
                            www.kodocreation.com

                            Comment


                            • That's the OpenCL error... what's the CUDA one?

                              FYI this rendered fine here on GTX 680 at 1080p.

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

                              Comment


                              • the second test is cuda...and this is the error returned
                                ./src/ocl_tracedevice.cpp<1120> : Driver API error : 999
                                ./src/ocl_tracedevice.cpp<655> : Driver API error : 999
                                ./src/ocl_tracedevice.cpp<224> : Driver API error : 999
                                ./src/ocl_tracedevice.cpp<224> : Driver API error : 999
                                www.kodocreation.com

                                Comment

                                Working...
                                X