FWIMW a shitshow is a shitshow, and everything goes.
Nooooo!!! You are too valuable here. You can’t do that! You have so much insight, knowledge, great experience working with all things vector, cameras, views, massive shitshow files, OpenGL issues, viewmodes, and all your array of knowledge that’s much thicker that a flatworm.
If all you need is a bit of drama, I’ll be your lobbyist. Confession: I have organically grown a group of special interest users who contact me offline, privately to ask me to pander and scream about their favorite papercut. It’s one of those business that grew very organically, no idea why
I’m thinking about starting a Rhino Users’ Union. We could have local chapters, events, motorcycle rides, we can all go on customer sites tours, and even on rides of Celeste, @Jess’s boat.
I agree with Steve here. A lot of paper cuts have been addressed, but we have to keep in mind that there are sooo many of them. And not because Rhino is bad or anything, there are so many tools, commands, workflows, use cases, user types, there’s just so much of everything. So this is understandable.
@Jarek, regarding this particular problem of performance, I think I also brought it up. Not sure of her win the forum or privately to Pascal. In my case was trying to update a bunch of cylinders used as cutters for speaker perf patterns. It’s a problem that we encounter a lot of we have to change slighting their diameter. We have even gone out of our way to avoid using this otherwise super simple method for size editing.
I think as BoxEdit takes another pass of refinement there’s a lot of things that could be improved. I’ve been very vocal about how this tool is under-developed. It has improved but still has a lot of flaws and limitations.
For me it’s biggest limitation right now (before the performance issue you mentioned for many objects) is that it does not work in subobjects. Especially useful in polygonal workflows where you want to control exactly the size/alignment/scaling of a selection of poly faces/edges/vertices. Of course all this polygon work applies equally to SubD, but since SubDs in Rhino are ‘Special’ I can’t even imagine the extra burden of performance this will bring. …this gets me to a very emotional topic to me, so I better stop. There’s a full workday ahead.
Let’s hope your papercut gets fixed soon!