|
#1
|
|||
|
|||
|
.. hi there ,
I work with Rhino. An year ago my friend ( with serious hardware ) try to import this Rhino model ![]() into Max using Power Translator. Result was crash of Max - model becomes 20 000 000 faces and over. Is there some way for export ( except part by part meshing in Rhino ) ? regards
Last edited by popoff; 11-21-2007 at 03:15 AM. |
|
#2
|
|||
|
|||
|
Great model by the way.
Make sure to import into a single viewport (and set the display to wireframe). How is the model built? Is it a bunch of small surfaces?
__________________
David Gill President nPower Software |
|
#3
|
|||
|
|||
|
... thanx for your answer Dave ,
glad you like my model. This was my first Rhino model , created on analogy with AutoCAD way of modeling - so every part is "closed poly surface" ( solid in AutoCAD ). I export solids from AutoCAD manualy ( using my own method ) and result is not so bad even on high poly models : ![]() ![]() ... but on Rhino models there is a lot of problems - toooo much faces and smooth surfaces are replaced with flat ones ...
|
|
#4
|
|||
|
|||
|
Those are awesome images.
But are you having trouble importing this model? Have you tried importing into a single viewport? And import into a wireframe view. Also, you can set the 3GB switch with Microsoft.
__________________
David Gill President nPower Software |
|
#5
|
|||
|
|||
|
... those images are from 2001-2002 - I make manual export.
Wireframe looking like a spot ( because faces are tooo much ). I always work in "one view" mode in Max ( alt+W ) ... If you care I`ll post direct import from Rhino to Max( clay render ). There is problems with surfaces result of fillet command - they look so sharp and some strange peaks on the edge of surfaces ... Presently I dont combine Rhino with Max for high poly models ... |
|
#6
|
|||
|
|||
|
Hello.
Very nice images. Our translation team is handling models that are much more complex then this image. Please Can you give us your System specs? We are running Max 64bit with 8 gigs of ram. Another solution would be to save the model in several pieces. Then import each set of data and tessellate it to the desired resolution and finally----- Power Cache the parts. Repeat this process until the entire model is loaded. Power Cache was created to deal with a complex assembles memory overhead in a 32 bit OS. - -
Last edited by EricPinkel; 11-29-2007 at 07:07 AM. |
|
#7
|
|||
|
|||
|
... once again :
import was done from my friend in states - NOT FROM ME ...He works at 2x1.7AMD CPUs , 32b OS , 2x2GB RAM. There is the imported mesh : ![]() ... all edges done with fillet are very "sharp" also there is some strange peaks on the edges and across the surfaces ( seen when some material with specular levels is applied ) ... and this at 20 000 000 polygons ... |
|
#8
|
|||
|
|||
|
As I said before we have been dealing with models this big and larger. As far as the errors are concerned there are tools in Power Translator to handle all of the issues you pointed out in the image. Plus, with our Power translator Sewing technology you do not need even close to that many polygons to create the exterior hull of that image.
|
|
#9
|
|||
|
|||
|
Eric,
Could an option be added to the import dialog to Power Cache models as they import. In my head this would allow to release memory for models that are imported, and be beneficial for those of us still on 32bit systems. I would think this could be very beneficial when dealing with large assemblies. Or when dealing with files that contain lots of seperate models/parts. -Eric |
|
#10
|
|||
|
|||
|
Great Idea
Eric,
Great Idea! ![]() I'll ask Gary about it ![]() Eric |
|
#11
|
|||
|
|||
|
Actually, we have some similar ideas about the memory usage during import. I think we can make some substantial improvements in the next release.
__________________
David Gill President nPower Software |
|
#12
|
|||
|
|||
|
... memory managemennt is immportant for sure
.But bigger problem is number of faces - NURBS surfaces of Rhino meshed becomes millions of polygons. In AutoCAD situation is much , much better ... |
|
#13
|
|||
|
|||
|
If you are importing NURBS Surfaces and Solids then the number of polygons should be directly related to your Viewport Display and Rendering Approximation settings. 1) Verify you are importing NURBS objects and not polygon objects. 2) Import with Coarse settings and adjust as needed. 3) Cache the NURBS data or Extract to Mesh to speed up viewports and/or rendering.
-Eric |
|
#14
|
|||
|
|||
|
#15
|
|||
|
|||
|
... is there possibility to import this model from Rhino to Max result to be less than 5 000000 polygons ?
![]() ![]() ![]() regards |
![]() |
| Thread Tools | |
| Display Modes | |
|
|