Announcement

Collapse
No announcement yet.

VFB freezes and becomes unusable in Vray 3.30.04. Had to revert back to 3.30.03

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

  • VFB freezes and becomes unusable in Vray 3.30.04. Had to revert back to 3.30.03

    A couple of days ago after I installed Vray 3.30.04 the VFB started freezing and I can neither click anything in it, nor close it. The only thing that fixes it is if I ALT+TAB to another app/window and then switch to Max again. BUT... it fixes it just for a couple of seconds and then it freezes again so you have to be fast and tab out and in Max all the time! This has happened to me before too and I think it is a well known bug but it wasn't that bad. This one I'm experiencing now takes this problem to a whole new level since the VFB freezes a second or two after you tab back to Max, where before tabbing out and back to Max fixed it for a long time before the VFB freezed again. Working like this is just impossible so I uninstalled 3.30.04 and reverted back to 3.30.03. I'm happy to say that now I don't get this problem so I suspect it comes from 3.30.04.

    Please find attached a video showing the problem and a simple scene where it is happening so you can test. Max 2016 SP1, no plug-ins used except for Vray 3.30.04. To test properly, try switching some times between rendering a region and full frame (no region). Sometimes it doesn't happen immediately so be patient. Also, don't change anything in the scene or Vray settings.
    Attached Files
    Aleksandar Mitov
    www.renarvisuals.com
    office@renarvisuals.com

    3ds Max 2023.2.2 + Vray 7 Hotfix 1
    AMD Ryzen 9 9950X 16-core
    96GB DDR5
    GeForce RTX 5090 32GB + GPU Driver 572.83

  • #2
    Yes I've been having this also. Every time I do anything in the VFB I have to minimize it and restore it before I can do anything else in Max or the VFB.
    James Burrell www.objektiv-j.com
    Visit my Patreon patreon.com/JamesBurrell

    Comment


    • #3
      I believe this was fixed in the nightly builds, saw this on the forum a few weeks ago I still use that build and get the same issue but got used to it for now.
      Adam Trowers

      Comment


      • #4
        Same here. I had to revert back to 3.30.03. It was impossible to work like this.
        | Max 2016 SP2 | Vray 3.30.03 |
        | Intel XEON E5-2620 x 2 | 32GB RAM | Nvidia GTX 970 (4GB) | SSD | Win10 x64 |

        Comment


        • #5
          Had this too but i installed one of the most recent nightlies and the problem is mostly gone, i don't have the issue but a coworker still has it but not as commonly.

          Comment


          • #6
            Originally posted by Moriah View Post
            i don't have the issue but a coworker still has it but not as commonly.
            It will be nice to share the reproduce steps for this, since after the fix it should be fine
            If it was that easy, it would have already been done

            Peter Matanov
            Chaos

            Comment


            • #7
              Can I get a version where these problems are fixed?
              Aleksandar Mitov
              www.renarvisuals.com
              office@renarvisuals.com

              3ds Max 2023.2.2 + Vray 7 Hotfix 1
              AMD Ryzen 9 9950X 16-core
              96GB DDR5
              GeForce RTX 5090 32GB + GPU Driver 572.83

              Comment


              • #8
                Originally posted by slizer View Post
                It will be nice to share the reproduce steps for this, since after the fix it should be fine
                We have the same versions, similar computers, etc. Only thing i can think of is that he is used to maximize vray's buffer window, and i don't...

                Comment


                • #9
                  Originally posted by Alex_M View Post
                  Can I get a version where these problems are fixed?
                  Email me to vlado@chaosgroup.com and we'll try to get you a fixed build.

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

                  Comment


                  • #10
                    same problem here.

                    3dsmax 2016 SP2 and latest Vray plugin

                    Comment


                    • #11
                      Same answer as one post above...

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

                      Comment


                      • #12
                        I could have sworn I posted a reply to this or maybe it was another thread, anyway I got the same thing where I could click once only in the VFB and after that I had to either alt+tab to another app or click the desktop and back to max, but then again I could only click once in the VFB and after that I go zero response. Anyway one thing that seemed to work was close max all together and open it again and then "Merge" the scene I was working on in to a fresh max scene and re-save it and that seemed to do the trick for me and I was able to work as normal. This has happened on 3 different files and 3 different times the workaround above worked.
                        Cheers,
                        -dave
                        ■ ASUS ROG STRIX X399-E - 1950X ■ ASUS ROG STRIX X399-E - 2990WX ■ ASUS PRIME X399 - 2990WX ■ GIGABYTE AORUS X399 - 2990WX ■ ASUS Maximus Extreme XI with i9-9900k ■

                        Comment


                        • #13
                          I have the same problem with the "old" 3.20.03. and 3ds max 2014.

                          Comment


                          • #14
                            We have some VFB focus issues with 3.30.03. I assumed that was what was fixed in .04 (have been in production; so unable to update). In our case sometimes I cannot click on anything in the VFB. Occasionally I can click cancel on the render dialog. Sometimes even that doesn't seem to work. Sometimes the mouse tracking of render buckets stops working too.

                            Switching to another app and back via alt-tab seems to fix it.

                            Again, this is 3.30.03. So perhaps this is fixed in .04.

                            Comment


                            • #15
                              We'll be releasing a patch next week that solves these issues.

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

                              Comment

                              Working...