There is a bug somewhere in the “Group” command – it randomly groups various objects that were not selected. (Unfortunately, I don’t have the time or capacity right now to record a video of this behavior or send the file where it’s happening. Once it occurs again, I will try to capture it, but the behavior is intermittent).
Additionally, when manipulating (rotating) mesh objects, their preview is not visible during movement.
Section drawings still display edges behind the section/cutting plane that are supposed to be hidden.
Rhino BETA experiences intermittent freezes or lagging for no apparent reason, requiring it to be closed via Task Manager and restarted.
thanks for the sample. This doesn’t seem a Rhino 9 specific issue.
I’m not a far from origin expert, so can’t say if 134350 units away from origin is considered to be too far away.
It is; we internally use 2^17 as a value considered “too far” from the origin and perform extra steps to handle the display of the geometry. That is 131072
I’m attaching a file with a set of unrelated objects that Rhino Beta improperly grouped together. When running the Group command, it seems to randomly pick up objects that weren’t part of the selection.
I don’t know if the file will be directly diagnostic, but Rhino Beta is definitely adding unselected objects to groups at random. I almost never use blocks.
@Chita in the project where you encountered objects being grouped inadvertently, is that a project created from scratch in Rhino Beta or did it involve older version files (with groups) as well?
@Wim Yes, they can be. But I didn’t create such a group myself—Rhino keeps adding random assemblies or objects into groups. In the attached GIF, you can see that clicking on one assembly selects the second one as well (they are grouped), but clicking on the second assembly doesn’t select the first one—this is definitely not standard Rhino behavior. I prefer using groups over blocks, and I often have nested groups (“groups within groups”), but this only started happening now in Rhino Beta.
Unfortunately this in itself is not a bug as I thought earlier. Clicking on an object selects the top most group. One way to reproduce this:
Select objects A + B, group → group01
Select objects A + B + C, group → group02
Run SelGroup, select group01, group → group03
Now you can click on C to select group02 (A + B + C), and click on A or B to select group03 (A + B)
Something like this can also happen with other Sel* commands (e.g. two red objects, grouped with two blue objects, then running SelColor → select the red objects → group)
This being said, I’m also confident that there is a bug in Rhino BETA with objects being added to groups, but until we can reproduce this, there isn’t much we can do.
@Gijs I use the same workflow as in RH8 (group combinations, i never use group name, or command for selection, just click or window) - but there never happened something like this. Definitely is problem in beta, but i dont know where…
@Chita I believe you, as said, I am confident that there’s a bug causing this, but the result itself is no proof of it, unfortunately.
While investigating this bug, I did find a regression with groups that is now fixed, which might or might not be related.
