So, 3DS MAX 2017 has been released and I am still having major problems in 3DS MAX 2016. How a mature software like this is so broken, confuses me. I can’t see things I try to edit and the layer explorer is broken; both keeps be from being productive. Here is what is happening in my later explorer.
http://screencast-o-matic.com/watch/cDhtDhi1L9
Anybody find a workaround?
The resolution might be to low to see, but my roses are not on any layer. it says layer 0, but as you see, nothing is on layer 0. Also, I have layers that are empty, yet I can’t delete them.
Pardon the small icons. The software works like freeware, so you have to expect things like this (sarcasm).
The small icons are fine, but the video is too fuzzy to make anything out, even if I set it to fullscreen
Yes, I figured that. I am using their free service, which isn’t very good 
Not any better! I paid for a pro account, thinking I could create videos that can be watched. I guess not!
your max window is fullscreen on a 4k monitor…
I’ll try it again, but with a smaller MAX screen.
change your screen resolution to 1080p before recording instead
I’m not exactly sure what you’re experiencing, but I agree the scene explorer is terrible. It seems to have been added as an afterthought using maxscript. State sets are even worse… I used that for a project recently and once I had more than 15-20 states suddenly it stopped allowing simple things like reordering states, and kept getting maxscript errors…
I have elements that can’t be found in the explorer. The properties might say layer 0, however, they are not there. In the example, that you can’t see (my apologies) I have a couple dozen rose bushes that I have to select one-by-one to edit.
surely you do it with maxscript.
found this on google.
-- create new layer
layer = LayerManager.newLayer()
-- set layer’s name
layer.setname “My Layer”
-- add nodes to layer from selection
for n in (selection as array) do layer.addnode n
you’ll obviously have to select all the objects you want to move, and it’s only a quickfix but hey, it works…
Interesting, thanks! I have since hacked my scene to make it work, however, I’ll bookmark this for next time.
I just got an error, but thanks for the try.
Bobby,
What features are in 2016 that make you want to use it ?
From all the stories I’ve read, as well as my own experience of it (last year), I wonder when, if ever, I’ll ever be making the jump from 2014.
I think AD will make you make the jump, eventually. I don’t see any reason to upgrade from 2014 and from what I’m hearing, 2017 won’t give you a reason, either.
Depends on what you need, you might not need new features in 2016. But, 2017 is a different story. The overall speed improvement and UV update is too big to pass on.
Anyway.. back to OP.
So… you can not see certain object in SE?
Is that object part of group or container? Xref?
Is it happen even after you merge the object in a new scene?
Ha. And I’m still on 2012. The golden year. Still haven’t seen anything improve…
Wow… 2012… you should try at least 2014.
If I have to use 2012 viewport again, that would be hell…