animagic (4/29/2018)
It would be helpful if you explained what is crippled about it. FBX import in CC serves a specific purpose, which is perfectly alright. That doesn't make it "non-standard".
"Industry standard" is also a bit of a misnomer, given that Autodesk willy-nilly changes the specs, which are proprietary. A real standard isn't something that doesn't change every year (FBX 2012, 2013, 2014, 2015...
) You do it right once with input from various industrial parties and then be done for the next 10 years. There are myriads documented cases of programs that have or have had trouble with this so-called standard (Blender and DAZ come to mind, for example).
My thinking is, if you state you comply with a standard, then implement a proprietary version of that standard, you are not in compliance with that standard after all. It's just an observation. I agree, it's perfectly all right.
"Less clicks good, more clicks bad."