bit of a bold statement isn't it?
while 5.x import/export of objs might not be working for you (I
personally never had a problem with it, infact I had more issues with
4.2's'), you should also bear in mind that .obj's guidelines aren't
exactly set in stone, and different vendors often have different ideas
about how it should work.
I could present you with files that will crash LW and not XSI, or that
will crash XSI but not Maya, or bring down both maya and XSI but work in LW.
What about pulling off a proper stunt, and name both developers and also
let us know what you think they did wrong in handling the format?
After all it's not rocket science, and to replace 4.2's (because we had
problem with THAT one), Phil Barrenger here wrote an obj I/O in python
in maybe 2 days, you might want to do the same to at least show the
developers how you'd like it done as you seem to know more then the
people in Soft about dev work and file format handling.
I know this doesn't help, but I just find it really upsetting when
people lay down such blanket statements, especially when the attack
veers toward personal and calls out a developer on "having done a shoddy
job", when the importer is actually much more solid for some of us.
You might one day find out that this also applies to other softwares and
formats in other fields by the way; like when you'll try to load an exr
that's not written bottom to top in shake, even when that exr opens just
fine in the FXtree, FrameCycler, DF etc.
Welcome to the world of open(to interpretation) standards.
******************************
| Raffaele Fragapane |
| Rising Sun Pictures |
| "Remember, TD is for TopDog" |
******************************
Rainer Schmidt wrote:
There is also a story
behind that... The programmer who wrote the 4.2 obj importer/exporter was
not utilized to write the new one and the guy who did it did a shoddy job.
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
