Hi stucki -
Okay so after a lot more testing I was able to reproduce the issue fairly consistently. The direct fbx import of the asset into 4.8 was where I was incorrect in replicating the issue. I was updating the entire 4.7.6 project to 4.8.1 which keeps the ability of the mesh to accept tessellated material, doing a direct import does not.
I continued testing trying to recreate a mesh which causes the same issue and ran into a wall as I am uncertain of exactly what happened that would cause the issue. The downside is I do not have 2016 to really test with but Max 2015.
BUT, good news I tested your assets in the Main branch and the issue seems to have been resolved which means that a fix for your issue will be forth coming.
Thank You -
Eric Ketchum