Announcement

Collapse
No announcement yet.

VFB Becomes Unresponsive & Flickers In Latest Build

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

  • VFB Becomes Unresponsive & Flickers In Latest Build

    Hi,

    The VFB becomes unresponsive when you click any of it's UI buttons after a render finishes. Also when it does this, the VFB window will disappear then reappear repeatedly for a few minutes then stop. Also if I try and move the VFB window it does this.

    I saw this behavior a few times in the 2.21 build, but now in the 2.22 build it is constant. I have had to quit using the vray VFB. Anyone else seen this happen?

    thx

  • #2
    Can you tell me which 3ds Max version you are using? If you are using Windows 7, have you tried with the Aero theme disabled (or enabled, opposite of whatever you normally have)? If you are using 3ds Max 2012, have you tried changing between Nitrous/DirectX viewport driver?

    In any case, unfortunately I don't think we can do a lot to fix this issue on our side, but it might be possible to find a configuration where it does not happen (or least happens less often).

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

    Comment


    • #3
      Hi,

      I am running 2012 SP2 on Win 7 64bit with Aero. I am not sure this problem has anything to do with Nitrous, as it has progressively worsened since version 2.1. In the latest build the problem is so bad that I can't use the VFB. I have reverted back to 2.1 and it is again usable. In 2.1 there is still a very slight hang up of the VFB after a render finishes, meaning that if I click one of the buttons after the render finishes, it may take a second to respond. In the latest build, doing that causes it to hang up for several minutes while the VFB window blinks on and off.

      rgds

      Comment


      • #4
        Ok then; what happens if you try my suggestions, just as a test? (The VFB code is not fundamentally different between the two builds, so I'm not sure right away what's causing the different behavior.)

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

        Comment


        • #5
          I had issues like this too. Violent behaviour from the V-ray VFB when trying to move it or close it. It would flash repeatedly, sometimes for minutes. However, after disabling "progressive update" in Viewport configuration/Display Performance and disabling the Win 7 aero theme, the problem seems to have gone.

          T

          Comment


          • #6
            I had the same issue on different machines with the vfb becoming nearly unusable (unresponsive and flickering back an forth) with the latest build. Also, the Solid Rocks interface became really sluggish. It seems disabling "progressive update" has solved the problem. The aero theme has no impact.

            Does someone know if the progressive update of the viewports can be disabled globally? It is a nice feature, but most cases it makes more problems than it helps.

            Comment


            • #7
              I had it happen today using the 2.1 build for the first time. I have not had a chance to try your suggestion yet with the latest build because all of my machines are busy rendering at the moment.

              thx

              Originally posted by vlado View Post
              Ok then; what happens if you try my suggestions, just as a test? (The VFB code is not fundamentally different between the two builds, so I'm not sure right away what's causing the different behavior.)

              Best regards,
              Vlado

              Comment


              • #8
                Ok then; some users suggested that turning off the Nitrous progressive refinement option also helps to avoid the issue.

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

                Comment


                • #9
                  Unfortunately I have to leave that option on, because it helps viewport FPS quite a bit. Is there a planned fix? It can last for several minutes here before I can regain control of 3dsmax.

                  thx

                  Comment


                  • #10
                    There is nothing we can do on our side to fix this. Autodesk are aware of the issue but I do not know if/when I fix will be available from them.

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

                    Comment

                    Working...
                    X