Rhino won't quit since SR11 - Evolute Tools bug

I noticed since I installed SR11 that the Rhino.exe process won’t end after I exit Rhino.
It stays at around 1 900 000 K (I work with large files) and doesn’t move. I don’t see it slowly decreasing or fluctuating, it’s just frozen.

I just did a test with a smaller file and it does the same but it freezes at 328 000 K

Another test, disabling plug-ins. It seems that Evolute Tools is the culprit.

Many thanks for letting us know about this, we will look into it. Please let me know which version of EvoluteTools you are using.

How do we know that? There’s no version number in the file properties of the plug-in and the download is a ZIP file without a date either.
Ah! in the .chm file… it’s version 2.5.7.

Hi, many thanks, please also let me know whether it is EvoluteTools Lite, PRO, or D.LOFT you are using.

I’m not sure what it’s called.
The folder is named “EvoluteTools T.MAP 64bit” and the plug-in files are “EvoluteCoutHook.rhp”, “EvoluteLicenseManager.rhp” and “EvoluteTools_T.MAP.rhp”

Many thanks for your feedback, you are using EvoluteTools T.MAP. We will try to identify the problem and fix it for the upcoming release. Does the problem occur every time you close Rhino?

When the plug-in is enabled, yes.

With the latest beta it’s still a problem, the Rhino process won’t go away after I quit Rhino.
Also, I still can’t get any usable result… I don’t no what the options do and just get error messages.

Could you post your example mesh please?

Here’s one;
sample.3dm (3.4 MB)

Hi Marc,

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://global.discourse-cdn.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?


Hi Mathias,
I finally had a few moments to try T.Map again. I have to say that the license validation process is a bit cumbersome. Do I have to go through this again because I disabled the plug-in in Rhino? That was because of the problem of the Rhino process not terminating when I exit Rhino.
So, I changed my render mesh settings so the “Jagged seams” option is not checked. I have to use render mesh because I need to use features like Shutlining. I then used TriangulateMesh and Weld and then the etTMap command worked.
I don’t quite know what the options are doing…
Direction; Curves, Curvature or Boundary?
NumberOfLevels?BoundaryType; Aligned or Extended?
Anyway, I got something:

But this doesn’t shade or render…
I tried to use this as a custom mapping object for the original geometry but it doesn’t work either…

Hi Marc,

thanks for staying with us!

About your questions:

  • License Validation: Could you explain a bit further what exactly you had to do again? Your license from your first registration should still be valid, deactivating the plugin shouldn’t matter.
  • Options: The option menu will have tooltips soon, and we will also allow you to press “F1” to open the Plugin help while on the menu. For now, the help file that came with the plugin can be opened from within Rhino via the “Help->Plug-ins” menu. All the options are explained there, please let us know if something is unclear.
  • Shading: Yes, this is something we have to fix. You created a quad mesh with T.MAP and selected to align (or cut) it with the boundary of your input mesh. That results in a mesh which includes arbitrary n-gons (pentagons, hexagons,…). EvoluteTools can shade such meshes, but T.MAP can’t yet. This will be fixed very soon.
  • Input for custom mapping: Only pure quad or triangle meshes can be used as input for TMapFromMesh. Therefore the n-gon mesh won’t work. Use the “extended” option instead of “aligned” to get a pure quad mesh which is then not perfectly aligned with your original boundary.


Hi Mathias,

  • When I enabled back the T.Map plug-ins (EvoluteCoutHook, EvoluteTools License Manager and EvoluteTools T.Map), it started the registration process all over. But today it doesn’t… fine.
  • Ok for the help document.
  • What does that mean? Rhino, by itself, won’t shade or render these meshes? The T.Map plug-in will have to be present to get a rendering?
  • I couldn’t try this, Rhino is now crashing everytime I try to run T.Map.
    What I wanted to do, since the resulting mesh wasn’t visible in renderings, is using th T.Map mesh as a custom texture mapping object for Rhino’s mesh.
    I join the object I’m playing with:
    mesh sample.3dm (6.7 MB)