[Plugin] Solid Inspector

Dave R · 2 Jun 2011, 23:47

Marcus. I'll send one with yours.

thomthom · 3 Jun 2011, 06:11

Cookies!!!

mariocha · 3 Jun 2011, 12:01

Cookies!!!

jgb · 3 Jun 2011, 12:36

Can't tell you TT how ecstatic I am with SI.
Although I have some suggestions for improvement, it still amazes me how it can find tiny random elements that SU says are "~0 in" in length that prevent a solid from forming, that would be simply impossible to find without SI.

When Google upgraded SU to form solids, something like SI should have been a native function, far more important and useful than merging solids that are only available with Pro. But Google has always displayed excellent software for internally identifying errors, but rate a serious for telling us exactly what the error is and where to find it to fix.

My only suggestions to improve SI are;
1- allow it to function INSIDE the group/comp. Right now it is a repetitive set of operations to
** select the group/comp,

call-up SI (which is my "S" key shortcut),
hit <return> to locate the next error,
zero in on it and place the cursor on the red highlighted object,
press <spacebar> to exit SI,
enter EDIT mode and
select the offender and then
delete it, which is 99.999% of the time the required fix.
Then, exit edit mode,
reselect the group/comp and, IF the solid has not formed (Entity Info box),
do it all over again.* This gets tedious.

If SI worked INSIDE the group/comp, you would only need to
** select the group/comp,

call-up SI,
then hit <enter> to select the first offender,
then <delete> to fix it,
<enter><delete> <enter><delete>* etc.
I would not want SI to automatically delete offenders, as in rare cases this is not the desired fix.

2- If the group/comp is already or finally a valid solid, paint a green circle around it, and if in edit mode, exit the solid.

thomthom · 3 Jun 2011, 14:01

Yup - I want SI to work inside the active group as well. On the todo list.
I just haven't had much time lately for plugins.

commandercup · 11 Jun 2011, 20:29

This is the greatest thing I have ever used.

Thanks for making this!

thomthom · 30 Jun 2011, 08:37

Version 1.1.0
If nothing is selected then the current context will be inspected.

Rich O Brien · 30 Jun 2011, 08:39

Thanks Thom

d12dozr · 30 Jun 2011, 12:27

Thanks, Thomthom

Jim · 2 Jul 2011, 15:20

Just noticed the update. Thanks, thomthom.

Jim · 9 Jul 2011, 14:07

It seems natural that when using Solid Inspector for nested models, that when I click on nothing it should go to the parent context and start checking that. And conversely, double-clicking a Group/Component while using ST could enter that context (except I know it's not possible in the current API ) What do you think?

thomthom · 9 Jul 2011, 14:26

Ah - navigate the current context like the native Selection too does. Yes - not bad idea. Closing is doable, but it does have a nasty bug where the event is not added to the undo stack when you use Ruby - which cause geometry havoc when you do try to undo/redo anything.
( wouldn't mind if more peope, besides me, went nagging to Google about the open/close context issue.)

bogmusic · 11 Jul 2011, 13:39

In a hurry and just got to get this one out....
doh! What do you mean not a solid you stupid machine, aaaaagh!

Thanks thomthom, you have saved me so much trouble.
Come to Yorkshire UK and I will buy you a pint!

jgb · 17 Jul 2011, 17:35

Just discovered a shortcut (sort of) to getting at those tiny fragments buried deep inside a complex solid.

I many cases you cannot easily get to see a fragment inside a solid due to short sightlines and clipping when getting up close, or the red circle seems to be disconnected visually from the fragment.

Pan/zoom till the red circle is around mid screen and then zoom in as close as you can but still outside the solid.

Switch to WIREFRAME view and now you can see the red fragment clearly. Put the pointer ON the fragment and exit SI by pressing the SpaceBar. Double click to enter edit mode. The cursor should still be on or very close to the fragment, click on the fragment to select and then delete it.

Go back to a solid view to make sure you did not open a face. Continue on to the next fragment.

You can also engage SI in XRAY, but you cannot select fragments through the transparent faces.

xiombarg · 7 Aug 2011, 03:49

thomthom, I can't even begin to thank you enough for this tool. You rock.

monsterzero · 8 Aug 2011, 20:10

Just downloaded this after pulling my hair out trying to find why something wasn't solid. This found the problem right quick! Awesome!

helmholtz · 10 Aug 2011, 17:53

ThomThom, once again your plugins have saved me from exploding out of frustration. THANK YOU FOR THIS!!!!!!!!!!!

Helmholtz

fumaru · 23 Sept 2011, 11:16

Using this with fix solid is great http://forums.sketchucation.com/viewtopic.php?t=33471

Thanks for the awsome plugin,
I dont know why SketchUp does not have this feature included in it.

jgb · 25 Sept 2011, 15:43

@jgb said:

Can't tell you TT how ecstatic I am with SI.
Although I have some suggestions for improvement,
I would not want SI to automatically delete offenders, as in rare cases this is not the desired fix.

After using SI extensively over the last few months, I wish to modify my statement above.

I have yet to have a failed solid where deleting every single fragment or duplicate face or lines failed to solve the problem, or worse, partially undo a solid.

Therefore, as an option, I would have SI delete every found element, either all automatically when hitting the <del> key, or sequentially by hitting the <del> key after the <enter> key cycling through the found bits. I think the very rare occurrence of "damage" to the solid by just deleting offenders (never happened to me yet) would also be very easy to fix.

So, yes, delete automatic is my vote.

thomthom · 26 Sept 2011, 07:42

There are cases where a solid has tiny holes, where SketchUp fails to create a face because the edges are too small.