This happens: I build a definition and at some point I need to do a two-track sweep. I have all the elements I need but the sweep behaves strangely. I bake the rails and the section and on Rhino the sweep works perfectly.
Because?
Succede questo: costruisco una definizione e ad un certo punto ho bisogno di fare uno sweep a due binari. Ho tutti gli elementi che mi servono ma lo sweep si comporta in modo strano. Faccio il bake dei binari e della sezione e su Rhino lo sweep funziona perfettamente.
I don’t know why Sweep 2 fails (in R6) but you can get the same result by using Pull Curve before Surface Split and then lofting the original and offset surfaces.
Ciao Carmen.
Il tuo è un problema particolare, e in generale la funzione sweep è tra le più ingannevoli da usare. È meno “assistita” che la controparte su rhino.
Quello che hai riscontrato te lo defenirei sostanzialmente un bug. In altre situazioni dovrebbe andare bene come avevi fatto tu: tieni la sezione vicino a dove
In questo caso, reparametrizza le due rotaie per risolvere:
Particular problem, generally sweep function is one of the most tricky to use. It is less aided than rhino counterpart.
I’d say this is a bug. In other situations it should be fine how it was used.
Reparametrizing the curves fix the problem.
Still it’s strange, the section curve is generated right on the seam of the rails, but it behaves like the seam was actually on the only other “discontinuity point” (G0) on the rails…
Edit: actually @Gambler found this solution 11hours ago in the italian forum.
I’m italian but i never visit the italian forum. The home page there… each scroll is a week … can’t really blame someone trying his luck here instead.
Guys, if you think it’s useful feel free to tag me…
Do you mean Italians talk too much or did I misunderstood? Anyways this is interesting. I am not even Italian but I have checked that discourse one or two times. Whole new worlds out there
… can’t really blame someone trying his luck here instead.
