Whoops, okay good point. I was thinking about the Make2D point first - as I could replicate it constantly, I wanted to ensure it wasn’t an erroneous point. Pretty sure I mailed this to his McNeel address. I’ve just sent him the link via discourse now for the 9 GBish file.
Attached is a plug-in that will purge all unused texture mapping table entries. Just load the 9Gb on your machine, drag and drop the plug-in onto Rhino and type “PurgeTextureMappingTable” at the command prompt.
I’ve sent you a different file that points to this problem. Let me know if you see the same.
Thank you! Is this something that is considered for being added to the Purge command in future? Was this something already available as a dev tool in plugin form, or newly made? Thanks for your help - I really appreciate it!
What do you think has generated the excessive amount of texture mapping entries?
Cool! For now I’ve just done it as an alias tagged onto purge.
Do you feel it’s something that was necessary to add on? (Not esoteric or anything?) - by which I also mean, is there any value of the mapping entries being in the table, if they’re no longer used?
See the below text file of a command history. I think some curves must have entered the texture mapping table? is that right? the curves were a result of Make2D.