ViewCube breaks entire viewport

[Anonymous]

Whenever I try to change my view via the viewcube, all objects and the viewcube itself disappear. This happens in ortho and perspective. all thats left in my view then, are the letters x,y, and z stacked on top of each other with 1 red pixel below them. I can use my mousewheel to zoom apparently, since the position of those letters changes when i alter the zoom focus (move my mouse around while zooming). I can manually select the view positions just fine. If I do that i can orbit my object and change from perp and ortho back and forth just fine. But when i click anywhere on the ViewCube again, boom, all gone. "Restore Viewport" does not help and ive found no Viewcube settings that could matter here.

no even starting from a new startup scene works out... kind of hard to work on a model when you can't see it

[Anonymous]

Wanted to bump this thread since I'm facing the same issue and haven't found a solution yet. This is what it looks like

[Anonymous]

Seems like it has something to do with the file, because it worked fine again when I loaded up an older save

[Alfred.DeFlaminis]

Hello @Anonymous and @Anonymous,

This is certainly odd.  Can you both please let me know more about your graphics cards, Max versions, and OS's?  It may be that the GPU's are unsupported or perhaps there is a bug here somewhere, but it's hard to say without a scene file.  Is it possible to share one of the files with this issue?  This isn't something I've seen a lot of, so I'm interested in learning as much about it as possible.  Thanks for any additional information. 

Best Regards,

[Anonymous]

Asus GTX 970 Strix, Intel i5 3rd Gen (Yeah, next thing to upgrade), 3DS Max 2017 (Student License), Windows 10 (most recent updates)

I included my save where this occured. It's hard to replicate and seems quite random. Mostly happens in perspective (try to just spam-click locations on the VC)

[Anonymous]

I'm using Max 2017 (student version) and my graphics card is an asus GTX 960m

Running Windows 10 home edition.

Here's the thing though. I can't replicate the issue again, and the same file is working fine now. Back when I was having this issue, I had noticed that my objects had some custom attributes allocated to them, which are gone now. Could this be possible related to anything?

[Alfred.DeFlaminis]

Thank you for the file @Anonymous and the details, that is very helpful.  Also, thank you for the details @Anonymous. 

Are you using W10 home as well @Anonymous?  Max does require the professional version of Windows to run properly, as noted here in the system requirements.  However, I don't think that's the cause of this, as I am able to repro some kind of viewcube problems.  I also cannot frame on the paddles at all in my perspective window.  There is something fishy going on here, and when I merge these parts into a new scene the problem doesn't resolve.  Are you both on the latest service packs / updates  available to you?  

What's interesting is my Max will act up for the rest of the session even if I reset once I've opened this file.  So, something going on there and I'll log this to the tracker right now.  Thank you for sharing the file.  I looked for a workaround and the only thing I found that helps is to literally delete the objects.  Somehow these objects were corrupted.  Is it possible this was loaded from a recovery file or something along those lines?  Any ideas what might have led to this?  Thanks!

Best Regards,

[Alfred.DeFlaminis]

I wanted to add that this is likely not caused by the viewcube, but the viewcube suffers as a result of what is causing this. I am logging the information now.

Best Regards,

[Anonymous]

I do recall those custom attributes shilbose mentioned. I can't look into the file right now, but you should find those in the ribbon ( if thats what you call the frame to the right), just like "Edit Edges" aso. Those were terribly formatted and the Text didn't quite fit into its borders. Something about mental ray displacement. Also yeah, those objects were probably recovered at some Point, but they didn't act up in any previous save.

[Alfred.DeFlaminis]

Thank you very much @Anonymous, this was all very helpful.  I can confirm that this isn't something you or @Anonymous have done wrong, it's a problem in Max and it will be looked at.  Thank you very much.  

Best Regards,

[Anonymous]

@Alfred.DeFlaminis thanks so much for looking into this

[Alfred.DeFlaminis]

No problem at all @Anonymous, it's why I'm here for you.  The weirdest part about this file is that deleting the paddle and the teal object fixes the problem!?   I did a lot of testing and logged it into the system to be looked at by someone in QA.  It's very bizarre.

In the meanwhile if this happens again, please revert back to a previous file.  Something corrupted the objects in the scene which had this far reaching effect. (It could have been a crash and a recovery file load, things like this can occasionally happen.)  I like to use iterative saves so when I press Control S, it saves a new version automatically.  You can set this up in Customize->Preferences->Files-> check Increment on Save.  

Best Regards,