I work in construction and regularly import large models (usually from Tekla) into SketchUp. These usually come in a .ifc file format. My first step is to break them up into tags/layers. SketchUp is TERRIBLE at facilitating this. Some of these models have up to 10,000 - 25,000 components/groups. I should be able to easily do this through Outliner. However… Soon as you type one letter into outliner it start to search. Why is this? For example a common search is Bolt Assembly, soon as you type B it searches all 25,000 components for “B” and then “BO” the SketchUp crashes. (pasting “Bolt Assembly” in the search bar doesn’t seem to help.)
What benefit does this have? Could we not just have the search start on an enter command?
Since we are on this subject, since 2024 release the “3D Text” dialog box now does not auto select the default “enter text” so this has to manually be deleted before entering your text, another big time loss that was added/overlooked.
I’ve been using SketchUp since 2017 and it’s functionality just get worst and worst with every update.
Yeah, this one is an annoying basic UI fail. My outliner search does not crash, Ive got thousands of items but less than you it sounds, so perhaps it’s just you’re maxing the capacity somehow. Interesting that it should crash rather than hang. If you want to PM me one of your files I can try it on my end and see how it handles.
I personally really benefit from this feature, but I can understand your frustration. Hopefully there is a way to resolve this without removing the instant search functionality, as most users I don’t think have models with enough components to cause the search to fail.
As far as benefit, there are a few:
Speed (especially important this function is used frequently)
Unknown naming convention (I might know an object starts with “wall” but I don’t know if it is plural, or something different like “wall_Exterior”)
Quick refinement of query: if I get too many results when I type “wall” I know that I need to refine my query to say “wall_Exterior”
Typos: in a hurry to name a group or component, I might have written “wal” instead of “wall”