News:

 

Topic: Nvil is slow.  (Read 22008 times)

0 Members and 1 Guest are viewing this topic.

  • Posts: 1697
  • Administrator
  • Polygon
    • http://samardac.com/
March 13, 2014, 05:28:13 pm
People,
I just made some little test.
This model has 74 700 polys, I toggle subdevision (3 level) in Nvil, Cinema 4d and Modo.

Nvil:
Subdivide - 1 minute
Unsubdivide - 40 sec

Cinema 4D:
Subdivide - 3 sec
Unsubdivide - 1 sec

Modo:
Subdivide - 1 sec
Unsubdivide - 1 sec

As you can see the result of Nvil is horrible :(
« Last Edit: March 13, 2014, 05:30:25 pm by samardac »
Portfolio: www.samardac.com

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
March 13, 2014, 05:45:25 pm
Until fixed,  I suggest only smoothing the areas you are working on and not the entire scene.  Single objects will be much faster.

  • No avatar
  • Posts: 306
  • Triangle
March 13, 2014, 06:12:12 pm
Modo, O_o, seriously ?!

  • Posts: 546
  • Administrator
  • Polygon
March 13, 2014, 07:36:49 pm
ya pretty much instant in maya as well about a second for 100k polys

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
March 13, 2014, 08:01:25 pm
Just so you guys know.


1x subdivision multiplies the polycount by x4.

2x subdivisions is x8

By default, Nvil uses 2x subdivision. 


So a 100,000k mesh is going to be 800k. 

  • No avatar
  • Posts: 3
  • Vertex
March 13, 2014, 08:16:03 pm
Modo, O_o, seriously ?!

Are you disgusted by Modo? Not sure what this reaction means.

  • No avatar
  • Posts: 306
  • Triangle
March 13, 2014, 08:57:11 pm
I did test
xsi 240 mil. tris
cinema 212 mil. tris
3ds max 160 mil. tris
maya 120 mil. tris
bledner 30 mil.tris ( edit mode object 20 000 polygons)
modo 23 mil. tris or 70 item mesh, 4 polygons in 1 item

i 3 year working  in modo, and I'm very sorry that I spent time on it

  • Posts: 1697
  • Administrator
  • Polygon
    • http://samardac.com/
March 14, 2014, 07:51:03 am
I made another test.
I have this detail of model that has 131k polys.

And open/save it in diffrent applications.


Nvil
Open - 3 MIN
Save  -20 sec

Cinema
Open - 2 sec
Save - 1 sec


Modo
Open - 3 sec
Save - 3 sec

As you can see Nvil also have horrible result :(

Also working with this 131k model is VERY hard, becouse everything is very slow....

Portfolio: www.samardac.com

  • Posts: 1697
  • Administrator
  • Polygon
    • http://samardac.com/
March 14, 2014, 08:04:34 am
This is the detail that I used for test, you can try it by your self...
http://we.tl/YgZHGjag2j
Portfolio: www.samardac.com

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
March 14, 2014, 08:32:58 am
Honestly,  You could reduce the polycount of that piece by half.


I know it is off topic from performance of Nvil which could certainly use a boost in performance.  As a general rule, this level of detail is only used at final rendertime.  In a production pipeline they would ask you to model at a lower resolution with the expectation to smooth later. 

Look at some wireframes of some famous breakdowns and you will see that they are working at a much lower resolution.  Your current assets would not even benefit from being smoothed.


  • Posts: 1697
  • Administrator
  • Polygon
    • http://samardac.com/
March 14, 2014, 08:34:36 am
Also I made this test, using the same model of helicopter that has 74K polys.
I toggle subdevision level 2 in Nvil, Cinema 4d and MODO than looked at Task Manager.
Nvil consumes much more, 5 time more memory then Cinema 4D or Modo.
Check the screenshot...
Portfolio: www.samardac.com

  • Posts: 1697
  • Administrator
  • Polygon
    • http://samardac.com/
March 14, 2014, 08:37:20 am
Mason all that you say I know... But this topic is about perfomance not about topology...
And belive me I have reason to work with this detail in this subd level... And if you are very intrested why, tell me I 'll discribe you why...
« Last Edit: March 14, 2014, 08:39:15 am by samardac »
Portfolio: www.samardac.com

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
March 14, 2014, 08:48:58 am
You could model at half the resolution and have no loss in visible quality. I am only offering tips to speed up performance simply because Nvil may very well not get the performance boost you need until after you have finished the project.  My working habit is to model cylinders with only 8 spans, and smooth it once and then delete all edge loops that are not needed for beveled edges.

That leaves a cylinder with 16 spans and smooths perfectly and is still sharp.  I also use Ngons a lot, to keep topology light.

  • Posts: 1697
  • Administrator
  • Polygon
    • http://samardac.com/
March 14, 2014, 08:54:35 am
Mason, thanks for your tips but all that tips are just tips while Nvil remain very slow compare to the other applications... :(
Portfolio: www.samardac.com

  • Posts: 496
  • Triangle
March 14, 2014, 09:17:28 am
Well, it has been stressed enough, but I was curious so I, too, loaded the rotor model in different applications:

Maya: 1 sec
Blender: 5 sec
Silo: 10 sec
NVil: 3 min 25sec

Also the loop cut operation on this model in Nvil was slower than in Silo. In Silo it was instant and fluid. In Nvil it lagged a little.
« Last Edit: March 14, 2014, 09:33:44 am by Vaquero »