Nvil is slow.

Nvil become very slow if you have more than 200 000 polygons. I think it is the main problem of Nvil.... Pleas FIX it!

I have 670,000 polygons and 600 meshes without any lag.


Viewport performance is relevant to your Graphics Card as well.

I am using an Nvidia 460 card...pretty old  card and it is handling things just fine.

I will be stress testing the app with my current project which is going to be 2m polygons minimum.

https://www.youtube.com/watch?v=tP1PTf3fcno&feature=youtu.be
 

Mason,
I have NVIDIA GeForce GTX 560 Ti, I7 and 28 GB RAM.

I have to wait 2 minutes to subdivide this model (80 000 polys).

And it is impossible to make subdive of level 2.

I found Nvil very slow in this way...
I think there is 2 weakness of Nvil at this time:

1. It is slow.
2. Lack of Help and tutorials.

Also see:- http://voidworld.cmcproductions.co.uk/index.php/topic,2231.0.html

Steve,
I tried this and a lot of other stuff that was recommended to me in one of topic I started about this. It is that thread that you posted...
But nothing can solve the problem. It makes Nvil a bit faster but it still stay very slow...

Have you tried the 64bit version, that should help remove any bottle neck around memory.

http://joxi.ru/eqghU_3JTJAWdI60sOI

Yep, I also have no *32 in task manager, so it looks like I use 64 bit version. 

I just did a very random test on view performance with around 1 million polys. Ran on a laptop with 8GB RAM, i7 QuadCore @ 2.3 GHz, Nvidia Geforce GTX 675M.
View navigation was still ok. I tried a few different rendering options (hide edges on unselected, hide edges on view navigation, hide vertices/edges). But selection got really slow and unresponsive, even when just selecting objects. I didn't try selection options. Also the recognition of shortcuts didn't work that well anymore.

Because the test was so random, the video is quite long (~8min):
http://youtu.be/VU7VjGh-61o

[Edit]: Disabling 'Edit>>Options>>Reatime Selection Enabled' helps a bit.

Vaquero, that is what I'm saying about...
Also as I notice, if you have simple topology like you have in your test Nvil will more responsive. But if you have complex topology it will more slow. Like I say in my helicopter example it hase less polygons but topologн is complex and Nvil become slow.

Also, imagine you have to work always toggling subd... It is very hard... waiting for minutes to subdevide/unsudivide model...

I believe that the program which is based modeler, the first thing should be different good performance and flexibility

ya navigation is ok for me at 1m polys, but when i hit tab to toggle subd on and off, it takes forver