XNurbs Rhino plugin is available!

We do not intend to embarrass anyone. However, some users may only be able to use XNurbs for some trivial cases, e.g., filling some simple holes. So we asked Vladimir Aleksic, an experienced designer, to develop tutorials and demos for XNurbs.

The following videos show how XNurbs creates surfaces. While the videos only demonstrate the most basic operation for XNurbs, once you understand how to operation XNurbs, then you can use XNurbs in thousands of different operations and XNurbs generates all surfaces in the same way: users just select curves or points, XNurbs will generate the smoothest NURBS surfaces that satisfy all the inputted constraints. Notice the surface quality generated by XNurbs.

Once users figure out how to setup the constraints, they will see the real applications of XNurbs.

The bottom surface of Jet Ski Hull

The top surfaces of a mouse

The side surfaces of a mouse

1 Like

Please watch the videos frame-by-frame.

1 Like

That appears to be correct. Analysis of the original pipe model shows that the brep edge normal deviations are quite high (above 0.5 degree) which is not a good starting point. Despite of that bad starting point, the 2 surfaces added by XNurbs are having acceptable edge normal deviation, below 0.2 degree.

@Stratosfear, i’ve had problems with my analysis tool too as the model was in meters. After adjusting the units to mm, i was able to analyze. Maybe this is the reason VSR fails too ?
_
c.

2 Likes

Yes, but you have to agree, only a few users would think that the checkbox unter Topology would affect items listed under constraints without clicking on it. It is not a common UI style. It just stands like an option, not a constraint property. Therefore i suggested above DataGridView style UI, which also clears up the list under Contraints and makes room for additional, new future options :wink:

You probably had no time yet to play with Rhino’s analysis tools, designers often analyze visually compared to numeric eg. using _Emap to evaluate surface continuity. I agree that Rhinos _Zebra` is less useful because you cannot rotate the stripe direction. But doesn’t this leave room to enhance XNurbs and provide some new features to analyze during the preview ?

You might provide that with your preview material, for the user’s convenience.

No, Rhino’s success is based on user’s feedback. Please jump on the train and see the suggestions not as a critique but as a wish for further improvement.

_
c.

9 Likes

Conspiracy theories can be both interesting and/or maddening, as they often stem from some fact(s) combined with conjecture, mere speculation, filtered through a lens of potentially related or unrelated historical ancillary evidence. They are either fleshed-out and strengthened over time, or totally debunked via further input and evidence.

Consider:

  • XNurbs unusually shadowy status, personnel, available information, etc.

Registrant Contact

Name:

Organization:

Mailing Address: , Jiangsu CN

Phone:

Ext:

Fax:

Fax Ext:

https://whois.icann.org/en/lookup?name=Xnurbs.com

  • XNurbs front man’s now infamous tone. Authoritarian in nature? Simply an individual or cultural phenomenon, or the unavoidable foible of a product of state apparatuses?

  • XNurbs potential opportunity to embed into leading CAD seat count products - e.g., Solidworks, Rhino, and historical espionage. If state sponsored, one’s commercial virus protection may be inadequate, requiring professional forensic investigation to uncover mechanisms.

Speculate or debunk away….

1 Like

just found a strange bug using Xnurbs: after using it in a Rhino session, Isolate command turns into Hide: see following command history:

Command: XNurbs
Select curves and points
Select curves and points
Select curves and points
1 extrusion added to selection.
Command: Isolate
Command: _Undo
Undoing Hide

Restarting Rhino solves it.

Hm - Isolate really is an internal scripting of the Hide command (with buckets) so I can see where it’s coming from… but it is odd…

-Pascal

I think the tone of the discussion is drifting a little bit into unconstructive territory.

Sure, it feels like the @XNurbs representative frequently has an irritating attitude (especially the habit to assume from the beginning that users are too ignorant to use the software. This consistently happens in email conversations too), but who knows what the reason for this is.
It might be a misunderstanding due to cultural differences or for whatever other reason we can’t imagine.
Why don’t we just assume they are acting in good faith and only happen to fail to communicate effectively?

The software is potentially very, very useful.
It is not the miraculous “resolve-all-surfacing-problems” CAD wonder weapon they are selling it for, but it has unique qualities that easily resolve some situations that would require hours of modeling in traditional modelling style.
I already have used XNurbs in production work and I can’t wait to buy a license.

  • by the way @XNurbs: when will the software be available? -

So users: just imagine some thick non native speaker accent when you read @XNurbs posts, so it will be easier to forgive the condescending tone and imagine they mean no harm :grinning:

And @XNurbs: try to understand that a lot of users that are interested in your software are just as capable designers and modellers as @Vladimir_Aleksic and many of them, being architects, engineers, industrial designers etc. have quite a good understanding of technical problems in general.
And remember that what you call “trivial cases of filling holes” are often the most demanding and challenging problems in surfacing: resolving the tertiary surfaces in complex modeling topologies.

So cheer up everybody…

22 Likes

That was the problem. I keep assuming everyone is using the right units and tolerances.

@XNurbs can you please take a look at the attached file and give some advise? I am able to create a satisfying result, although it is a bit against the advise as shown in the manual.

fill-this.3dm (1.5 MB)

another test with xnurbs, I am sharing it so it might help others to explore

xnurbs-G2-fill-test.3dm (5.4 MB)

1 Like

@XNurbs if using Rhino’s history is not an option, is it maybe possible to enable point editing of points/curves during the preview?

and please consider to enable EMap preview. Shaded doesn’t give enough information during creation

1 Like

Hi,

Cool tests, attached is a version with adjusted input surfaces, no curve constraints.

test_fillet.3dm (525.7 KB)

regards.

1 Like

thanks, but is there any other way to figure out /solve these issues? I don’t have VSR plugin. Would be nice if XNurbs could indicate where the issues are. @clement do you plan on sharing/releasing your plugin? I think the issues came from going back and forward between SW and Rhino, but not sure.

Well in this case I would: 1. check that you are not matching to weighted point surfaces
2. make sure all inputs are tangent to each other

When you control for that xnurbs works no problem in this case without any need for additional curve constraints.

Thanks for the model.

While you could generate a satisfying result, we are treating it as a XNurbs bug. A fix should be available next week.

We will discuss it with Rhino. So please give us a couple of days.

Yes, but I need a bit of freetime to streamline it… :wink:

_
c.

Could you elaborate on the nature of the “normal problem”?
Are you referring to the different UV directions between surfaces?

When I check @Gijs 's example file the surface normals are perfectly fine.
There are some inconsistencies in the uv directions which can be manually fixed in Rhino, but this doesn’t seem to have any influence whatsoever on if or how XNurbs works.

Am I missing something?

By the way, this case is a perfect example that XNurbs sometimes behaves inconsistently (as I reported via email, but having difficulty to supply a repeatable example):
depending on the sequence of selection the same combination of boundary conditions and slider adjustments may in one particular case succeed, while in virtually all others it leads to no surface.
Two exactly identical combination of boundary conditions and adjustments, two different results.
Sometimes jigglig back and forth with for instance the"relax precision" slider can make a surface magically appear.

Norbert

Hi Vladimir.
What are your adjustments to the input surfaces?

Thanks, Norbert

@Vladimir_Aleksic
Nevermind, I found the problem with weighted fillet surfaces in @Gijs 's file.

1 Like