Thank you for posting this video. I am only catching a scrap of this but it feels like something real and doable could come from using it and the explanation is not mysterious.
nothing like tryinng to get g3 continuity from 5 sided areas with nurbs patches. then again getting accurate class a surfaces from mesh modeling via smoothing, or subdiv can be frustrating. also the pesky vertices, that get knocked around if not careful.. easy to get caught in between the two ways of modeling. framing up job in advance as you mentioned is key.
Its very much helpful sir very thanks on you to clearing a doubt on 3D mesh & poly object nurbs etc etc on 3d world as i can modeling in autodesk maya & 3Ds max... also i'm an VFx & 3D animation student from India
Nice video! xD I am Designer mecahnical since more 10years and I use CATIA and SOlidworks in Nurms, after DAZ or 3DS MAX in MESH for make Render fantasy xD
Excellent presentation. What do you think of NURBS in Blender 2.8 ? I ask because Blender is free. You mentioned Rhino but Rhino is very expensive. Thank you.
I spend time to learn a 3d software until a day I find out it can not smooth because it polygon. I search and search then I find Rhino is NURBS which is different with mesh. There's a issue with Rhino is comeback and edit. You could not edit after boolean. I find again and now I fall in love with Fusion 360 T-spline. It perfect for make sphere, history edit and more.
thank you! great video, interesting to know the frenchies working for Renault and Citroën beside their skills still made ugly cars...Beauty is in the eyes of the beholder i get it but i can see beauty more than most. I was born on the planet beautyon. I love your video
Meshes are actually more precise than parametric models. Vertices, at the very least, are exact, while parametric models are approximation. They are smooth and nice, but they don't pass through correct points. Use what you like. I chose to use mesh (and I am nearly finished with a slicer that converts sliced mesh into multi point Beziers, to get the best of the both worlds).
Its not a question of one of the other. In CAD applications, you use NURBs for multiple reasons (e.g. you can visualize them without aliasing in any scaling). In the medical field e.g. to visualize the mesh of a bone or do some algorithmic manipulation like fill holes in a mesh of a bone, you use a polygonal mesh because this is whats generated from imaging modalities
@@fritzschnitzmueller3768 Thank you for your feedback. I don't understand what advantages are in visualizing without aliasing, but maybe that's just me. I mostly use Blender and it runs even on Raspberry. Mesh can be sliced and made into geographical map like curves, that is my point. We don't need curves for modelling. That's pain to do. For me. From slices parametric model can be rebuild precisely, the other way around approximately. I abandoned the slicer temporarily anyway, in favor of da Vinci's compass which, if CNC driven, will output lenses of higher accuracy than mill can.
@@kokeskokeskokes If u sample data from the real world(like a CT/MRI scanner, a 3D scanner) you dont get curves u get points or volumes, which you can triangulate or use contouring to get a triangulate mesh. It wouldnt make sense to convert them to NURBs because u cant win more precision by doing that. U can only lose
Most of CAD software have NURBS integrated today, but it is usually not their focus. For Rhino that is the selling point (NURBS modelling tool), and that is why it is easiest and most comfortable to use, and at the same time, it is relatively cheap. If you want to go open source, then Blender could be a possibility. If you are already using 3ds max their NURBS is not bad either. If you are a mechanical engineer (with a lot of money) then CATIA or similar software that includes static analysis is the answer. So I do not really recommend any other software when it comes to NURBS...if NURBS modelling is your goal...but you can use most of them.
Another favorite of mine (by the same guy who originally programmed Rhino3D) is MoI3D. It is much cheaper, and easier to learn in the beginning. Rhino is a bit more robust, but may be overkill for your NURBs needs.
Really thank you for your unwavering implication of knowledge. I do have a question, if you allow - Why Mesh at all, if a NURBS with so many advantages. Greatings, Martin
in the medical field we generate meshes from Voxels (volume element), which is volume data or the 3D equivalent of a pixel(picture-element)) because this is what a CT-scanner or MRI-scanner provides. The meshes are generated from the voxel data with contouring algorithms like MarchingCubes or DualContouring. So if a doctor wants smooth-surfaces from the CT data(voxels, which look like minecraft) to do operation planning,he can only do that with polygonal meshes. Therefore many algorithms use polygonal meshes
