But, the happiness didn’t last long, because I now discovered that it is my GrassHopper definition which causes some Rhino objects to go bananas. When I run my Gh definition in Rh5 the aforementioned x-ray problem is back again.
And more. For example, there’s a square surface in the picture below, but (after “healing”) it has lost its visibility after the first run of the Gh definition. It’s not that this object is “hidden” (it must always be available for the user to guide the baking), and unhiding doesn’t bring it back. In short: Something in my Gh def seems to affect the shader since also other objects (mesh objects only it seems) becomes affected (“x-rayed”).
Fig.1. An invisible object is there (see gumball). This is a little surface that is used to “guide” the baking position of the (grey) sphere & cylinder thing (the Gh baking works, but in Rh5 it also distorts the shader of the meshes in the model).
And I can’t switch to WIP with this project as of yet. Now what?
I have now tracked the problem down to
SetPt (!). Well, so it seems.
When I drag the “guide surface” around, it all seems to work (at least the guide surface stays visible), but if I try to move the center of that surface using
SetPt (see Gif) then suddenly the surface disappears (this surface is referenced from the Gh Def in a surface component, guiding the baking of the ball & shaft).
Fig.2. On SetPt, suddenly the moved surface disappears :
Same problem in WIP 6.