Jump to content

NURMS subdivistion and turbosmooth


isaac_cm
 Share

Recommended Posts

Not sure I get the question correctly.... You should use turbosmooth or meshsmooth when you need a smoot model.. Any time you model something soft.. A human, clothing, pieces of soft furniture like chairs or beds.. usefull for aircraft, cars, trains and others as well

 

NURMS is the method used to smooth the thing, there is also classic, try both to see wich one is better for your needs.

 

Only thing to remember when using turbosmooth: try keeping things Quads.

Link to comment
Share on other sites

Turbosmooth is newer (though now again old) technology, so you should use turbosmooth. Good to know is that not all options from meshsmooth are included in turbosmooth, so in real rare cases you should use meshsmooth.

 

Nurms don't use that, it is not handy.

Link to comment
Share on other sites

Turbosmooth is a version of Meshsmooth that has been simplified, for speed (hence the "Turbo") Meshsmooth has the ability to "Weight" smoothing, as well as many more features, it is my understanding that many people used Meshsmooth and never needed these features. Meshsmooth has some very cool options like "keep faces convex" which will work if things are not quads, where Turbosmooth breaks down. Although now with Max 2010 there are new tools to make this case less of a problem.

 

NURMS are not NURBS (which are surfaces), NURMS are the default smoothing type in both Meshsmooth and I believe Turbosmooth. I don't know what NURMS stands for, but if we use the NURBS model it might be "Non-Uniform Rational Mesh Smooth/Spline" or something like that.

 

Hope this helps,

 

-Nils

Link to comment
Share on other sites

Thanks all, I would say you clear it specially NilsN answer, I was asking this because I notice turbo smooth is eating alot of memory if I did not collapse the stack while NURMS is not and also gives me freedom to go back to low poly

 

Personally I see the stack feature of MAX is a not very helpful since putting alot of modifiers there is taking alot or ram and if you need to go back and change something in a prior modifier the next modifier will break the model !!. I experince this problem many times so I alwayes collapse which make stack is kind of weak feature!!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...