This is indeed great news!
Yes, I think it is correct that if Model Groups are supported, this would allow us to isolate an instance of a family inside a group. Then we would use ‘Switch objects’ on the group intead than on the family, which would kind of solve problem a) as well.
Another thing that we noticed, is that Shapespark keeps the names of the Families as they come from Revit, which is very helpful because we can reuse Extension setting from a Shapespark model from one project to another. However, we also noticed that in the case of Revit Links, Shapespark adds a number at the end of the name. It would be better if it didn’t do so (either for Groups or Links) once support is implemented, because it is very common for architecture firms to use ‘standard’ groups in a way that is similar to families (like a standard Bathroom design group that is the same in multiple projects, gathering several appliances and plumbing families together). If we use an extension to switch between bathroom layout groups, and the name is kept the same as the Revit group, we could reuse the same Shapespark Extension settings on every project just like we can do with families.
Once support for groups is implemented, my firm is probably going to do heavy usage of Shapespark (we are not able to achieve the results we want without this). I know it’s probably too soon to ask, but is there a target date for this Q4 update? So we can better plan our work around here.
Thanks again for your amazing product and attention to customers!