Dumb ESM?

[Agnot2006]

I have converted a lot of mods into ESM’s to get over the head and body texture problems. But I have found that any mod that has new added speech sound files don’t work, but were fine when the mod was an ESP. All the mod sounds are in Data\Sound\Voice\Modname.

Has anyone else come across this problem and is there a fix for this?

[pkleiss]

I'm not sure if this is the issue, but voice files usually have a structure like

 

\Data\Sound\Voice\mod.esp\voicetype

 

So If you changed the mod name from an ESP to an ESM, you would also have to change the folder name from "mod.esp" to "mod.esm".

[Agnot2006]

I'm not sure if this is the issue, but voice files usually have a structure like

 

\Data\Sound\Voice\mod.esp\voicetype

 

So If you changed the mod name from an ESP to an ESM, you would also have to change the folder name from "mod.esp" to "mod.esm".

 

Yes that was it. I can’t think how I missed it, just stupid I suppose. Everything works fine now, thank you.

[nosisab]

I'm not sure if this is the issue, but voice files usually have a structure like

 

\Data\Sound\Voice\mod.esp\voicetype

 

So If you changed the mod name from an ESP to an ESM, you would also have to change the folder name from "mod.esp" to "mod.esm".

 

Yes that was it. I can’t think how I missed it, just stupid I suppose. Everything works fine now, thank you.

I can't even imagine how converting ESP to ESM can correct textures and voices issues other than losing them altogether and the "vanilla" originals returning to scene.

 

There is always one and just one answer to questions about missing textures and stuff: They are really missing or in wrong place. It's the way to go, you should try to find how they got astray and bring them to their legit home...

 

That procedure you are taking is certain to give you insoluble headaches in short time. ESM is not a "master plugin", actually it is much more limited about what it should contain. There is a reason you'll notice mods that uses ESM have ESPs too. The ESM is meant to keep just "common resources" to be referenced by the ESPs and nothing that can directly affect the game world or game play.

 

Know every minor conflict in ESPs may become deadly conflicts in ESMs. These words are here as advice to everyone that "comprehensibly" mistakes ESM for "master plugin" instead a "place" for common resources that can be "seen" and used by the several ESPs over there, and itself not doing anything more than being that "storage area".

 

PS: finally it's not just changing the suffix to ESM which turns a ESP in one, beyond the purposes there is a specific flag that tells the engine which type is the file being loaded and it is not fooled by the file extension. Just changing the name you are loading mere ESPs anyway :)

[pkleiss]

I would just like to add that there are certain advantages to turning an ESP into an ESM other than the "storage" theme. Two examples that come to mind are inherant bugs to ESPs that do not exsist in ESMs. The lost path navmesh bug and the mismatched head/body tone bug. While this does bot apply to all mods, keeping certain mods in an ESP format can render them virtually unplayable, especially with the navmesh pathing bug.

 

And, Agnot2006, your welcome. :)