XSI 7.0's crosswalk exporter's COLLADA not working

Hi,
I used XSI 7.0 and its crosswalk exporter(ver3.0) and exported a model in Collada(1.4.1) format. When I import this Collada file to Unity it complains that the file is corrupted. Has anyone seen this before? Does anyone know how tox it?

To test whether Unity or XSI was causing the problem I also tried to import dae file that came with Nvidia's FX Composer 2.5. The result was same,,,Unity would complain the file is corrupted.

So I'm more inclined to think Unity can't do Collada or is very picky about version or Collada schema. Any info regarding this stuff would be appreciated too-.

Work around is to export model in FBX but FBX doesn't do subdivision and I actually would like it in my model.

Thanks in advance!

 

Ok, just for hell of it, I downloaded blender, created a simple mesh, and exported as Collada file. And to no surprise Unity didn't import Collada again. Is Collada supported at all in Unity???

 

I don't think so, but you wouldn't be able to use subdivision in Unity anyway. Only plain polygon meshes are supported. (You can use subdivision in Blender and save as a Blender file, and when importing into Unity, the subdivision gets baked to a normal mesh. Which is to say, the Blender FBX exporter bakes it.)

--Eric

 

The Unity manual says dae files are supported, but I suspect that Unity relies on readers built-in to the FBX SDK for some formats and it seems some of them aren't very robust. I had some OBJ files that were importable by some 3D apps but not Unity, and then when I tried running them through the FBX converter and had a similar failure. (and I seem to recall seeing some problems with OBJ and Collada readers mentioned in the FBX forums)

 

Great info, guys. Thanks!

 

Use Crosswalk and export to FBX from XSI... I haven't had time or willingness to upgrade to 7.5 yet so I'm not sure if that works or not. I know Crosswalk 3.1 works and that Crosswalk 3.11 does not. I did report that to the Unity folks. I haven't tried the latest version which is 3.2. I'm in the middle of production and I'm too afraid to screw with my setup. My findings so far:

XSI 7.0 w/ Crosswalk 3.0 = works with single UV set per object
XSI 7.0 w/ Crosswalk 3.1 = works with multiple UVs per object
XSI 7.0 w/ Crosswalk 3.11 = uvs break

Hope that helps some.

 

While I've been able to export static meshes with multiple UV sets using Softimage 7.5 and 7.01 with Crosswalk 3.2, it appears that there is a bug in 3.2's FBX exporter.

Have you tested 7.5 3.2 yet? Can you confirm a problem with Crosswalk 3.2?

 

The new Mod Tool comes with version 3.3 of Crosswalk, so a new download should be available for everyone else soon.

I can confirm that it fixed the distortion problems I was seeing with 3.2, but it doesn't seem to like animations to be stored on the Mixer.

 

This stuff just doesn't end. :cry:

Crosswalk 3.3 exports the animation correctly, but the UVs don't seem to work properly.

 

Gotta ask.. isn't it necessary to plot the animation before exporting anyway? :?:

 

Yes, assuming you used a control rig, you plot the animation back to the skeleton. But from there, you might want to put that animation onto the mixer. This is the step that 3.3 apparently doesn't support.

Right now I'm now going round and round trying to get the UVs working.

I'm beginning to understand why IT departments are reluctant to update software. Once you have a working pipeline (which I did with 7.01 and 3.11), don't mess with it!

 

Yep, especially with Autodesk updates I guess. I'm still on XSI 5.11 and with the Autodesk takeover it's gonna stay that way!

 

How else would you sell 1 / x year update contracts if users weren't force to updates due to errors.
How do you think does Daz survives (the never ending Carrara Bug story)

 

Here's a new bit of information I just learned re: Softimage and Crosswalk.

Although the software supports multiple UV sets for export, it doesn't for import. So if you are texturing your mesh in Modo and wish to animate it in Softimage or the Mod Tool, make sure it only has one UV set. You can always create additional UV sets before exporting it again.

 

i have xsi 7.0 and export to unity:

works:
- static models work and the 2 texture work

doens't work:

- envelopping sometime goes nuts. I saved my
envelopping map reply it and re-export it and
than it works

- but the nightmare is anamation. I importing
an scene and splitting up the animation doesn't really work. I logged the case to unity and the reported
back that the problem is with unity but i am stuck now.
I don't know what the real problems: is is the splitting up , is the constant interpolation,... ???

 

It took a bit of doing, but I got a working bit of animation out of the 7.5 Mod Tool, which includes Crosswalk 3.3. The character is from a Digital Tutors DVD. It has two UV sets. It's impossible to export a working version of this file with Softimage 7.5 and Crosswalk 3.2.

http://stuffwelike.com/islanddreamer/ModToolExport.html

Move the mouse to rotate around the object and use the mouse scroll wheel to zoom in and out.

Is the animation you're trying to import more complex than this?

 

Have you tried exporting to FBX in 7.5? Its time for me to update but I'm afraid to if I can't have multiple UVs and animation...

 

That's what I've been battling with. The Crosswalk 3.2 FBX exporter (the only one that works with 7.5) is broken when it comes to exporting animation.

I'd recommend you hold off on updating until 3.3 is released. It should be soon, given that it shipped with the Mod Tool last week.

 

and did you try out the 3.3? does it work for

- static models with 2 uv?
- does animation work?
- is the envelopping stabitily back?

 

Yes, but only with the Mod Tool. The standalone version for 7.5 isn't available yet.

 

Appears to be a bug...
To fix the missing uv problem when you try to export with Crosswalk, just remove all the textures of your model or apply a new empty shader. It worked for me. Import the model in unity and will see that the UVW projection continues there.

I am using XSI 7.0 64 bits and crosswalk 3.3.

However, I still having problems using crosswalk FBX. My UV sets appears to be damaged in some areas sometimes...

Melantonio

 

Hello

I dont want to be pedantic but I have written three or four posts about this topic without receiving even one reply
Honestly I was expecting some support :wink:

Everybody knows that FBX / COLLADA files format have still many issues :twisted:

I have developed games for years , at an amateur level
Never had a problem with I/O

I have been using Unity3d for some months

Great engine , out of question, but I can not cross my fingers anytime I have to load an animated model

Unity must support also a simple but rock solid file format , I suggested .ms3d, until all these issues with FBX and Collada have been fixed

 

would anyone be so kind and post Crosswalk 3.1 for download?

I can't find it anywhere

 

http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=13525184&linkID=12544121

I went hunting for ealier versions a while ago and came up with nuthin. You might try posting at The Area.

 

Looking for specifically 3.1 (the version right before 3.11)

 

According to the Softimage Crosswalk wiki, version 3.11 and 3.1 are the same except for Autodesk branding.

 

Autodesk announced at Siggraph that the next release of Crosswalk has been updated to FBX version 2010. I'm dreading to see what breaks now.

Below are the links for the Max and Maya updates:

http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=10775855

 

They're not the same version.
They rebranded / fixed bugs (and probably introduced new ones)

It's 3.1 we need.

 

the crosswalk 3.3 work well at getting animation from XSI to unity ...
I dont see that much people cpmplain about it right now , and well specially because XSI user here comparing to maya one are really a minority

Anyway i should still have teh 3.1 veriosn in my HD so if you want it i can maybe upload it somewhere

 

I would really appreciate that
What we're doing currently is export into Cheetah, and export to .fbx from there... less than ideal.

We will certainly give the 3.1 version a try if you manage to find and upload it