No there isn’t at the moment. Although gha files are loaded from folders that contain rhp files that are loaded, so if you put the gha in a folder next to an rhp, and make sure only Rhino6 knows about that rhp, the error should go away on Rhino5.
At this point the only other thing we can do (because there will be no more releases of Grasshopper for Rhino 5) is indeed designate a special folder somewhere for Rhino6 GHAs only.
@stevebaer, any suggestions on where might make sense?
What about putting version numbers inside current special folder? That can be used for any future version that needs a separate folder.
Good idea for future releases, won’t stop GH on Rhino5 from trying to load it.
I’m going to fart that question off to @will since he may have an opinion on what would work best if something like a package manager ever became available 
@MarcusStrube, since this is probably going to happen more and more, the next weekly WIP release (should be Tuesday unless it gets cancelled) will load GHA files from a folder where GH in Rhino5 does not look. This will allow users to install GHAs for Rhino6 only. We still need to do some testing so I won’t tell you where this folder is until we’re certain it’ll work as advertised.
I found it, thank you.
A reminder that latest version can always be found here: https://github.com/mcneel/GhShaderNodes/releases
Hello. played a bit with grasshopper today. rhino wip example.3dm (2.9 MB)
tried a basic setting with the nodes.
do not understand if this is a bug or feature but it’s funrhino wip example.gh (13.4 KB)
The error you see is related to RH-38781. Baking the geometry (and then assigning your own material again to it) should get rid of the buggy drawing.
Hi,
I was wondering if there is a way to set some basic parameters (like a colour or diffuse texture) for the OpenGL views when using a Cycles XML material? The pink is nice, but not practical 
Currently there is no way, but it is on my list to write a function that does that.
Until then you could of course set Cycles for Rhino as your current renderer. It should render the Cycles XML materials correctly.
I look forward to that. Then I will finally be able to use the Disney shader for everyday work.
I’m going to try a workaround and see if works ok. The problem right now is I work with OpenGL views all the time, and I can’t look at all pink objects all day! But I’ve made a custom display mode and set it to use Object’s color for shading. Now I can just change the object color to something similar to the Cycles XML material, so while designing it doesn’t look so bad.
Is it broken again? I used the latest release from github and Rhino WIP is up to date. I am getting the TargetInvocationEception and FileNotFoundEXception errors on all of the nodes it looks like
I did make some changes to the internal setup. I’ll check if I need to release a new version when I am at the office.
Edit: got caught up in bug fixing, but this week I can definitely check.
I just posted a new .RHI for the shader nodes. Compiled against current public BETA, you can find it at https://github.com/mcneel/GhShaderNodes/releases/latest
error on install:
I’m actually not sure if grasshopper components should be installable from a .rhi. Just get the .zip, unpack somewhere, and place the files in the appropriate special folder ( File > Special Folders > Components Folder).
Hmm, not sure what happened here. I was under the impression I installed latest BETA, as that is the track I am on, but for some reason I see I have a newer build. I am assuming a new public BETA will be out sometime tomorrow. If that is the case I’ll rebuild against that (and double-check first I really have latest BETA).
