Thanks for reporting this Tony, it's definitely a bug in the display mesh generation.

I've collected it with a couple of other display mesh bugs. It will probably be a while before I'll be able to solve these, I'm putting more of a priority on fixing export mesh bugs instead for 1.0.

- Michael