Announcement

Collapse
No announcement yet.

442.52 unavailable and 442.92 doesn't work with rtx

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

  • 442.52 unavailable and 442.92 doesn't work with rtx

    As the title suggests.
    Anyone have a link to the one that works please? I must have misplaced the one I had.

    EDIT: I now am getting this error with CUDA...no idea what it means. The render starts, gets to pass 6 and stops.

    Attached Files
    Last edited by fixeighted; 21-06-2020, 01:22 AM.
    https://www.behance.net/bartgelin

  • #2
    Seems like something went wrong on the GPU. Can you send the scene over to alexander.soklev@chaosgroup.com so I can investigate?
    Alexander Soklev | Team Lead | V-Ray GPU

    Comment


    • #3
      It's 1.4gb so will take a while but sure.
      Anything on the driver? 442.52 WAS working fine but it got upgraded to something else which didn't work. Now that driver does not exist so I cannot reinstall it.
      As mentioned, the only one available is .92 and that is totally useless.
      You guys still have .52 as recommended driver but if it doesn't exist......maybe you have it that I can download? Maybe that will fix the current issue..
      https://www.behance.net/bartgelin

      Comment


      • #4
        Yeah, that's our bad. Didn't notice that NVidia have brought down 442.52 for some reason, maybe it had some issue that didn't affect V-Ray so they deviced to bring it down.
        I believe it's safe to upgrade to 445.87. Haven't had any complaints about it.
        We're currently stress testing the new 446.14 and if it's stable we will soon update to it.
        Alexander Soklev | Team Lead | V-Ray GPU

        Comment


        • #5
          Updated the page to now recommend 445.87 so people are not confused anymore. Thank you for pointing this out
          Alexander Soklev | Team Lead | V-Ray GPU

          Comment


          • #6
            Let me install .87 and see if that fixes stuff before uploading this file. Hopefully it will fix the RTX thing too.

            https://www.behance.net/bartgelin

            Comment


            • #7
              I installed .87 and it worked...the first time. This was direct render, not IPR, res 1100x619.
              Second was IPR and 3rd was direct render, res 3000x1688 - both failed.
              Went back to IPR at the resolution that worked, 1100x619. This time failed with errors.
              I switched back to CUDA and it is still broken with the same errors.
              Doesn't even recognise there's a compatible GPU now.
              This is Max 21, Vray 5, with lightmix, tonemap, lensfx

              For comparison I loaded the same scene to Max 20, Vray Next 4.30.01
              Apart from errors for missing new materials there are no errors with RTX or CUDA mode in IPR at any resolution I tried.

              Is there still any point in sending the specific scene, as it clearly works with previous versions?

              There is also an issue with mattes which I'll post separately.
              https://www.behance.net/bartgelin

              Comment


              • #8
                There's definitely a point in sending the scene. It will tell us exactly what's broken, so we can fix it.
                Same for the mattes, if there's an issue, please send a scene that we can reproduce with and we will fix the problem.
                Alexander Soklev | Team Lead | V-Ray GPU

                Comment


                • #9
                  Ok I'll pack it and post a dropbox link here when it's done...could be quite a while lol.
                  Meanwhile here is the post for the matte stuff https://forums.chaosgroup.com/forum/...pu#post1075490

                  EDIT: Of course I won't post the big model link here - who do I send it to ?

                  EDIT: I sent the scene to support, mentioning this post.

                  EDIT: I thought it might be helpful to include a grab of what happens after the initial error - showing that subsequently the card is not recognised as even compatible.
                  This, by the way, screws the whole session regardless of renderer rest.
                  Attached Files
                  Last edited by fixeighted; 23-06-2020, 06:54 AM.
                  https://www.behance.net/bartgelin

                  Comment


                  • #10
                    I know you guys are very busy but any small update on this at all? Or is there another proven driver that will work?
                    https://www.behance.net/bartgelin

                    Comment


                    • #11
                      I've been trying to reproduce the problem but can't. I used to run driver 445.87, and not I am running 451.48.
                      No crashes here. Will try on a few more machines just in case
                      Alexander Soklev | Team Lead | V-Ray GPU

                      Comment


                      • #12
                        That is odd, as clearly it is fine with Max 20.
                        I can't think what I could test here to try to figure it out....
                        https://www.behance.net/bartgelin

                        Comment


                        • #13
                          The good news is that I have this working now.
                          Clearly there was something in the scene that was causing the errors but I don't know what.
                          The scene I sent to support was stripped down a little (very little, just to tidy it), so something that I stripped was to blame, or it was a random glitch which
                          has since rectified itself. Maybe it was a Windows update....who the hell knows?!

                          Anyway it remains strange that the scene, even with those bad elements, worked fine with max 2020 CPU and GPU and fine with 2021 CPU after multiple tests over days.
                          https://www.behance.net/bartgelin

                          Comment

                          Working...
                          X