Originally Posted by StephanD
That's my point.
NC would gain in this since HASH stated X times in the last several years times that they won't be supporting polygons...Are you asking them to rewrite their whole software instead of someone developing an exporter???
How is hash writing an obj importer going to force them to rewrite thier whole software? It sounds like A:M users want polygons, but the developer of thier software give them options. So why does it fall to another company? If anything another A:M user should it, they would probably have a much better idea of what functionality is desirable in a hash spline exporter anyway.
|think exporters are an easy feature that wouldn't detract from other features.|
This isn't necessarily true, things like an obj or dxf exporter, sure pretty easy. But when you get into program specific file types all sorts of issues surface. Look at Modo's maya ascii exporter for example, it tends to mess up the scale pretty bad. Hash splines are a radically different geometry type from polygonal subd's. Writing an exporter on the Nevercenter end of things would require writing a ton of new code to go from polygons to hash splines, as I am guessing they don't have any existing hash splines floating around in the silo code.
I understand the pain you A:M users are feeling. Hash splines suck to model with and with the wide array of cheap subd modelers available you want some alternatives. Your best bet though would be to do an obj to hash spline converter on your own. As A:M users you will know what functionality is most desireable, and you don't have some axe to grind against polygons like the Hash team apparently does.