Hi FDP, thanks for the information. But it's pretty difficult for me to fully understand what you're seeing without having specific examples.
Can you please post example 3DM models for each of the situations that you describe?
For example, you wrote:
> My projects usually have dozens of individual named objects and the scenario
> I find myself in all the time is needing to see how say, the M3 Pivot Pin and Spring
> interact with the Capo Hinged Group items.
You say how the objects "interact" - do you mean you want to know if these objects touch each other?
Can you please post a 3DM model file (or e-mail to me at
moi@moi3d.com) with the "M3 Pivot Pin and Spring" and "Capo Hinged Group items" so that I can try to repeat what you are doing over here and try to gain better understanding?
> 1.) Accidentally copying a group when I want to copy one object in the group. If the group is large enough
> (I have some 800MB projects with a hundred or more objects) this can cause the UI to stutter.
Can you please send a 3DM file where you are getting the stutter when accidentally copying a group?
For files larger than 10MB you'll need to use a sharing surface like WeTransfer, DropBox, OneDrive.
> 2.) Groups causing UI stuttering just by existing in a project.
Can you send the project file where you're seeing the UI behaving differently with a particular group existing versus with it removed?
> 3.) This is an issue with the latest beta and not only a group problem, but some sub-objects
> randomly turning their visibility on and off during project loading. It seems like visibility state
> is not saving correctly when projects are saved and then loaded. This is a V5 Beta issue.
There was a v5 bug that was preventing shaded surfaces from being shown on an object that started out hidden in the initial file load. It would end up looking like a wireframe display with only the edge curves showing on a solid and not shaded faces.
That should be fixed in the current v5 beta though. If you have any cases where visibility state is not saving correctly in the current v5 beta please send me the model files so I can reproduce the problem and then try to fix it.
Thanks,
- Michael