3d/2d Conversion Resolution

[RubenH]

1. For Separate object. Maybe in the obj info palette. (3d conv.)

2. A number instead of low-medium-high-vhigh. (3d conv.)

3. Maybe for the 2d conversion resolution an option when you apply the convert to polygons tool, and a number for the resolution.

Thanks in advance.

[ 12-06-2005, 11:15 PM: Message edited by: Mr. Gog ]

[RubenH]

Everyday i need more of this!

[islandmon]

There was a time when this was in fact the case ... then a decision was made to "optimize" the file structure by fixing the "smoothing" values to avoid the persistent overhead ( in the olde days when RAM was limited & expensive and VirtualMemory a twinkle in the programmers eye ), because the CPU did all the imaging, too.

This allowed the programmers to ignore complex object frequency array issues and let the code page out the results only as required thereby reducing file size exponentially.

As anyone who has experienced the massive overhead increase after importing a "converted" DXF mesh, soon discovers.

The trade-off is well worth the loss of casual User control over frequency modulations and replaces it with extremely limited specific "additional" procedures ...like adding a few more 3d vertices... which are a pain in the butt to implement.

Perhaps, it's time for NNA to revisit this important issue now that RAM,VM,CPU,GPU, and file storage limitations are less onerous.