for some reason the CK can no longer save esm files properly after a while, without destroying the data contained in the file.

i'm not sure if this has anything to do with file size or what (it started happening when the record count went over 1800 or so), but my esp can no longer be converted to esm in the CK anymore. it automatically corrupts all the data.

it can convert smaller esps just fine.


has anyone else had this problem?

right now i can convert to esm in Tessnip, so it isn't that big of an issue. is there any difference between a Tessnip-created esm and a bonafide esm?

I'm at about 8.5 megs and probably like 10000+ records and I can convert to esm just fine.

What do you mean it destroys everything? That doesn't sound good, but doesn't happen to me.

when i reopen in the CK with the new esm, i get hundreds of errors saying the records are missing, record counts need to be truncated, etc.

if i look at the file in the details window, all the records are blank with no names, no groups, they are all just just TES4

if i open it in tessnip it crashes on load.

Amethyst.. the CK was not updated with the 1.5 beta patch. Any mods made and saved through it are corrupted..

http://www.gamesas.com/topic/1358905-important-the-ck-and-beta-15/

does steam force-feed you beta updates as well? because i didn't manually download the beta 1.5 and it still shows v.1.4.27 in-game

Edit: err my bad. I just read all of that again. You have a different problem.

If your errors are nothing like the one reported in that link.

my beta preferences already says Not Participating. i dont think i ever activated it

and it works completely fine in esp, just when converted to esm all hell breaks loose.

but i can convert it perfectly fine in tessnip (i just dont know if a tessnip-created esm is as good as ck esm or if there is any difference)

Yeah sorry about that.(man I must stop this jump-the-gun impulse posting ~_~ )

OK, a month later, i FINALLY found out why this keeps happening to me.


if you are using a Tamriel "wilderness" cell and you change the location to your own custom location, it will permanently corrupt your esm during conversion.

the solution to this is to keep all cell location data in the esp. i'm assuming this is related to lack of ONAM in the esm while hack-ify-ing.

and now my damn horses finally stay on the ground instead of following me up to the mountain balcony LOL


i guess my lesson learned is to only keep the bare necessities in the esm (architecture/navmesh if possible, non-vanilla, containers and npcs), and everything else in the esp.

I've had issues with adding custom locations as well... I think they're all messed up.