Resident Evil 5 (.mod) - Noesis improperly loading model

[Irastris]

Hello, XeNTaX. I'm hoping someone can help me out with this issue.

I'm trying to import a RE5 mod into Noesis, but for some reason several of the vertices end up misplaced in the preview, and persist if I export to a different format.


Here's the mod in question: http://residentevilmodding.boards.net/t ... or-costume
And here's a direct download to the .mod and the .dds textures: http://www21.zippyshare.com/v/0ABoVVCA/file.html

Thanks in advance to anyone that can provide some help and/or a solution.

[shakotay2]

Since DMC4/RE5 is a built-in format there's no direct solution.
You might export as obj, then import to blender separated as groups.
Then it's possible to select proper mesh parts (delete remaining odds in face or edge select mode):

pl1200-groups.jpg

[Irastris]

Since DMC4/RE5 is a built-in format there's no direct solution.
You might export as obj, then import to blender separated as groups.
Then it's possible to select proper mesh parts (delete remaining odds in face or edge select mode):
]

Thank you for the help!

[Darko]

I imagine that model is from the remaster or Re5 in PC because Noesis works wery well on every model of the first RE5.

[MrAdults]

I'd been meaning to look into this, and finally did recently. This looks to be a user-made model that someone has butchered mercilessly. RE5 stores multiple LOD's for each model, and Noesis loads all of them. Typically a LOD index of -1 means "draw in all LOD settings". This model relies on putting the only legitimate surfaces in LOD -1, and has piled a bunch of broken garbage geometry that no longer correctly matches up to the vertex buffers in LOD 0. The game is only showing you LOD -1 surfaces, but Noesis shows you the horror underneath.

Figuring there's more busted data like this floating around in the user community due to whatever unholy tool produced this abomination, future versions of Noesis will have a "-capmodln1" command, which will ignore all geometry that doesn't have a LOD assignment of -1, which causes this broken model to load like this instead.