Or you could have simply clicked the Help button on the xNURBS toolbar.
That is true, and you will find that info in the Rhino documentation and tutorials.
E.g. to understand in Rhino Loft, Sweep, Patch and more.
You should learn this first.
I don’t agree that it is because of no audio.
Because a surface can’t be tangent to a point (e.g.).
Good you know about XYZ (not meant sarcastic).
You will learn about UVN when you go through the basics.
You won’t find a tool which frees you from learning and understanding.
Even using a hammer requires some knowledge in physics, and some training.
xNURBS is not a standalone tool.
As you know it is a Rhino Plugin.
You need some basic knowledge!
The xNURBS doc can’t explain all from ground up.
And what do you miss now?
Why should it?
If you would know what trimmed/untrimmed is, you wouldn’t ask.
You will find detailed explanations of this in the Rhino doc and tutorials.
E.g. by shortening the curve.
Creating the wing is a 1 minute task.
When you know some basics - you don’t have to be experienced to do it.
I don’t think a voiceover will help.
There are no xNURBS surfaces.
The surfaces created with xNURBS are just NURBS surfaces.
See xNURBS documentation…
No video necessary.
You need to know the nature of NURBS surfaces!
You blame Rhino and xNURBS docs instead of learning.
You look for a tool that ‘just works’ without learning anything.
You ignore helpful answers.
Isn’t it you who throws mud?
Relax, go through a basic Rhino tutorial, then you are many steps in the right direction.
Because Mr. xNURBS learned, thought, researched, and invested time in the XNKernel.
And I’m sure he didn’t blame Microsoft for the C++ docs.
He learned the basics first; what is a variable, data types, a loop etc., and of course a lot of math knowledge is required.
Math knowledge starts in primary school
We all accept?
Better speak for yourself only.
xNURBS is not a “work in progress” program, it is ready in it’s current stage.
As with nearly all software, there is always room for enhancement.
xNURBS was very usable from the beginning on.
And it evolves - see the enhancements in V2.
In no way it can be described as “a work in progress” software.
That’s very true!
Perhaps it is a good idea to discuss all the basic stuff in a separate thread?