Hi mdesign,

re:
> ... but why sweep2 in MoI has higher CP count than multiply CP of surrounding edges? Exact setting on
> sweep in MoI also should give similar effect to network exact. Isn`t it? Why one row is higher?

I'm not seeing any difference over here - the profile curves have 6 control points:



Sweep surface using those profile curves also has 6 control points in that direction:



- Michael

But rail edges should have 4 vertical rows only and there is a lot more in your example. You have not visible control points over surfaces so it`s not visible that surface edges are 4 CP only.

I had it a bit different on my printscreens because I`ve set rails and profiles as inverted to your example but it is not changing anything in that example. Because in MoI profiles are always as low as the edge/curve count is and rail rows are much more dense. Why this happens?

Rhino sweep (6 horizontal rows * 4 vertical rows):


MoI sweep (only profile rows are ok and rail row are denser):


Is this intentional or is it a bug?

Hi mdesign, it's intentional - in MoI the result in the rails direction is going through an adaptive fitting process. In some limited special cases it could be possible to not do that if the conditions are just right. I think in Rhino there's some kind of "simple sweep" option for doing that. MoI does not have that function currently.

- Michael

That`s ok because in the other side Rhino has NetworkSrf with more dense mesh and there is no option to make it lower like in MoI.

It`s a quite funny because in Rhino I should omit NetworkSrf If I would like have lower mesh and in MoI I should use Network (exact) if I want lower mesh. Sweeps mirror that situation. Because in Rhino I will get lower sweep than in Moi :)

It`s a new info for me because I`ve thought I will have same effect on both and there is no difference where I will create sweep and where I will create network.

Thanks for answer.

Cheers

Edit: In attachment I showed networksrf in Rhino (very dense without any options)