Verm <a@b> wrote:
> In case anyone had not spotted it... chessmesh uses a mesh not mesh2 so> the issue is not mesh2 specific.
.... which would have been a surprise anyway, because below the hood they're
actually the same.
(But it rules out the parser as the source of the error :P)
