Just a note.. according to the investigation
the .obj files that you reported earlier this year all contained
corrupted meshes, meaning for example triangles with only one or two
vertices, or duplicated vertices, which eventually results in UV and
polynode trouble after bad triangles are rejected. The
application that's generating these is wrong. Obviously you've
found that the importer in XSI 4.2 was dealing better with these
corrupted meshes, although not necessarily by design... The
goal of the new importer in XSI 5.x was to address severe performance
and memory management issues loading large meshes. Additional
hardening of the importer against corrupted meshes has been done in
5.1. I think this whole made-up story about good programmer
making the old one and a bad one making the new one is totally
inappropriate.. the new importer in 5.x is helping a lot of
clients who couldn't load their .obj meshes at all with 4.2.
-----Original Message-----
From: Rainer Schmidt
Posted To: xsi
Subject: RE: 5.1 Download now
Yhats true but if you encounter that with literally every second mesh you
touch, then that makes you wonder. I had a problem with .obj in 5.0 which
then was quickly fixed with the 5.0.1 release. So I am anticipointed now
8-).
Besides that... there is such a thing as error free software. But there is a
price attached with it. Along the lines of: If failure is not an option,
success becomes immensely expensive. And I bet there is no QA budget along
that line in the 3D community. So, you have to flexible and fix things as
you go along. In the financial services industry, specially in the risk
management area, software standards are along the mentioned lines. And we
all pay for it ;-).
Rainer
> --- Ursprüngliche Nachricht ---
> Von: "kim aldis" <kim(at)cg-soup.com>
> Datum: Sun, 2 Apr 2006 16:51:12 +0100
> > Sent: 02-April-2006 15:49
> > But to expand a tiny bit on 'shoddy'... If it
> > is posible that I can crash an application in a way that it
> > does not even say goodbye or if I can lock it up with a data
> > import then that module has been implemented shoddy.
>
> Personally I don't feel that that has to be the case. It may be the case
> but
> the nature of the beast is that it's unpredictable and some things simply
> cannot be foreseen, even with the best will in the world. It's perfectly
> possibly that a well designed and well implemented piece of software could
> die or lock up, it happens all the time.