Hey, Scott. Thanks. It's good to know about these bugs. I won't even bother with it 2016 anymore.
There were a just a couple of advantages (for me at least) that 2016 had over 2014.
-it loaded the material editor and material libraries a lot faster
-it had FINALLY group layer like rhino (although i was very excited about it, i kind of never used it at the end of the day ehehehe), but at the expense of a more complicated user interface, i think.
As i do most of the modelling in other programs, whichever new features were cool, i wouldn't even know how to use them
Now, i have just reinstalled all my plugins and everything on a fresh 2014 installation and... fingers crossed!
Already, it has come up with a problem:
My material libraries (vray) that were been used by 2016 all these weeks now aren't recognized by 2014. AAAAAAAHHHHHHHHHHH!!!!!!!!!!!!!! I know max files don't have backwards compatibility and i had to leave 2016 installed to save my libraries and stuff *.2014 along the way, but for the matlibs, there is no way i can SAVE AS _ legacy format.
@SCOTT, as for the layer names i realized that if you export in .3ds it cuts the layer names after 4 or 5 letters and applies a _0001 after it (eg: _b_facade_glass = _b_fac0001), but if you export to .dwg it exports the whole name of the layers.
Cheers guys and good work!!!!