I have looked into your file and there are two separate issues I’d like to comment on:
First, T.MAP can and will not work as expected directly on the example you sent. This is because your mesh has lots of naked edges in its interior, but T.MAP needs a closed (watertight) mesh to work properly.
<img src=“https://discourse-cdn-aws1.com/mcneel/uploads/default/original/4/b/4b5e05131dd757dc0a27311062cd509318804495.jpg” width=“400"”>
Your mesh is made up of several mesh patches of different density which don’t fite together - this can be seen by using the Rhino “Explode” command on it:
I suspect that the mesh was created by meshing a NURBS polysurface. You can try to redo this in Rhino with the “Jagged seams” option unchecked during the meshing, this should result in the individual meshed patches fitting together. See these instructions from our release thread:
If the quality of the polysurface is not good enough to get a watertight mesh using the Rhino mesher, you could fit a new triangle mesh to your input by using EvoluteTools Light.
Secondly, we are still looking for the reason for the Rhino proccess not quitting. We have seen this behavior before, but we can’t reproduce it with the current T.MAP release, not even in connection with your example file. I have a quick question on that: Does this occur when you quit Rhino normally, or only when you force quit it after one of our plugins fails to respond for a while?