Roof plugin issues with su2018 pro
-
I have previously used this plugin with SU2017 pro and when I run solidsolver, it fixed any issues and made it a solid. With SU2018 pro, when I run solidsolver, I get an error message that says it can not fix surface border issues. I like to use this to create simple roofs and then use solid tools to combine them into one roof. As I said, in previous version, this worked fine. I have attached a very simple example of what I am wanting to do. Thanks in advance
-
Did you create these two roofs using my 'Roof' plugin ?
Your post is unclear.
But it looks like you did.The two gable-roof groups can never be solids.
When they are created the roof planes and the gable-end walls are made as single skins.
I cannot see how they were ever solids in earlier versions ?There are two straightforward fixes:
-
You could edit them in turn and add a bottom plane to force them into solids: just view with rest-of-model-hidden, from below, and over-draw an edge to form an underside skin...
Then they are both solids and can be merged into one.
-
[my preferred method, which only takes a minute to do] Make a group from the two selected roof-groups, edit that new group, and then select all, then choose intersect with context.
Next select and then explode the two nested roof-groups, and manually erase the unwanted geometry.
Select all geometry and assign it to Layer0 - the exploding can mess with layers...
This alternative solution requires no 'making-solid', and leaves the single skin parts intact...
Remember to rename/relayer the new group as desired...
-
-
Thank you.
Yes the plugin I'm using is yours. Great plugin btw.
I went back and did the same procedure in 2017 and do not get that message and upon running solidsolver, it says there are 2 coplnar planes, do you wish to remove them and I check ok and it turns into a solid and can thus be combined with another one using the same process. As you can see from the attached, it did create a plane on the underneath side as you were described was needed.
???
-
My solution 2. is still my recommended fix...
Also you don't need Pro to do it ! -
TIG, I do understand your fix and I will have to do that. What I don't understand is why it worked differently in 2017 than it does in 2018. If that is something that SU changed in the programming, then so be it. If it is something I'm doing different, then I would like to know what that is.
-
It might well be because of the changes to the way SketchUp references objects with IDs.
This has recently changed.
Frankly I think that the present result us as it should be !
Advertisement