NVariety issues resulting in CTD...

[Codifer]

I may be totally out of my depth here but, I seem to recall having read somewhere that the NVariety nekkid mesh IS an armour mesh. The resources are limited and it was the only way it could be done. NBAIO may work differently. I dunno.

 

I figure that Thandal can shed much more light than I.

 

I am still wondering why and how an override mod (such as Sappho's Daughters.... among others) can scramble portions of the game even after it is removed. I must think that either there are bits written to files that I cannot see or they are somehow hiding in the save game or perhaps even in the Dragon Age program folder. I am ignorant.

 

Electrons are funny things and there are a horde of them chasing each other around in my machins.... some are angelic and some demonic I guess.

 

When I do a fresh install of the game I am sure that NVariety will be part of it. As Thandal said, we must endure a bit of hassle to achieve the supposed impossible.

 

Cheers

[Thandal]

Hmmm, I've installed/un-installed/re-installed NV4 more than once. Don't remember ever having to deal with a hidden file, just having to uninstall the "tool" part after the "mod" part.

 

And yes, Codifier is correct (again!) There is no "undressed" base 'toon model in the Eclipse game engine over which clothes, armour, etc. are worn. The "undressed" model is just another model, EXACTLY like the "Heavy Plate", or the "Noble Clothing" models.

 

It's made-up of the same pieces: torso, (including arms to mid-forearm, and legs to mid-calf) lower legs/feet, ("boots") and lower arms/hands ("gloves"). Some special models (e.g. most mage Robes) include all three elements in one, which is why even when you equip Morri with boots and gloves, her appearance in-game doesn't change. (The only time I ever change her robes is when I decide to give her the "Vestments of the Seer", the best BioWare-supplied robes in the game! :teehee: )

 

So there's no way NV4 could modify a character's appearance without interacting, (and potentially interferring) with custom meshes, since it is one too! :thumbsup: