Yeah, I'm probably supposed to remove and redo video nr.4 anyways, as it was done in haste without a script. It's also a week ago, since then I refined my skills in Blender.
I understand the capacity of MeshLab, but waiting for hours to forward overall decimation is a no brainer. I might start using it once I found a capable way of creating highly resoluted and vertexed maps, and decimate them in Blender more decently. The variant I was trying a week ago is pretty much obsolete, stupid to begin with. Actually the solution came to me when watching video 4 again yesterday. Why start adding high detail and lot of vertexes, and then use decimation for individual reduction, if working the other way around, by adding low detail and low vertex count, and then specificaly increase detail/vertex with subdivide? You'd need to shape out coastlines, AI-travel routes, mountain range etc. anyways. So as I said, nr.4 is supposed to be remade. And just as the other videos it needs a underlying, well thought out script with hours of additionally testing various workflow variants.
Possible variants I'd need to test:
1. high detail/vertex, split import into Blender, using vertex grouped material selection to decimate all various material layers then rejoin all layers with CTRL-J before exporting the map as a whole
2. low detail/vertex, fixed import into Blender, add detail/routes etc. with subdivide function
3. testing general workflow in Wings3D and Meshlab...possible other modeler software?
It also appears I should add a additional standardized section with links and what not, for people not wanting to watch videos, as well as just reading thorugh the other threads I based most of experience on...which I could basically forward now...
BTW your link in module_inf.py is missing a closing /
That's why it adds the module folder name to the file name and dumps the compiled files in the folder above your module folder.
That's done in purpose as I want it to go there. No convenience in cluttering up my module folder...