I should have explained that I found the XNurbsHelp.chm.
The installed folder path is:
C:\Program Files\Common Files\McNeel\Rhinoceros\5.0\Plug-ins\XNurbs for Rhino 5 (random ID)\
Or you could have simply clicked the Help button on the xNURBS toolbar.
so an explanation of the fundamental concepts is essential.
That is true, and you will find that info in the Rhino documentation and tutorials.
How can a surface be defined by a point?
E.g. to understand in Rhino Loft, Sweep, Patch and more.
Does that mean that a Rhino generated surface will butt against an XNurbs surface an Zebra will be happy? Somehow I think no.
(I have never trimmed a surface. I do not know how this affects the boundaries of that surface)
You should learn this first.
(there was no audio on the aerofoil example and I could not understand WHY he was doing the things he as doing)
I don’t agree that it is because of no audio.
With respect to the Dialog page inthe help file, I am not able to select CONTACT, TANGENT or CURVATURE in all cases. two are greyed out. I am not understanding why.
Because a surface can’t be tangent to a point (e.g.).
Keep U/V isocurves perpendicular… what is U and what is V… I know what X.Y and Z are.
Good you know about XYZ (not meant sarcastic).
You will learn about UVN when you go through the basics.
but I am a newb looking for a tool that saves me 3yrs of CAD school.
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 might be that tool so explain these things. Assume I am 4yo.
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.
U- and v-directions:
Every surface is roughly rectangular. Surfaces have three directions, u, v, and normal. You can display the u- and v-directions and the normal direction with the Dir command.
The u- and v-directions are like the weave of cloth or screen. The u-direction is indicated by the red arrow, and the v-direction is indicated by the green arrow. The normal direction is indicated by the white arrow. You can think of u-, v-, and normal-directions as corresponding to the x, y, and z of the surface.
And what do you miss now?
Trim the Generated Surface: Specify whether or not to trim the generated surface (Obviously, if you select Quad-Sided Surface , this option is ignored.). Not obvious. Why would it not trim a quad sided surface??
Why should it?
If you would know what trimmed/untrimmed is, you wouldn’t ask.
G0, G1, G2 … These are the boundaries as defined by curves of points I assume?
Perhaps a little explanation of what this is all about.
You will find detailed explanations of this in the Rhino doc and tutorials.
HOW do you make a partial curve that conforms EXACTLY to a full curve defined by the bounadry curves??? Need a video on that.
E.g. by shortening the curve.
For complex surfaces, e.g., the following aircraft wing tip, you may need to add more internal curves. This video needs to start with a blank document and needs step by step build WITH voiceover !! The video you have assumes too way too much knowledge.
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 also needs to be a chapter on Mixing Rhino generated surfaces with Xnurbes surfaces, or is it assumed that ALL surfaces in a model must be one or the other?
There are no xNURBS surfaces.
The surfaces created with xNURBS are just NURBS surfaces.
See xNURBS documentation…
XNurbs mainly handles open surfaces (like a sheet of paper). For closed surfaces, e.g., a cylinder that is closed in one parametric direction and a sphere that is closed in both parametric directions, you should split such a surface into two surfaces.
No video necessary.
You need to know the nature of NURBS surfaces!
Finally, please ignore the posts that are not polite. There are petty people and trolls in all forums that love to throw mud and will never create anything.
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.
You have created something, more than 99% of people will ever do
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
and we all accept that it is a work in progress
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.
and a great leap forward.
That’s very true!
Perhaps it is a good idea to discuss all the basic stuff in a separate thread?