Re: 5.1 Download now

["Tim Leydecker" <BauerOink(at)gmx.de>]

> I read them with V4.2 and that works. However, the .xsi exchange creates
> other problems... In the moment I cannot win without a pretty weird
> application chain through which I have to pump and fiddle every second mesh
> I am dealing with.

So import does work for version 4.2? Why would you
want to export as *.xsi then instead of saving a default
format *.scn and loading that into the 5.01/5.1version?

I don´t get it but go ahead. As long as it works at least.

Cheers

tim



----- Original Message ----- 
From: "Rainer Schmidt" <itrisk(at)gmx.net>
To: <XSI(at)Softimage.COM>
Sent: Sunday, April 02, 2006 4:48 PM
Subject: Re: 5.1 Download now


> "bit of a bold statement isn't it?"
> Yup, not politically correct. But consent usually rises out of dialog and
> controversy. Your points are well made and I do not dissagree. 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. I'd wish it works
> like the rest of the tool with which I have ZERO, NADA, NONE problems
> whatsoever. Unlike other apps I pile up left and right on my way. Specially
> the modeler... you can only pry that one out of my dead hands. And the
> FX-Tree... and MR/Rendertree... and... you get the point.
>
> Only in case of the few hundred .obj I imported and have to import into XSI
> I have experienced majorly three variations of problems which I will not
> repeat as I already sound like a broken record. I dropped those problems
> into the support hotline as severe and all I get for month now is that
> 'someone' is working on it, without results (yet).
>
> I really agree that V5 is a major step forward. But for me personally, I
> have lost three (small) jobs because it took me wayyyyy to long to bend the
> .obj straight. I am refering to the corrupted UV problem, and the inability
> to automatically assign textures to the objects while reading the .mtl file.
> All known issues, nothing fixed, and no replies, no estimations.
>
> I read them with V4.2 and that works. However, the .xsi exchange creates
> other problems... In the moment I cannot win without a pretty weird
> application chain through which I have to pump and fiddle every second mesh
> I am dealing with.
>
> Enough... point made. When the weather is getting a bit better I'll take my
> plane up to Montreal and aquire a status in person ;-).
>
> Now I have to go and play with .obj again.... grrrrrrrrrrrrrrrr
>
> Rainer
>
>
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
> unsubscribe xsi


---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi