Show messages:
1-5
6-25
26-45
46-65
66-68
From: Michael Gibson
Hi Brian, the inputs for Network go like this:
0: Object list - U curves
1: Object list - V curves
2: List of curve orientation values - U orientations, each has a "flipped" bool value and a "seam" parameter value.
3: List of curve orientation values - V orientations
4: String - Mode, one of "normal", "lighter", "custom", "uniform"
5: number - Custom tolerance, Fitting tolerance to use when mode = "custom"
6: int - Uniform Num Points, Number of interior points to use when mode = "uniform".
If you pile up all the curves in input 0 and leave input 1 blank and the orientation lists blank it will automatically sort the curves into separate U and V lists and generate the orientations.
- Michael
From: bemfarmer
Thank you very much Michael.
Separate u v inputs, availability seems nice.
Does this have any speed advantage?
I wonder a bit about what "List of curve orientation values means and how it works.
But probably do not need it.
Saw something about coons patch also...
- Brian
From: Michael Gibson
Hi Brian,
re:
> Does this have any speed advantage?
Not much speed advantage, but if you already know which set a curve is supposed to be in if you separate them then you won't run the risk of the automatic sorter making a mistake in classifying them.
re:
> I wonder a bit about what "List of curve orientation values means and how it works.
> But probably do not need it.
They will be created automatically for you if you leave it blank. It stores whether a curve should be flipped from its natural direction when used in the network and where the closing seam point of a closed curve should be switched to from its natural seam when used in the network.
> Saw something about coons patch also...
A Coons patch is when you have just 4 boundary curves, there is an "exact" option that can be used in this case.
- MIchael
Show messages:
1-5
6-25
26-45
46-65
66-68
