![]() For example fences with a lot of holes are difficult to mesh at Rhino, so for rendering I premesh it per MoI. ![]() Also MoI is using multicore, so it’s quite fast, not like Rhino where it needs ages some times. Also MoI do what I say if I set a divide larger than … than it do it. So for example, fillets can be a single row of polygons. MoI can give very clean result for low poly meshes where Rhino create ugly kinks. Rhino is a great tool for universal pro 3D usage, only the display pipeline is out-dated, not ready for the GPU power of modern cards.īest you try the MoI demo. I wished, there would be an alternative display pipeline for the high end user, for example special optimized for Quadro cards only. Looks like hobbyist, semi-pro user or lightwight pro user are in the main focus of deveoplment. It’s a pity that there is no interest at the McNeel side to provide the best graphic power for pro users and high end usage. I’m very curious how good a K4000 acts, because I’m looking for more graphic card memory always. So, there was no big difference between the Quadro 4000 and the GTX285, except the price. But this mode is quite uninteresting, since Rhino is a NURBS modeller. If only meshes are shown, than the Q4000 is three times faster, because there is pure OpenGL performance needed. 0% … 25% faster than the GTX285 for display modes with lines/NURBS. It’s a bad situation, we have a NURBS modeller with a display problem with NURBS data. The times are for full NURBS/curves 20s, no curves 8s and only meshes 4s (_testmaxspeed). And if you extract the render mesh and delete the curves/NURBS, than you get high speed and full GPU usage. You can test it, a display mode where curves and iso-curves are disabled is much faster. Mesh creation and display - two basic features, at the moment not millions of polygons are not a problem for the display, also at Rhino, the problem are the NURBS data and curves. The same problem can be found at the bike model, the initial shading is horrible slow. I’m curious how long we need to wait for this stable speed and support of modern cards.īut also you list an other problem - 2 minutes for shading. Interesting is, if I open the model per MoI3D, than the display is fast like expected. The problem seems to be some models with complex internal data. The GTX285 doe’s a quite good job, better than the most new cards. I’ve looked at other articles about video cards on the forum but not found any definitive answers.Īny thoughts, ideas, or information that would provide resolution?Ģ27MB isn’t so big, my files are often in this size or bigger. Is it just me? is there something I can do with settings? ![]() I see others with comparable setups getting high frame rates with models that have millions of polygon using 3ds max or Maya. The qudro is set to ‘workstation app - dynamic streaming’, and Rhino OpenGL is set to use accelerated hardware, redraw scene when view-ports are exposed, 4x AA, and low anisotropic filtering.Īm I just expecting to much? I get great marks on SpecView perf. I Have a Core Quad processor over-clocked to 3.0gh, 8G ram, and the Quadro, all running rhino 5.5 on windows 7. It has definitely improved things, but with complex models such as this 222mb Lamborghini, from grab-cad (link below), or others I have made myself, view ports are very slow and chopy. I expected that it would allow me to handle relatively complex model without any stuttering or slowness on the view-ports.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |