Announcement

Collapse
No announcement yet.

Frame Buffer often became unresponsive

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

  • Frame Buffer often became unresponsive

    Unable to review, edit and even save (if Save Image option isn't turned on in Asset Editor) because Frame Buffer alone, not V-Ray plug-in itself, is unresponsive.

    The only way I know to address this issue is to close and open SketchUp itself then relaunch V-Ray.

    Anyone else is having a similar problem? Any suggestions for a better workaround and/or avoiding it?

  • #2
    Hi mengchung_liu,

    Is it possible to provide more details as to when exactly does this happen? Are you using Interactive rendering, is it only on specific/heavy projects or does it always happen?
    Do you see any errors or warnings in the Progress log while rendering?

    Have you tried reinstalling V-Ray to see if the issue disappears?
    You could also try deleting the Frame Buffer state by going to C:\Users\%username%\AppData\Roaming\Chaos Group\V-Ray for SketchUp - there should be a file named FrameBufferState.fbs.

    Providing a screen-recording might also help, or alternatively - you can get in touch so we can schedule a remote session.
    Nikoleta Garkova | chaos.com

    Comment


    • #3
      Hi nikoleta.garkova, thanks for your response.

      It happens quite randomly when I'm working on heavy projects without any errors or logs able to retrieve.

      I'll try to capture something useful for your analysis the next time it happens.

      Comment


      • #4
        Hey mengchung_liu,

        A recording would be greatly appreciated. You could also try deleting the FrameBufferState.fbs as mentioned above, or reinstalling, just to make sure. Another thing you could try is updating your drivers, if you're using old ones. Can you also give us the system specifications - CPU/GPU/driver versions? Thanks.
        Nikoleta Garkova | chaos.com

        Comment


        • #5
          nikoleta.garkova it happened so spontaneously that I really don't know when to expect it and capturing the problem.

          It happened again just now, as I was starting the interactive renders. Please see the screen recording taken after it happened, and I've deleted the FrameBufferState.fbs as suggested.



          My system specifications:
          CPU: AMD Ryzen 7 3700X 3593 Mhz
          GPU: NVIDIA GeForce GTX 1660 Ti
          GPU Driver: Ver. 471.41
          Last edited by mengchung_liu; 27-07-2021, 01:14 AM.

          Comment


          • #6
            This doesn't seem VFB specific if you are unable to load anything from the V-Ray toolbar. Is it possible to get in touch so we can schedule a remote session and investigate on the spot? You can mention this thread (or my name) in the subject. Much appreciated.
            Nikoleta Garkova | chaos.com

            Comment


            • #7
              Is there any resolution for this issue? I'm having the same problem with Rhino. Nothing works except for restarting Rhino.

              Comment


              • #8
                Hi guys,

                First of all, excuse us for the inconvenience!

                This issue is unfortunately not happening for anyone here at our office.
                Otherwise we would have caught and fixed it.

                I'll talk to the developers and share any ideas for how to continue investigating the issue.

                In the meantime you can 'restart' V-Ray without closing SketchUp.
                Just navigate to and use the Extensions / V-Ray / Help / License / Release V-Ray License feature.
                The next time you click on any of the V-Ray toolbar buttons V-Ray will be reinitiated.

                Regards,
                Konstantin

                Comment


                • #9
                  Here's one thing you can try.
                  After the VFB becomes unresponsive just run the following code in the Ruby console:
                  Code:
                  VRay::WindowManager.show(VRay::WindowManager::LOG_WINDOW)
                  The render log window should pop up.
                  You can share any errors or warnings if such are listed there.

                  Konstantin

                  Comment

                  Working...
                  X