[Plugin] Solid Inspector
-
Why this must be made by Hand ? (Close the solid) it detects 2 possibilities?
-
Because while it's easy for us humans to see the correct solution, it's much harder to code a solution. One can code a solution for this specific situation - but that wouldn't apply to other situations. Generic solution for repairing geometry is difficult.
-
The way my SolidSolver deals with that particular case is that it finds faces for the unfaced and single-faced edges on that corner, it then removes the newly added inner triangular partition-face, whilst leaving the three new triangular facets on the outer shell.
At that point it's a solid.
It finally prompts you to remove the three coplanar edges.
If you want the cube actually to have an angled triangular corner facet you need to edit it and delete the unfaced edges before attempting to make it a solid - then the one triangular corner facet is added if it's still missing... -
THX for the infos!
-
While I really appreciate TT's SI2's ability to fix problems, (for me it works well about 90%++ of the time) it would be better if it could simply highlight an "unfixable" problem, now indicated as "info" and maintain that highlight when exiting the tool, so I can find it fast and fix it manually.
Perhaps, by creating a group on its own temporary layer that traces/duplicates the unfixable errors and renders them in red lines/faces, as is done now to identify those errors. That way I can see and fix any problem outside SI2, then simply delete the highlight layer/group.
Just a thought.....
-
I just noticed something; whenever I import an SU-8 model into SU-2015 and make edits to some faces (in what was a perfect solid in SU-8 or SU-15) I often end up with multiple faces off single lines that SI-2 does not see, and SU says it is no longer solid.
It has happened in 3 models so far, and I quite often get 3 faces on a single lined perimeter. When I delete just the extraneous faces, it regains solidity.
It does not happen when the solid originates in SU-15.
Betchya nobody else sees this.
-
Your plugin saved my life, thank you
-
Hi ThomThom, I've been using SI2 for a couple of weeks and is awesome. I totally loved it, but right now I'm checking on a component and it says everything is fine, but still doesn't appear to be a solid component. Dunno what else to do
Thanks
-
Are you able to share the model?
-
This is not a post about the (excellent) Solid Solver in particular, but it applies to it as well so that is why I am using it as an example.
I have problems with eye strains and feel quite uncomfortable looking at many of the low-resolution extension icons that are piling up inside my SU workspace. It looks like they are all out of focus on my Mac retina display, so I found a simple way to upgrade many of them using this simple method. See attached image.
I hope someone else out there find this information helpful as well.
-
I just updated this extension to 2.4.4 in order to add some extra debug code for a particular persistent bug I'm getting reports of - which I've been unable to reproduce.
Please update to the latest version in order to ensure you can submit error reports with better info back to me.
Also, if you run into issues, if you can, please post the model in this thread. (Try to undo whatever Solid Inspector might have tried to fix and submit the model as it where before fixing.)
-
Have a strange issue with Solid Inspector2. Posting screenshot of an example. Modeled the cube at correct size for a casino dice. Made a component. Scaled up 1000x. Drew the "pips" in the scaled up copy, 24 sided circle. Ran Roundcorner on the edges. SU shows it as solid but if I run Solid Inspector I get "short edges" for basically every intersection. No line segment in the scaled up copy is shorter than 2.5". I see this behavior in a lot of different models.
Where the problem comes in I will get a "fix model" prompt when closing SU and if you let it fix the model it will destroy some of your geometry. In this models case it's at the corners of the dice. I'm sure it's something I'm doing but like I said I see this a lot in small objects that I do modifications on in a scaled up copy.Edit - forgot to mention.... SU2015Pro on Mac osx 10.10.5
Advertisement