http://i.imgur.com/FCEdH.jpg This thing looks like it has multiple material sections o.O Is that common in 3D objects? If not, what could it represent (besides...corrupt data) I might treat the first number in the highlighted section as "# material sections" and then do a loop over that. ...

Oh, I see it.
I was loading the wrong xac file lol

Here's my guess so far for some BSB files (samples were less than 10 kb) From the filenames, it appears they contain scenery assets like trees stones and architectures. I don't know what some of the floats could represent. The extent of my knowledge so far is limited to coords, faces, UV's, and norm...

Type 1 vertex has vertsize 32 Type 3 vertex has vertsize 48 Type 4 vertex has vertsize 56 dword xbin 10 bytes [seems always 0D 0A 00 0B 00 00 00 00 00 01] short charCount charCount meshName 10 bytes ??? short charCount charCount unique ID (just some name. Some xgeom have, some don't) 2 bytes ??? sho...

Valiant online uses the same format, and it works as well. The smaller items seems to work using the format up there, but it won't work for a lot of the larger files. In particular, some differences are dword xbin 10 bytes [seems always 0D 0A 00 0B 00 00 00 00 00 01] short charCount charCount meshNa...

^I have tried the bms script on some item textures but I converted it to tga afterwards. If anyone is interested in figuring out the xgeom files (items), here's a couple small ones I picked out. There are a couple 1 KB ones http://i.imgur.com/kCBXb.jpg My guess is that it uses shorts for stuff like ...

The contents of this post was deleted because of possible forum rules violation.

The contents of this post was deleted because of possible forum rules violation.

ah, got it thanks.

fatduck posted up shaiya's 3DC format, but I couldn't find anything about the SMOD of 3DO format although they are already supported by various programs. It doesn't look too complicated so I thought I would take a shot at it and try to figure out the format on my own. Comparing a couple SMOD's, seem...

I am writing some scripts to scale models by some factor but don't have any ideas how the new coords are calculated, so I decided to take a couple models and scale them up and down and then analyze the results. At first I thought it was just new_x = x * factor new_y = y * factor new_z = z * factor (...

oh, didn't even notice there was difference in vertsize! Now I am not getting any nan's for the vertices: http://i.imgur.com/TB4vhs.jpg http://i.imgur.com/nQTLZs.jpg I also just realize I confuse myself and thought that float is 32-bytes instead of 32-bits :ninja: http://i.imgur.com/MLYBZ.jpg yay :k...

I've updated the first post with correct files (well, more correct than what it was before). I've also included a variety of models, from characters to items to map assets. The vertex structure seems a little weird cause I'm getting a lot of nan's here and there. This is the part that does it: self....

Unfortunately, it's not a blender importer. It is for my own set of data structures that I use for batch converting between formats (currently only exports in mqo and obj since those are easy to do). It would probably be better to just learn blender, but I don't know if blender has batch conversion ...

nvm, got a different extractor and the output looks fine now.