[Plugin][WIP][OpenSource] Bezier Surface
-
@unknownuser said:
But the one that cause problems, that not publicly available? I was hoping to be able to inspect it and then see if I could reach out to the author and ask that he can release a new version that doesn't conflict.
Components on face by CPlassais
-
@thomthom said:
Got a wireframe of that mesh? I'm curious to what makes out the difference. (I'm wondering if my SUbD tool might address that.)
the render mesh looks like this:
the tangent one has all facets at equal angles/sizes whereas the g3 blend starts off mellower then gradually tightens..
at the highest end, this stuff only really matters if you're designing surfaces for cars etc but at the midTOlow end, some of it can & should trickle down into sketchup/architecture/furniture/etc.
-
@pilou said:
Components on face by CPlassais
That is using the exact code that smartdrop.rb uses - which is bugged and breaks the Ruby API.
class Sketchup;;Group def definition return(entities[0].parent) end end
I'm about to take a weeks vacation so I'll be off the grid. Pilou, since you worked with him, care to follow up with him on the issue? Request that he updates his extension to not modify the Ruby API?
-
No problem I will send him this advice!
-
Hi Thomthom and guys, can anyone move a point with a fixed measurement?
Each time I try to move say 2m to the side, the measurement box assumes I want 2 subdivisions and the SU bugsplats. Is it only me and maybe a plugin clash or does it happen to more users?
I think subdivision is really important to be able to input quickly, but distance is even more. What would you feel about introducing subdivisions as "2s" while "2" would be used for units?
(Thomthom - I submited the bugsplats.)
What a wonderful plugin this is! Such an intuitive way of modeling surfaces!
Thanks,
João
-
Yes for me using the Gizmo defaults to subdivisions and will bug splat if you try 2.
However, the Move tool works properly with measurements, including 2m. -
I think this will become the skinning plugin of choice for bodywork and such very quickly.
For example: You know how fiddly it can be to set up the sections to make a nice curviloft helicopter, or a smooth hood for you car etc etc
This Huey skin took no time at all, it's all done by eye, a little more effort or a framework to work to and you would have lovely clean skins.
-
Another brilliant plugin ThomThom!!! Great!!!
-
Another situation where surface is brilliant.
The ten minute custom shaped bathtub.
The bath itself and it's edge are a solid skin, theoretically printable. -
@box said:
Yes for me using the Gizmo defaults to subdivisions and will bug splat if you try 2.
However, the Move tool works properly with measurements, including 2m.Yes I noticed that move works...
Shame also that we can't scale to 0.
Those are the only things that make this imperfect, otherwise the tool is GORGEOUS to work with!
-
@box said:
Another situation where surface is brilliant.
The ten minute custom shaped bathtub.
The bath itself and it's edge are a solid skin, theoretically printable.I could do that in say, 20 min. I can just send it to Box and open the file when it comes back done
-
looking good.
-
@thomthom said:
I'm about to take a weeks vacation so I'll be off the grid.
I wish you a pleasant and relaxing holiday!
-
What a tub!
-
But, will it blend?
-
@pbacot said:
I could do that in say, 20 min. I can just send it to Box and open the file when it comes back done
Got a patch view of that?
-
@tt_su said:
Got a patch view of that?
I assume you are asking me.
No I don't have the original as you need to explode it to work on it.
It would have looked very similar to this before I trimmed the rim and gave it a follow me profile. It's only a few moves to create it, move the center down, scale a few points lift a bit here and there.....
-
thank you very much for sharing this very fun tool.
a consultation:
as add tripatch tool is used? -
@jql said:
(Thomthom - I submited the bugsplats.)
Which platform and what OS? Did you mention Bezier Surface in the BugSplats?
-
@jql said:
I think subdivision is really important to be able to input quickly, but distance is even more. What would you feel about introducing subdivisions as "2s" while "2" would be used for units?
That sounds like a good idea. Filing feature request.
Advertisement