====== Mesh optimiser update ====== Hi All, [[http://www.bundysoft.com/phpBB2/viewtopic.php?f=2&t=2107|A valid complaint]] about the [[bundywiki>plugins:calc:atMeshDecimator|tiled mesh exporter]] in L3DT v11.11 was that it didn't optimise the tile edges, which meant that a huge number of triangles in a given tile were devoted to the edges. This was originally done so that neighbouring tiles would match up exactly, without having to do the tricky bit of producing two consistent, seamless optimisations of both sides of the edge between neighbouring tiles. Anyway, long story short, I've modified the plugin so that it can optimise tile edges under certain conditions. Specifically, the latest version of the plugin will optimise tile edges __//if and only if//__ the output tile size is a multiple of the ROAM tessellator patch size (64). This means that if you use the usual power-of-two tile sizes (512, 1024, 2048, etc.) your mesh tiles will be fully optimised, but if you use unusual tile sizes (e.g. 513), your mesh tile edges will not be optimised. Also, the optimisation doesn't apply if you're exporting a selected area; only the whole map. Here's a screenshot of four tiles in Blender. Note that all tiles are optimised uniformly, and there's no high triangle-density areas at the edges.