What is the best practice for keeping legacy versions of grasshopper plugins so that you can have both a functional install of Rhino6 and Rhino5?
Ideally, we would have Grasshopper in Rhino5 point to a different folder for plugins than Grasshopper in Rhino6 so that there aren’t so many conflicts. I often need to open up older files and it would be great if I could simply open them up in Rhino 5 with the plugins that were working in Rhino 5. Why do Rhino 5 and Rhino 6 both look in the same folder (AppData>Roaming>Grasshopper>Libraries) for Grasshopper plugins? It seems like the changes to Rhino and Grasshopper between Rhino 5 and 6 were big enough that maybe it would make sense to have two libraries, one for each Rhino version? A bunch of plugins have either R5 or R6 versions and I can’t have both in the libraries directory without errors.
It’s great that Rhino installs new versions of itself without overwriting the old version but it seems like that then creates a conflict with Grasshopper sharing the same libraries. If anyone has a good solution for this, please let me know. For example, is it possible to force Rhino5 to look for plugins in here instead: