-= Gametoast.com =-

Okay, I installed it, and the file appears in the toolbar, however, none of it works... When I looked at the log, It read: The XSI used Is the 2012 Full version, obtained through the student site.

Do you know what the problem is?

It is
I think the problem may lie, that mine is installed on my external hard drive, the F:\ Drive, would that interfere with the scripts?

This is most likely the problem. You have to unzip it into your User directory(check the Installation entry at the same page).

AH! Thankyou. I misread the User Directory - I just put it in the program files. My Thanks.

Okay - I have another problem - probablby because of my noobishness.

The tools seem to work, however, when I export my model, it creates the .msh file, but when I veiw it, it is not there.

I am perplexed by this - I merged all the objects that made up my model, then exported it, but forsome reason, it does not seem to have worked (And yes I did add a Material) Any ideas as to why this is?

With what program view it do you? Tried it in game have you?

View it with the SWBF .msh viewer I do.

I have have not tried it in game yet.

How large is the .msh file in kilobytes? What steps did you take to export the model? Did you create a dummyroot null at 0,0,0 and put your model and hp_fire null under that null and branch select the dummyroot before you clicked "Export"?

It is 827 KB and yes, all of the models, HP etc are under dummyroot.

I created the Model
Added the Materials
Froze it
Branchselect dummyroot
Export

SWBF msh viewer usually resembles in-game in the part of showing a .msh or not. To make sure that it definitely doesn't work, please test it in-game.

How big/how many polies/vertices does your model have? Judging from the filesize it has pretty many.

Try exporting just a cube with one material to see if the export works at all.

Thanks so much for all the work you've put into this Ande! It's made my life a lot easier, and I'm sure the lives of a lot of others too. Especially for guys like me who are just beginning to use XSI, your plugin makes things so much easier, especially with those templates.

A quick question ; what do you mean when you say per-poly material flags?

Also, you might want to update the first post with the newer version of Python.

lucasfart wrote:A quick question ; what do you mean when you say per-poly material flags

Example: You have a gun model. There is a little HUD on the model and you want it to glow, so you select the polygons that make up the HUD and apply a glow material flag to them. Also, there's a scope lens that you want to have be transparent, so you select the polygons that make up the lens and give it a transparency material flag.

Ah ok. That stuff is still changeable via hex editing though, isn't it?

Hmmm. Thats interesting... I tried to export a cube - But that is not showing up either...

I will try to get in game, to test it soon.

EDIT: Munging Now. It shows up in ZE however... I wonder why it did not show up in SWBF2.MSH VIewer?

Hmm. I'm having trouble getting my materials/textures to work on exporting my model. I keep getting this error in the log: I dunno if this is relevent, but i have multiple clusters in my model, and I'm not sure where to go to find the extract polygons command...

To me this looks as if one of the models still is assigned to a material you deleted. Multiple clusters will break the msh if you for example just applied uvs to a part of your model.
ZeroEdit and ZeroEngine seem to ignore scale to some degree, msh viewer doesnt. It could be that the exporter somewhere mistakenly sets scale to a wrong value/forgets to reset the scale after calculating vertex world coordinates.

Did anyone test out weights yet btw?

For the next release I will switch to XSI's material system. For the new feature(s) planned I need XSI's materials. For the user it's better anyways, no need to create every material twice anymore. The Zero-specific flags and attributes will now be stored in the material itself.
There won't be any updates/fixes until this next version is released because I never want to work with the old code again.

Here's a comparison of roughly the same part of the code,
new and old(the new code is broken up in a lot of smaller functions so it's not exactly the same part).

UPDATE:

I can see during the Munge process that the ODF for my Model (In prop format) That the Odf is Mundged.... However, in game it does nt appear.

Any thoughts?

ANDEWEGET wrote:Did you put your model under a null? If you did, did you uncheck branch export current selection? If you didnt, make a screenshot exactly before you hit the export button. I need to see your selection(open the explorer by pressing 8 ) and the export dialog.
Check that you placed it above the terrain.
Make sure you dont use a transparent texture + transparency flag, too.
Do you get any errors in the munge log?

I've changed the export dialog a bit. I think it's better like this. You can see the path better, removed some(IMO redundant) flags, added some flags concerning reports(to reduce clicks when exporting models you know will work). The export will ignore the bbox if a model with the entered name doesn't exist. Now every setting you can make will be stored on export or when pressing the Store Flags button. Also, I think the general look improved a bit, too.

Here it is just before I click Export. I clicked Check Sel - But no problems showed.

Looks fantastic! Also, I see you used the Mass Effect (Slider Thin) font for the graphic, hehe. 8D

@Slime615:
Check Sel doesn't check hierarchy or the MSHProperty.
You shouldn't export the MSHMaterials null, so drag&drop it onto Scene_Root.
Disable Export Global BBox.
It's more efficient to use nulls as hardpoints than models, but that should not break the .msh.
Maybe just select dummyroot, then press Export.
Last thing: Double click the item with the orange 'C' icon(named MSHProperty) and check if a material with the name exists. Try reassigning the material via the material manager, too.

@Marth:
Thanks! The font's called Koshgarian or something, could be from Mass Effect, I use it because it looks pretty similar to XSI's UI font though.