[Bf-committers] small fix for import_3ds.py
Campbell Barton
cbarton at metavr.com
Tue May 2 04:47:00 CEST 2006
Hi Ed, are you sure you have the latest CVS, Im pretty sure this was
addressed a while back
The 1 remaining bug with 3ds import is that it messes UV coords up when
importing because of the zero index vertex order issue,
the sooner we use maxint or a flag for tri's the better.
- Cam
Ed Halley wrote:
>
> I think this one's for Campbell Barton, but in case anyone else wants
> to get it...
>
> On line 289 on my version of import_3ds.py script, it is catching
> AttributeError exceptions. It should instead (or in addition) catch
> ValueError exceptions at that point, and handle it similarly. I added
> that as an additional clause in my scratch copy and it let me proceed
> to load a test .3ds I needed. In case it's important, it was
> conflicting on a camera name, not a mesh object name.
>
> There's another object-naming bug which I've not fully tracked down,
> but is not too critical, but may be related. It appears off by a
> name, so that imported components get names that are meant for other
> components from the same .3ds file. An airplane may get two wings and
> a fuselage, but their names seem to be assigned off.
>
--
Campbell J Barton
133 Hope Street
Geelong West, Victoria 3218 Australia
URL: http://www.metavr.com
e-mail: cbarton at metavr.com
phone: AU (03) 5229 0241
More information about the Bf-committers
mailing list