Ogre Forums

AMAZING release from Softimage. We gonna get an updated exporter? That would be sexy!

As far as I'm aware the existing exporter should work fine - the enhancements in v5.0 don't require any changes to the way the exporting works. I've only just returned from holiday but noticed the new release (and yeah, there's some pretty awesome stuff in there) and will be asking SI about getting an updated version.

Sweet bro! Maya 7's additions aren't really impressive -- I'm sort of disappointed. There's 'new' stuff that should've been there years ago. (Wow edge-loop split? There's been a MEL script for that for years.) I'll check XSI 5's exporting capabilities soon as it comes out.

HI -- XSI user --

I tried to use the Ogre XSI exporter with XSI 5.0 demo and I have a error

ERROR : 2262 - This plug-in could not be loaded:
'<path: D:\Softimage\XSI_5.0_Foundation\Application\Plugins\OgreXSIExporter.dll>
'

The plugin works fine with the 4.2 version -> The plugin need some update or this is because I've only a demo of XSI ?

Thinks

I'm guessing it's the demo version not allowing exporters...

I ordered 5.0 and got my key in email a couple of days ago. I'll try to give this a shot tonight and confirm that it still works.

ok thanks - good news

No dice -- the exporter I think needs to be recompiled to use xsi5 libraries maybe...

Quick bump... crossing my fingers sinbad gets his copy of XSI 5 so he can make a new exporter. THX SINBAD U R TEH SEX!

I haven't received it yet, it's one of the things I have to follow up when I have time because my regular XSI 4.2 license expires this month anyway, so I'll have to get it renewed. If you have v5 yourself though, why not just try to recompile the exporter, the source is all there.

A word of warning to anyone using a GeForce Go5700 (laptop video).
XSI 5.0 doesn't seem to be compatible with that.
I've been talking to tech support for the past week trying to get it to work.

I had a problem with XSI 4.2 with my FX card, but new drivers were released a couple of days later which fixed it.

A quick recompile doesn't seem to work (for me). I mean, the DLL builds fine, and I can copy it into my Plugins directory, but it still won't load properly.

I could very likely be doing something wrong since I don't really do coding for our Project. Can anyone else who knows what they're doin with Visual Studio give it a shot?

I'm chasing SI for a license renewal and access to v5, they say they are still happy to continue supporting us so it shouldn't be too long hopefully.

Did you copy in all the dependencies as well as the exporter DLL? See the manual install notes in the readme for details.

I think I have it working. Try this version and make sure you also have the dependent Ogre files somewhere in your path.

Linky

Woot got it myself as well. Sinbad and Slicky you dudes clued me in... dependency dlls... duh. Added those into the XSI /bin dir and everything works cool. Thanks!

I've got access to XSI v5 now (downloading it as we speak - legally from Softimage I might add ) so 1.0.6 will feature an XSI v5 exporter as well as one for 4.2.

great! I'm seriously considering XSI as max just bugs the hell out of me and the vids of v5 are very impressive.
Is there .scene exporters?

No, I don't believe there is a .scene exporter. I think this exporter goes directly to mesh with maybe an option of xml. I would imagine you could massage the xml and add what is needed for .scene. There is another XSI exporter (search the boards) that definitely had XML output.

Ok, here's a problem I did not anticipate. XSI uses STLPort too, but in 4.2 they were clearly still compiling with VC6. Now, they've upgraded to VC7.1, but they are still using STLport (even though they shouldn't need to anymore). They are distributing stlport_vc746.dll with XSI 5.0, but it's built against the VC7.1 runtime libraries.

This is a significant problem for me, since I am still using VC7.0 with STLport (necessary), and the STLport DLL name is the same. Thus the OGRE exporter I build will not load in XSI due to version conflicts unless I remove the version that they are distributing. XSI seems to work this way, but it's far from an ideal solution.

I had intended to upgrade to VC8 next month anyway so this may become a non-event provided the exporter works with it. However, if I need to do a release in the meantime I won't be able to build an XSI v5 exporter here, I will need to recruit one of you to build it for me.

I haven't tracked it down yet, but I get a lot of linking errors on VS 2005 (8.0) when I try to build the exporter (and I'm linking with the SDK etc.).

I'll try to play around with it tomorrow, but all of the missing externals looked like they were from the XSI libs. It seems like a lot of signatures changed for some reason.

I am using 7.1 and stlport (dating back to the debug pause days). I was trying to understand are you looking for a 7.1 or 8.0 build?

If I need to do a release for XSI v5 before VC8 is out and working with the exporter, I'd need a VC7.1 build of the exporter. I'd prefer it without STLport though, since our standard build is without STLport with VC7.1.

I'll see how things go in the next couple of weeks and get back to you if I need help.

btw
If anyone needs it my XSI Exporter for 4.2 seems to run fine under 5.0.

I did a rebuild with the 5.0 libraries and that works too, but the addon builder in 5.0 seems screwed up so I haven't posted it yet.

It's ok, so far anyone that needs the official v5 exporter has built it from source (it works fine in v5, it's my compiler that's the problem) so there's no real rush.