3ds max 2016 constant cpu usage for viewports

[dlparisi]

I'm having a problem with constant cpu usage in max 2016. Even with an empty scene the cpu usage is between 6-7% if the normal quad view is visible, and about 1-2% if just one viewport is visible. This is on a 5820k, 32gb of ram, Win 7 and a GTX 970. I just updated the nvidia driver to the latest (364.51) but this problem has been present for a while so it's not related to the current driver (although it could still be the driver in general). As long as the 3ds max window is not minimized, it's using the cpu that 6-7%. It doesn't matter if the viewports are set to wireframe, realistic, shaded, etc - it still hits the cpu. Playing with the display configuration (shadow quality, antialiasing, etc) doesn't change anything either. I've currently got it set to Nitrous Direct 3d 11 but it's the same if I select Direct 3d 9 (even more disturbing is setting it to use the Nitrous software driver where it jumps to about 32%). This gets to be a problem if I have multiple max sessions running where I can easily eat up 20% of my cpu cycles.

Is this normal? Does anyone else have similar issues or any idea what might be wrong? I don't recall this on earlier versions being a problem.I'm thinkning it might be a plugin issue or something - is there a way to start max "clean" without any plugins?

[dlparisi]

I just opened up a never used copy of max on a DR node and it behaved exactly the same, 6-7% cpu with an empty scene. Granted it does still have most of the same plugins but I think I can rule out a driver or video card issue.

[vlado]

What if you switch to DirectX viewports?

Best regards,
Vlado

[dlparisi]

Do you mean "Legacy Direct3D"? If so, it goes down below 1% when not interacting with the views. Spinning around and such understandably starts to raise the cpu% but the viewport fps drops when compared to Nitrous Direct 3D 11. So should I just fall back to the old version? This seems incredibly stupid if that's the case.

[vlado]

Do you mean "Legacy Direct3D"? If so, it goes down below 1% when not interacting with the views. Spinning around and such understandably starts to raise the cpu% but the viewport fps drops when compared to Nitrous Direct 3D 11. So should I just fall back to the old version? This seems incredibly stupid if that's the case.

You could also try disabling the progressive refinement for Nitrous, maybe that could help too.

Best regards,
Vlado

[dlparisi]

Already disabled. Anyone else have similar issues?