Tales of VS .Chain/GMO

[ShinKun]

Thanks to fatduck, I was able to extract the files from the .mgz
viewtopic.php?p=56417#p56417

http://dl.dropbox.com/u/32409323/Rips/TOVCHain.7z
These might be the model files or another compressed archive.

They are GMO files inside them. I used GitMo.

GitMO to rip them. The load fine in Noesis (3.33), but the mesh is meshed up.


It looks like this in Max.

But, the mesh is messed up. Is there any to fix this?
http://dl.dropbox.com/u/32409323/Rips/TOVGMO.7z

[finale00]

Probably can't do much about it without modifying the GMO parser code.
Someone else had the same problem with GMO files from another game. I think he said the bones were not being done correctly.

[ShinKun]

Is there a way to export without the bones?

[finale00]

Ya, I think noesis has that as one of the options. Scroll through the list.
I don't know if that's the problem though.

[ShinKun]

When I switch subtype models, it loads fine.

http://dl.dropbox.com/u/32409323/Images/Nos001.png

Yea, it's the bones. But, the mesh still needs to fix some how.

http://dl.dropbox.com/u/32409323/Images/MeshFail003.png

[MrAdults]

There is nothing wrong with the bones. (obviously, anims play fine too) There is nothing wrong with most of the model either. On c001_00_00_00000030.gmo, go to Data viewer->Meshes->Mesh 3, double-click Skip render, and there's your evidence. Mesh 3 is probably geometry that's expected to be transformed differently at runtime or something, or a LOD morph target, who knows. Doesn't seem to me that it's got any place on the model at all normally.

[ShinKun]

Awesome, I'll try that out right now.

I noticed a some of the gmo files crashes Noesis, like "c15_00_00_00000030.gmo" Sort it by size, and it's about 965kb.

So, it still exports with that nasty mesh.
http://dl.dropbox.com/u/32409323/Images ... esh001.png

[MrAdults]

I don't have that file, only the ones you uploaded. And yes, if you export it, you would have to delete the offending mesh(es) in Max/Maya/whatever.

[rexil]

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

[MrAdults]

Thanks. It was a crash from the line primitives. New release up to fix it. This release also has support to directly extract the .mgz files, with all of their contents. (they contain more than just GMO files)

[ShinKun]

The offending meshes is tied to the same channels map as the some of the polygons on the model. If you export the with the bones, edit it in Max and try to remove the offending mesh, messes up the bones placement. So, would it be possible to add an option for it not to render mesh that has "skip render 1"

[MrAdults]

The offending meshes is tied to the same channels map as the some of the polygons on the model. If you export the with the bones, edit it in Max and try to remove the offending mesh, messes up the bones placement. So, would it be possible to add an option for it not to render mesh that has "skip render 1"

That's not true. Unless your Max importer is screwing up or you're exporting to a format that doesn't support multiple meshes. COLLADA with OpenCOLLADA as the importer is usually best for preserving everything.

I've also noticed a trend with people exporting PSK a lot lately, apparently someone made some Noesis tutorial with that as the export target. That was a bad idea. PSK kind of sucks as a format and doesn't preserve a number of data types (most notably vertex normals, they have to be approximated with smoothing groups), and the PSK importers I know of for Max all have significant issues. If you're going to make a tutorial, you should use COLLADA as an example.

But it's a non-issue in your case if you're using the new Noesis release, the screwed up meshes were also line primitives. (ps- you're welcome)

[rexil]

Thank you MrAdults you not just fixed the error but made things better. Thank you very much.

[ShinKun]

Just awesome, a part from some of the models missing, it's fine. That can be added in a 3D Editor.

Would you mind adding a another support, if you can?
.DAT
->.CAB
-->.BIN
-->.BLD
http://dl.dropbox.com/u/32409323/Rips/T ... %281%29.7z

The .dat has a FPS4 header, which FPS4Dumpe can dump.
Then there's a cab file, which any windows, mac, etc tool and uncompressed.
The .BIN, I'm think this the cell data, like the NCER files in NDS games.
The .BLD is the graphic and palette. You can view it TitledGGD, but piece those together would be nearly impossible, or at least very time consuming.