Hi @Dale,
Yes it does,
So I removed it following your remark, and it did the job! 
You saved me many (many) rebuild-restart cycles.
Thanks!
–Xavier
Pretty awesome, eh 
2 Likes
How can I “restart” Grasshopper without this command? I used to use this in Rhino 5 for when GH was acting up for whatever reason; now it appears that I need to restart Rhino to achieve this.
I want this unload function back because i noticed that sometimes when GH is running, rhino crashes when printing pdfs
I doubt the two are related (though anything is possible). If you have a repeatable case where you can crash Rhino, please let us know and we’ll try to fix it immediately
It is a repeatable case. On multiple files have I tried to print pdf of layouts. Crashes often. I’d provide the files but they are company confidential information. Anything else I can do to help you identify the crux?
Hi,Dear David, How about the _GrasshopperReloadAssemblies, Without this command really make me headache when I want to reload a new gha. I really don’t want to restart rhino. Because I use rws to work with many rh files at one time. it’s to slow to restart rhino!
I don’t understand, _GrasshopperReloadAssemblies is available in Rhino6. It was added some time after _GrasshopperUnloadPlugin was removed, but if you’re on a recentish Rhino6 release, it should be available.
3 Likes
Yes, there is a _GrasshopperReloadAssemblies command, really good than before! Great!
Just because no intellisencse tips for this command when I type “Grass…” I thought there is no this command–
I really wish that I could unload GH as before.
I’m trying to figure out which component creates the “Grasshopper breakpoints” that keep popping up, and if I choose to dismiss these messages, then they don’t appear anymore at all which does not help in my investigations.
Before, I used to “GrasshopperUnloadPlugin” and run the definition again with a few components disabled to check if the error was still there.
Since I can’t unload GH, now I need to close Rhino each time which takes even more time…
yeah whatever this command was actually doing, it was useful, for example when updating a plug-in or when grasshopper has started acting funny. I don’t understand why you want to remove features.
If you don’t blame any mishaps on me, try this on your own risk with this evil little script which you can save as a UserObject.
David Rutten already made one variant which kills the def immediately when dropped on the canvas. This thing however is a tad bit more graceful in that you have to give it an explicit final push.
The difference between manslaughter and murder I guess.
// Rolf
1 Like
Thanks, I will definitely use this.
I just crashed bacause I was making a change to a block, and GH is still running a definition which has a pipeline listening to blocks…
@DavidRutten : what was wrong with GHUnloadPlugin ?
Maybe I’ve missed something in this discussion, but I also use GHUnloadPlugin in Rhino 5 to install new GHcomponents. I find it faster and more convenient than restarting Rhino. Or is there a better way to do this in Rhino 6, @DavidRutten ?
GrasshopperReloadAssemblies doesn’t seem to reload all my .ghpy components. I have to restart Rhino.
1 Like
_GrasshopperReloadAssemblies seems useless in the new version.