truespace likes to rape smoothing to hell and its not the most convertable format either. unfortunately trusepace -> pcs is the most stable means to create a pof right now. as im using max more theese days im starting to see the problem with that. the max plugin has some heirarchy limitations that im not to happy with. it cant deal with more than a couple layers of heirarchy. not to mention the shield bug.
im not too fond of 3ds format either. the format has various versions which are not all 100% cross compatable with eachother. i can never get truespace 3ds import to work. and it has a way of screwing things up.
more format support is the way to go. the more formats you support, the bigger chance there is that theres one you can go through. i like to be able to set up all data chunks in the modeling program, so that reconversions can be made faster. in reality id rather not go through a converter/editor at all, but instead save as pof from the modeling program. thats why i like the max plugin, despite its countless flaws.

of modeling programs have built in script interpreters, max and truespace has em, not sure about blender or sketchup. porting pof output code to those script systems might be a good idea. i want to learn more about file i/o and model representation, and making a converter sounds like a way to do both