[Plugin] Solid Inspector
-
dear Thomthom
when I said "simple" I wanted to say that it was an easy program
to use, no less important.
"simplicity is characteristic of that is good"
sorry if not properly expressed
(I can not praise what is done well)
your plugin is fantastic.
Thanks.
-
@jgb said:
I've been using Solid Inspector for about 3 weeks now, and only a few days ago discovered the <tab> key, arrow key and <enter> functions. Never thought to look down.
I use it so much I have the "S" key as a shortcut.
But a most unintuitive aspect of SI is when it finds and highlights the problem(s).
Generally you want to delete the offender entity(s).
The process is to toggle amongst the highlights to choose one, which is now indicated by a red circle.
Press <Enter> to zoom in on it.
Place the white arrow cursor on the highlighted entity.
Right click and select "Edit group". If you click "erase" here, it will delete the whole group.
Keeping the cursor on the highlighted entity, Right Click and select "erase". That will delete the single cursor-ed entity only. Either 1 line or 1 face, but not the faces highlighted perimeter lines.
And that leaves you in a form of limbo.
Now you have to select the "edit menu" and "close group" to get back into SI for the next problem.Since 99.9% of the time you want to simply delete the offending entity, why not simply;
Place the cursor on it and just double click to delete the red highlighted entity.
Then you toggle to the next.This obviates the wish for an auto-fix which is complex and where a simple deletion may not be the fix one needs to do.
One other thing; when SI encounters a true solid (no errors) please say so, maybe a green circle around the group/comp. But do come out of the white arrow select mode.
I have plans (desire) to make the inspector work inside the active group/component instead of outside. That would improve usability.
-
Thomthom said "I have plans (desire) to......"
I know THAT feeling all too well.
-
@unknownuser said:
make the inspector work inside the active group/component instead of outside. That would improve usability.
That would sure be a great improvement
on an already so useful plugin! (icon of your username)
Now youv'e made me eager . -
this was realllllly handy to me .... nowadays I was modeling a chair part , to be produced by plastic, and need to be a solid, and it was really handy.
thanx a bunch. -
Nice work Thomas! I am going to check this out. I really hate trying to find small holes in groups!
-
Thank you so much!!!
Leaks had been bugging me for days!
-
@unknownuser said:
Nice work Thomas! I am going to check this out. I really hate trying to find small holes in groups!
Defects in solids are sometimes produced by carrying out SU boolean operations, and these are very difficult to find. SI is a most welcome tool. Thanks a lot!!
-
Thomthom, I use this plugin ALL the time...how do I send you a cookie?
-
Marcus. I'll send one with yours.
-
Cookies!!!
-
Cookies!!!
-
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.
-
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.
-
This is the greatest thing I have ever used.
Thanks for making this!
-
Version 1.1.0
If nothing is selected then the current context will be inspected. -
Thanks Thom
-
Thanks, Thomthom
-
Just noticed the update. Thanks, thomthom.
-
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?
Advertisement