Re: Modo < -> XSI workflow...?

[Raffaele Fragapane <jaco(at)thejaco.com>]

there's been heaps of threads on quite a few forums and mailing lists 
about modo's issues with obj files.
not only it doesn't support some of the bolted-on additions to obj 
(which is nothing short of embarassing considering how simple and 
features lean obj is), it also has big issues exporting to obj, as it 
seems to randomly not to compact the vertex indices, creating illegal 
obj files or obj files with ghost points.

apparently 201 fixes most of this, and their "plays nice with others" 
claim is mostly a bunch of new import/export tools for geometry, UVs etc.

their lwo export/import is apparently a lot better (and I would hope so, 
considering the 2 daddies of LW founded the company), so you could want 
to go through some conversion app, even a cheap one like milkshape would 
probably do the trick (it supports dotXSI and I think it supports LWO as 
well)

******************************
|     Raffaele Fragapane       |
|     Rising Sun Pictures      |
| "Remember, TD is for TopDog" |
******************************



Erik wrote:

> HI Rainer,
>
> On Tue, 2005-08-30 at 08:40 -0400, Rainer Schmidt wrote: 
>  
>
> > Modo raises my blood pressure significantly...... To say the least.
> >    
>
> Ah...so I'm not the only one slowly turning purple ;-)
>
>  
>
> > I am 
> > having MASSIVE problems with modo and .obj files.
> > Create a simple cube with Silo and export it as .OBJ. 
> > XSI,ZBrush,BodyPaint can read it in all it's cubic glory. Modo crashes 
> > when you select it. .OBJ import problem. After tweaking my output 
> > parameters in ZBrush I could get some geometry into Modo. Not all. It 
> > has something to do with the inability to read something else than plain 
> > polygon files. Grouping or other fancy .OBJ format features kill Modo. 
> > The .OBJ output is equally limited and makes modo go HOME frequently on 
> > my machine. The .OBJ import/export module in modo is simply broken imho. 
> >    
>
> Correct. Any kind of hierarchy and composed objects immediately
> seriously break the entire import/export, often bringing Modo to a
> grinding halt/crash. I've done testing exporting to and importing
> from .lwo before but with Lightwave as the final target, not XSI. That
> went a lot better than going to .obj, hopefully with PO and it's native
> XSI plugin things should go a lot smoother, I'll send an update to the
> list as soon as I get some results with PO.
>
>  
>
> > I send all the files in question to Luxology and received a mail a few 
> > weeks ago with the information that it's being looked at.... I urge you, 
> > if possible, to do the same.
> >    
>
> I've seen people complain about this on the Modo forums as well so I
> guess it is a real problem that they know about, sadly it doesn't seem
> to be a real priority to fix it.
>
>  
>
> > I put modo next onto the shelf to my 
> > VUE5infinity package. The Software shelf for weekend experiments. I'll 
> > have another look at it when it matures.... 
> >    
>
> Haven't really got a choice at the moment, got a fair number of Mac-
> based artists that have all content natively in Modo and I REALLY need
> to get that content out.
>
>  
>
> > Modo supposedly has an 
> > update coming before the end of the year. And I am not talking about the 
> > 201 but a '103' fix. I hope they implement the file formats correctly 
> > till then.... Did you try LW and conversions from and into that format 
> > as bridge??? 
> >    
>
> Haven't tried LW as a bridge yet (or perhaps Polytrans using .lwo to go
> to XSI), but did a Modo -> LW conversion a while ago that went a lot
> smoother than the crappy .obj export/import.
>
> As soon as I get any real results (good or bad) I'll be sure to post
> them here.
>
> Cheers & thanks for the feedback,
>
> Erik
>
>
>
> ---
> 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