I cannot really comment on the Dynamo UI history, I am not part of that team. I do agree that some things there are clunky, but I would hope that this clunkiness goes away over time, with more people using it.
Still, already now you can do powerful things, which I will be evaluating over the next months.
Hi, GG. I think I understood the questions. For Alias users, we are playing with complex surfaces/structures (for example G2 fillet or draft surfaces with specific draft angles) which can not be done with the existing nodes and Design Scripts elements in Dynamo. But we know clearly how to build in Alias workflow. So if we can use Alias API library in Dynamo Python, we can fix all the issues.
Now the question is: Can we use Alias library in Dynamo Python scripting environment?
Thanks for the reply, GG,
Just want to emphasize again how important it is to have access to Alias libraries in Dynamo. As an Alias and Grasshopper user, I have to say Dynamo is a very promising tool for both car/product designers and 3D modelers, but unfortunately, its ability is still far from enough in actual project scenariosâŚ
Build a better connection between Alias and dynamo could be a practical solution. Just like Revit & Dynamo, Rhino & Dynamo. By the way, Dynamo Player in Alias 2021.2 is already a big step towards the direction we eagerly await.
Very appreciate your work and I have faith in Autodesk products. I believe very soon we car designers can finish all the 3D design tasks In Alias and donât have to switch back and forth between different softwares.
Hello!! I have a simple solution about two fillet from two curve. I use the node call âBy betweenCurvesâ But fillet have a lot of spans. and I canât fix this. So I use the other solution. The solution not really G2 fillet. But is approximate.
Sorry, My English is not good . I canât explain this. You can look my Dynamo capture
Hi,
Unfortunately, we donât have access to better fillet functionality from Alias inside of Dynamo yet (this is a known issue).
I am surprised that the result has so many spans. Could you share your Dynamo script here?
Thanks,
GG
Hi, Guys.
I dug a bit deeper into Skittâs solution. After I adjusted some nodes, now you can Fillet even when the original curves are not straight lines.
But, the blending curves created by the ''Curve.ByBlendBetweenCurves"do have too many Spans, which are not acceptable.
I tried to add a few more Nodes in the script to simplify the blending curves, the result is visually OK.
Anyway, If you need more precise constructions, Please go to my #2 solution in another comment.
The 2# solution: It is a little complicated, but it works.
With this solution, you can have high-quality fillet curves(5 degrees, 1 Span);
You can have more control over the shape of the fillet curves.
But there are still Bugs:
In this Solution, the original curves have to be 3 degrees. If they are not, you have to change some numbers in the scripts.
Hi, GG.
It is true that the curves created by ''Curve.ByBlendBetweenCurves" node.
I thought the problem should be caused by the data type conversion(when converting a 5-degree âNurbscurveâ to a âcurveâ).
I did some trial: when I convert âNurbscurvesâ(which is very clean, 5 degrees, 1 span) to ''curves", and then convert back to âNurbscurveâ again, the construction of the Nurbscurves changes a lot: got too many spans.
I also tried:
If I convert a 3 Degree Nurbscurve to curves and then convert back to Nurbscurve again, the result is Ok, the curve properties didnât change.
If I just manually increase the curve degree from 3 to 5 and donât do any other modifications, the result is also good, the result curves become 3 degrees but still have 1 span.
If I manually increase the curve degree from 3 to 5 and move some control points, and then do the same operation above. The result is bad, too many spans.
Draw 5-degree Nurbscurves directly in Alias, and then do the same operation above. The result is bad, too many spans.
You did some very cool stuff here! in fact, you implemented your own curve blend! Yes, what you write about the too many spans is true, but sadly makes sense from the Dynamo point of view. So far, Dynamo works similar to Rhino (and probably a lot of other, non Class A CAD systems): whenever something needs to be re-approximated, they do it by simply adding degree 3 spans, until the needed tolerance is reached.
I also totally get that our Alias users shouldnât have to re-implement the Alias math to get clean Nurbs tools in Dynamo (although, again, hats off for achieving that for curve blend!).
I will give my best to point out the importance of the availability of good Nurbs math in Dynamo to our product management team.