Hello all,
I’ve just completed v0.1 of my dotXSI export script. Instead of losing all your lovely layers when exporting you can now bring them into xsi as their own mesh objects. Fun! 
Materials, Morphs, and UVs are not supported yet because I’ve only spent part of the day working on this script.
I’ll add that stuff soon, but if you can’t wait and end up doing it yourself then please repost the changes.
Please let me know about any problems.
Thanks,
_chip
Excellent Chip.
Thanks for working on this. I hope you don’t mind, but I plugged it in the XSIbase forums.
Looking forward to the future features.
Alrighty folks,
I did a complete rewrite as I realized a couple of things. The first being that dotXSI v3.6 is supposed to support tex coord information but doesn’t… even with files exported from XSI using one of the scripts available at their website! 
The second thing was that my original script design was horribly messy.
So yeah, I switched to dotXSI5 and made the script a lot easier to read and understand.
Basicallly everything is working but there is a bug when importing in XSI where it’s duplicating the objects. The first one will not be, but then it creates two of the next object in the file, three of the next, and so on until the last object in which you’ll have one for.
I’ve checked the output and everything is as it should be (that’s not where things are being duplicated), so at the moment I’m sorta lost.
Either way it’s no big deal if you don’t have a lot of separate objects and I because of all the positive encouragement I wanted to make sure the script was getting to people in a timely fashion.
So please download and give it a go. I would really like to know how things work for you and let me know what problems you run into.
so features at the moment:
-mesh
-UVs
-better file formatting
No materials or morphs yet.
I’ll be chasing bugs and trying to figure out the weird duplication that’s happening.
remember, it’s version 5 of dotXSI so you’ll need to use that importer and not the regular dotXSI… importer.
finally, it’s worth noting that if you have more than one texture class vmap (aka UVmap) it’ll only export the last one found for the layer.
I’d love to hear ideas on how to make this script better or friendlier.
When you get materials/textures (nothing procedural of course) working I need your paypal address!!!
Seriously, THAT would be fantastic! I haev a few Lightwave Objects and cant use them because the texture assignments are not transported into a mtl file. GAHHHH.
Rainer
w00t.
figured out the duplication bug. I was missing a closing bracket to end the shapes. So yeah everything works as intended now.
updated script has been uploaded.
Enjoy!
Materials/Textures coming right up!
Awesome. I wonder if when 201 comes out, there will be a way to script in Motion data and use the Modo Renderer for animations. I heard they wrote a script to render turn tables but we need more. Maybe you’ll be able to cook something up like that.
Well, you can basically export any value from XSI (that changes over time) as an FCurve so I dont see much of a problem animating in XSI and then writing a script to render, save, update, render, save, … and so on. I don’t want to write it though. I want modo to become the best modeler and UV editor ever (and also export to xsi).
Great work _PHO.
Anything that produces closer integration between my two favourite apps is great news as far as I’m concerned 
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.